Yes, I checked that before posting. Everything matches up. It is a varchar(10) column. We've not added any translation or other data manipulation on this column in the SSIS package.

I've seen this happen before, years ago on prior levels of SQL Server, with a SSIS package. We never had a solution.

Just hoping someone has had this situation trying to use a SSIS package and had a solution to get the data transferred exactly as it exists in the source.