Migration strategy: what to bring

"Bring everything across" is what clients ask for, and it is expensive, slow and usually pointless. Three categories. Must migrate: the open items — open payables, open receivables, the asset register, bank balances, the opening trial balance. Without these you cannot operate. Should consider: master data, meaning suppliers and customers, and prior period balances for comparatives. Usually leave behind: closed transaction history — keep the legacy system read-only for a defined period instead. The comparatives decision: how many years of prior balances? Two is common, and each year costs effort and adds risk. Ask what the client actually reports on, not what they would like to have. Master data is a cleansing opportunity. Migrating a supplier master with forty per cent inactive records is migrating a problem. Cleanse before, not after. The dry run is non-negotiable — full-volume migration into a test environment before UAT. Projects that skip it discover…

In this module: Module 14 · Data Migration and Integration

1. 1Migration strategy: what to bringFree preview
2. 2The import architecture
3. 3File-based import end to end
4. 4The finance import objects
5. 5Opening balances
6. 6Configuration migration between environments
7. 7Integration patterns and third parties
8. 8What breaks
9. 9Lab: migrate opening balances