Agree what “migration” means
Moving accounting data can mean opening balances, active customer and vendor lists, selected transactions or a longer history. These are different projects. Start by listing the information you need in the new system and the records you can retain separately for reference. Do not assume every attachment or custom field will transfer in the same way.
Ask your accountant and responsible record owner about retention obligations before excluding history. Write down the source system, target product, date range, currencies and any related applications. A clear scope makes it easier to evaluate a migration proposal and recognize missing work.
Clean with a record of the changes
Review duplicates, inconsistent names, inactive records and unclear account mappings. Decide who can approve a merge or correction. Cleaning data should not mean silently deleting inconvenient records or overwriting the only copy of the source. Preserve an accessible original and document meaningful changes.
Build a mapping sheet for the fields and accounts that matter. Include the source value, destination value, owner and unresolved questions. Where two records look alike, check whether they represent the same thing before combining them. The goal is a defensible set of decisions, not simply a shorter spreadsheet.
Define acceptance before the test
A completed import is not the same as a reconciled migration. Agree which balances, lists and representative transactions will be checked. Have the responsible finance person define the appropriate reports, dates and accounting basis for comparison. Differences need investigation rather than a cosmetic adjustment to make totals agree.
- Preserve dated source exports and a secure backup.
- Compare agreed financial totals on a consistent basis.
- Trace representative customer and vendor records.
- Record exceptions and the person responsible for resolution.
Practice the handover
Use an authorized test environment and a representative sample before the final cutover. Walk through the tasks people will perform after launch, including corrections and reporting. A clean import may still leave an unusable workflow if permissions, integrations or staff instructions are missing.
Plan a cutover window and decide when the source stops accepting routine entries. Identify the person who can pause the change if acceptance checks fail. Keep a recovery plan that explains which system remains authoritative, how access is controlled and how staff will be informed.
Keep an evidence pack
Retain the agreed scope, mapping decisions, reconciliation results and sign-off together. Restrict access to financial and personal information; a general website inquiry is not a suitable way to transfer company files. Discuss an approved secure transfer method with the actual implementation provider before sharing data.
Further reading
Product details were checked on October 26, 2026. Features and terms can change. These are general planning resources, not individualized accounting, tax or legal advice.