Start with business processes, not modules

An ERP implementation is ready when people can complete their real work and trust the resulting records. Installing sales, inventory and finance modules is only part of that outcome. Your checklist should therefore describe tasks, owners and evidence, not just configuration screens.

Choose a first release that can be tested end to end. An order flowing from checkout through stock reservation, dispatch and reconciliation is a clearer scope than “connect everything.” Document what remains outside that release and how the team will handle it temporarily.

Use this checklist as a planning framework. Adapt it to your accounting requirements, operating model and software configuration with the relevant business owners.

1. Agree ownership and acceptance criteria

  • Name one accountable business owner and an owner for each process.
  • List the systems that create orders, products, customers, stock and payment events.
  • Choose the authoritative source for each field or business decision.
  • Write acceptance criteria using real tasks and expected outputs.
  • Record exclusions, dependencies and decisions still waiting for approval.

For example, “orders sync” is not an acceptance criterion. A better test states which paid orders qualify, how discounts and shipping charges map, when stock is reserved, and where an unmatched product appears for resolution.

2. Prepare data before migration

Audit duplicates, missing identifiers, inconsistent units, inactive records and conflicting customer details. Decide what to migrate, what to archive and what must remain accessible in the old system. Do not migrate historical clutter simply because an export makes it possible.

Maintain stable source identifiers in the mapping design so a repeated import can be matched deliberately. Test how your chosen importer updates existing records; never assume that running an import twice is harmless.

  • Assign a data owner to approve each dataset.
  • Document field meanings, required values and transformation rules.
  • Test representative records, including awkward exceptions.
  • Reconcile counts and business totals after a trial migration.
  • Protect sensitive exports and agree their retention and deletion process.

Use our ERP–CRM field mapping workbook as a starting point. It is free and requires email delivery; adapt the fields to your actual systems.

3. Design integrations for failure as well as success

Every connection needs an owner, a retry policy and a visible exception queue. Decide what happens when a system is unavailable or a record cannot be matched. The correct response may be to hold the task for review, not to guess a value.

Test duplicate notifications and interrupted jobs. An order event delivered twice must not create two business transactions. A replay after an outage should reconcile the affected records, not silently reset later changes.

For commerce, pay particular attention to stock reservations, cancellations, partial fulfilment, refunds and returns. Our Shopify–Odoo inventory guide explains why stock definitions and timing need explicit agreement.

4. Test the whole operating day

Build a scenario pack with expected results and a named person signing off each one. Include ordinary orders, unusual discounts, mixed tax cases for review by the finance owner, partial deliveries, failed payments, returned items and warehouse transfers.

Run tests with the roles people will actually use. An administrator completing a task does not prove that a warehouse colleague has the required access, or that a salesperson is prevented from changing restricted data.

Check documents, screens and reports together. A shipment can look correct in one screen while an accounting or inventory record is wrong elsewhere. Keep unresolved discrepancies visible and give critical failures a clear stop launch rule.

5. Rehearse cutover and recovery

  1. Set the migration window and specify which writes must pause.
  2. Take verified recovery copies using the supported procedures for your systems.
  3. Run the migration and reconcile records, stock and relevant balances.
  4. Have business owners approve the reconciliation evidence.
  5. Enable integrations in a controlled order and monitor the first transactions.
  6. Define who can call a rollback and how transactions created after cutover will be handled.

A rollback is not simply restoring yesterday’s database if today’s orders have already arrived. Rehearse the decision and recovery process before launch, including communication to the teams affected.

6. Plan the first weeks of ownership

Provide short role specific instructions, a support channel and an escalation owner. Review failed jobs, reconciliation differences and repeated manual corrections daily during the initial period. Schedule a handover covering credentials, monitoring, documentation and change approvals.

Measure whether the implementation improves real work: order processing time, stock discrepancies, unresolved exceptions and time to close key operational reports. Do not judge success only by how many modules are enabled.

Discuss your ERP project with the current systems, number of entities or locations, major pain points and intended first release. For the broader architecture, read our ecommerce ERP integration guide.