Agree the process before configuring the product
Map purchasing, stock, sales and accounting responsibilities with the people who perform the work. Identify where departments use different meanings for the same field or status. Demonstrate important exceptions in a shortlisted product before assuming a configuration will cover them.
Resolve three migration conflicts before cutover
Two departments use different codes for the same product and keep separate opening balances. Importing both files successfully is not the same as creating a reliable ERP record. Use a trial migration and reconcile these cases.
| Conflict | Resolution to approve |
|---|---|
| Two codes for one product | Choose a master ID and retain aliases for historical records |
| Different customer balances | Finance signs off the opening balance and the adjustment trail |
| Orders edited during migration | Agree a freeze window or capture and replay approved changes |
Treat migration as its own workstream
Assign owners for customer, supplier, product and opening-balance data. Agree which history to move, which records to archive and how to resolve duplicates. Rehearse imports and compare totals against the current system before selecting a cutover date; successful import counts alone do not establish correct balances.
Plan the first operational week
Identify who answers staff questions, approves corrections and monitors interfaces. Decide when the old system becomes read-only and how transactions around the cutover are reconciled. Training should follow the actual role and workflow, with a clear path for exceptions after the implementation team steps back.
Before you proceed
- Assign data owners and acceptance criteria.
- Rehearse migration and reconcile meaningful totals.
- Agree cutover, staff support and correction procedures.
