An Excel Migration job that updates a custom field fails with 'savepoint 'NEW_JOB' never established,' even though the same general setup worked without issue on a previous migration job targeting a different view.

All FAQ questions / Data migration

Answer

Check whether the Migration Job ID itself contains a space or a hyphen — the Excel migration add-in uses the job ID to dynamically generate procedure names internally, and a space or hyphen in that ID breaks that dynamic procedure creation, producing this exact savepoint error. Stick to letters, numbers, and underscores only in Migration Job IDs going forward. For a migration job that's already been created with a problematic ID, right-click it and choose 'Copy Migration Job' to create a working copy under a new, valid name, rather than trying to rename the existing broken one 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