Move to a new ERP without stopping the business.
A complete checklist for moving from spreadsheets, QuickBooks or an older ERP: what to decide first, which master data and opening balances to bring across, how to rehearse, and how to run cutover week.
The ERP migration checklist.
Guide 02What this guide covers.
A migration fails in one of three ways: the data is wrong, the people are not ready, or the cutover date arrives before either is fixed. This checklist covers all three, in the order you will meet them.
By the Sundial team. Free to use, copy and adapt for your own business.
1. Decide before you migrate
- Name one owner for the migration, with the authority to make data decisions.
- Choose the cutover date. The start of a month is simplest; the start of a quarter or of the fiscal year (January 1 for most US companies) is cleaner still, because opening balances come straight from a closed period.
- Decide how much history to bring. Most businesses bring master data and open balances, and keep the old system read-only for history.
- Decide whether to run old and new in parallel, and for how long. Parallel runs catch errors but double the work; one or two cycles is usually enough.
- List every integration that must work on day one: bank feeds, card and ACH payments, e-commerce, payroll, shipping.
2. Clean the data before you move it
Never migrate a mess. Fix it in the old system or in a staging spreadsheet first.
- Merge duplicate customers, suppliers and items.
- Deactivate items, customers and suppliers with no activity in the last year rather than migrating them.
- Agree naming rules for item codes, customer names and warehouses, and apply them now.
- Check units of measure and conversion factors (case, each, lb) on every active item.
- Confirm sales tax details for customers (including exemption certificates) and suppliers, and the tax templates you will use.
3. Master data checklist
- Company details, fiscal year, currency and number series.
- Chart of accounts, mapped from the old one, including cost centers.
- Customers and suppliers, with addresses, contacts, payment terms and credit limits.
- Items with groups, units of measure, valuation method, reorder levels, batch and serial settings.
- Warehouses and locations, matching how stock is physically stored.
- Price lists and pricing rules.
- Bills of materials and routings, if you manufacture.
- Fixed asset register with categories and depreciation methods.
- Users, roles and permissions.
4. Opening balances checklist
Opening balances are taken as at the close of the day before cutover. Each one must reconcile to the old system’s closed figures.
- Trial balance by account.
- Open customer invoices, one by one, not as a single total, so you can collect against them.
- Open supplier invoices, one by one.
- Stock quantity and value per item, per warehouse, per batch or serial.
- Bank and cash balances, with uncleared checks, ACH and wire transfers listed.
- Fixed assets with cost and accumulated depreciation.
- Open sales orders, purchase orders and work orders, with what has already been delivered or received.
- Advances received from customers and paid to suppliers.
5. Rehearse at least twice
Run the full migration into a test copy at least twice before the real one. Time every step.
- Load masters, then opening balances, in the same order you will use on cutover day.
- Reconcile: trial balance, receivables total, payables total and stock value must each match the old system.
- Have key users run a day of real transactions in the test copy: an order, a delivery, an invoice, a receipt, a payment.
- Write down every fix you make, and fold it into the import files, not into manual corrections.
Example reconciliation (sample figures for an illustrative company, Kestrel Workspace): receivables in the old trial balance $1,842,300; sum of imported open invoices $1,842,300; difference $0. Stock value in old system $4,210,650; sum of imported stock lines $4,208,150; difference $2,500, traced to one item with a wrong unit conversion and fixed in the import file before the second rehearsal.
6. Get people ready
- Train by role, using your own data in the test copy, not generic slides.
- Give each team a one-page guide for the five things they do most.
- Name a go-to person in each team for the first month.
- Agree which reports each manager will look at in week one, and check they are ready.
7. Cutover week runbook
- Announce a freeze: no new masters in the old system from an agreed time.
- Close the old system’s period and export final balances.
- Load masters and opening balances using the rehearsed files.
- Reconcile trial balance, receivables, payables and stock value, and record the sign-off.
- Switch integrations and bank feeds to the new system.
- Make the old system read-only. Do not switch it off.
- Go live, with the migration team on hand for the first days.
8. The first 30 days
- Reconcile bank daily for the first two weeks.
- Check stock for fast-moving items at the end of each week.
- Review every error or workaround people report, and fix the cause, not only the symptom.
- Run the first month-end close with the old and new figures side by side.
- Hold a review at 30 days against the problems you set out to fix.
Common pitfalls
- Migrating years of transactions nobody will look at, and delaying go-live to do it.
- Loading receivables as one total, so nobody can collect against individual invoices.
- Skipping the second rehearsal because the first one “mostly worked”.
- Customizing before the team has used the standard flow for a month.
- Switching off the old system before the first close in the new one.
Next: run your first close in the new system with the month-end close playbook.

