Guides / Switching · 3 min read
Prepare the records before the migration.
A clean move begins with an agreed scope, readable exports and a record of every uncertainty. The aim is not to make the old data look perfect; it is to make the decisions visible before launch.
By the OperiQ team
1. Agree which records are moving
List the product, customer, supplier, stock and opening financial records in scope. Decide which system owns each field, the date at which balances will be taken and who can approve an exception.
- Product codes, descriptions, units and tax treatment
- Customer terms, balances and account status
- Supplier references and purchasing records
- Stock locations, quantities and unresolved differences
2. Keep the source and the decisions
Retain an untouched copy of every source export. Work on a controlled copy, record transformations and flag missing identifiers instead of guessing. Duplicate codes, blank terms and inconsistent units should become review items.
3. Test before the final cutover
Run a test migration and reconcile totals against the source: stock value, customer balances, supplier balances and sample documents. Review warnings with the people who understand the records, then approve the final scope in writing.
The available exports and data quality determine what can be moved. A migration plan should state those limits plainly.
See how OperiQ handles this on your own work.
Book a meeting