Data migration
Plan what data moves, clean it, and load it in cycles until the customer accepts it.
This page applies to the Establish solution stage.
IDK templates: IDK-14, IDK-15
Page in the app: /p/{projectId}/migration
One load cycle
Run several cycles. Each one should have fewer issues than the last.
- Extract. Take data from the old system.
- Cleanse. Fix and complete it.
- Load. Load it into the target environment.
- Check. Compare counts and sample records.
- Accept. The data owner accepts each object.
How to do it
- Define data groups. Decide scope, history and access to old data.
- List migration objects. Give each one an owner and a method.
- Run a cycle. Record the result and the issues it found.
- Sign off. The data owner signs each object, then each data group.
Good to know
- The last cycle before go-live is a full rehearsal.
- An object may set its own tolerance; give the reason before its mapping is approved.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: