Migrating Arabic (or other non-Latin-script) data into a custom table via a standard migration job results in garbled special characters instead of the correct text.

All FAQ questions / Data migration

Answer

Make sure the character set in use is explicitly marked as Unicode in the migration job configuration, and save your source data file itself as UTF-8-compatible before running the migration. Standard migration jobs handle non-Latin-script data like Arabic correctly once both the migration job's character-set setting and the source file's own encoding are properly set to Unicode/UTF-8 — the garbled-character symptom is almost always an encoding mismatch rather than a genuine limitation of the migration mechanism.

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