A migration job source file with double-quote characters inside a field's own data ends up with extra double quotes inserted around and inside the value after import (or when viewing the raw file) — is there a way to prevent IFS from adding these?

All FAQ questions / Data migration

Answer

IFS isn't adding anything incorrect — this is standard CSV escaping: a field containing a literal double-quote character has to have that character doubled and the whole field wrapped in quotes per the CSV format, which is exactly what you're seeing when viewing the raw file in a text editor (Excel just hides this and shows you the clean original value). The migration import itself correctly interprets this standard CSV escaping and stores the true original value. If you'd rather sidestep CSV escaping entirely for data containing quote characters, saving the source as a plain tab-delimited file and setting the migration job's column separator to tab avoids the need for quote-escaping altogether.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Data migration questions