Moving to a new ERP, or a major new version, is one of the biggest changes a finance and operations team will make. The technology matters, but most issues come from scope, data and people. Working through these questions early keeps the project on track.

Scope and processes

  • Which business processes are in scope, and which are not?
  • Who owns each process, and who signs off the future design?
  • Which current workarounds should the new system remove?
  • What reports and outputs must be available on day one?

Chart of accounts and structure

A migration is the best chance you will get to clean up the chart of accounts, cost centers and entity structure. Decide early whether you will move the current structure as-is or redesign it, because the answer affects data mapping, reporting and testing.

Data

  • Which master data needs cleansing: customers, vendors, items, employees?
  • How much transaction history will move, and how much will be archived?
  • Who validates migrated data, and against what?
  • How will opening balances be reconciled and signed off?

Data work almost always takes longer than planned. Start cleansing early and run at least one trial migration before the real one.

Integrations

List every system that sends data to or receives data from the ERP: banking, payroll, CRM, e-commerce, reporting and others. For each, decide whether it is needed at go-live, who builds it and how it will be tested.

Testing

Test with real scenarios, not just individual screens. Run a full cycle, such as procure-to-pay or a month-end close, using migrated data. Involve the people who will use the system every day in user acceptance testing.

People and training

  • Who needs training, on what, and when?
  • Who are the internal champions in each team?
  • How will questions be answered in the first weeks after go-live?

Cut-over and support

Agree the cut-over plan in detail: freeze dates, final data loads, reconciliation steps and the go/no-go criteria. Plan for a period of heightened support after go-live, and schedule a review once the first month-end close on the new system is complete.

The short version

Agree scope and owners, clean the data early, map every integration, test end-to-end with real data, train the people who will use it and plan support for the first months. Projects that do these things well rarely have surprises at go-live.