A migration job that was previously working stops updating certain custom fields correctly, despite everything in its configuration appearing correct — nothing obviously wrong can be found.

All FAQ questions / Data migration

Answer

If a migration job's configuration looks correct but it's stopped updating specific fields for no discernible reason, deleting the migration job entirely and recreating it from scratch has resolved this in at least one confirmed case — some kind of stale or corrupted internal state in the job definition can apparently cause this, without there being any visible configuration mistake to find and fix directly.

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