Before moving business data into Odoo, rehearse the complete handover and ask business owners to verify the results. A successful file upload should not be your acceptance test. Use a migration rehearsal to check what moved, whether people can work with it, and what will happen if the final cutover must stop.
Define what the migration must preserve
Start with a written scope rather than a folder of spreadsheets. For each business area, decide which master records, opening positions, open transactions and historical information belong in the new environment. Distinguish information needed for daily operations from information that can remain in a controlled archive. Ask the finance and operations owners to approve these choices before extraction begins.
Make exclusions visible. If closed documents will remain outside Odoo, record how authorised users will retrieve them and who will maintain access. If a legacy reference must remain searchable, include it in the mapping and test it. Treat these as design decisions, not details to resolve after users start work. This checklist is a planning framework, not a promise that every legacy record or customisation can be transferred unchanged.
- Name a business owner for each dataset and its acceptance criteria.
- Record the agreed migration scope, exclusions and archive arrangements.
- Identify dependencies between customers, products, balances and open documents.
- Confirm who may approve corrections and who may authorise go-live.
Review mappings before loading a rehearsal
Prepare a mapping sheet that explains the meaning of each source field and its intended destination. Include currencies, units of measure, company ownership and the treatment of blank values. Agree how duplicates will be identified before anyone merges records. A familiar name alone is not a safe business rule for deciding that separate records represent the same entity.
Use a documented sample that includes ordinary records and difficult cases. Consider an inactive product referenced by an open order, a customer with several delivery addresses, or an item held in different units. These are suggested test scenarios, not claims about your database. Ask the responsible team to explain the expected result in business language so the migration team can test against an agreed outcome.
Run the rehearsal in a separate, controlled environment. Agree how confidential data will be protected and how test emails, integrations and other outward actions will be handled. Record the extraction date and mapping revision so everyone knows exactly which inputs produced the results under review. Avoid making untracked corrections directly in the rehearsal database.
Reconcile business meaning, not just record counts
Record counts are useful evidence, but ask what those counts prove. An equal number of customers does not demonstrate that addresses, payment terms and ownership are correct. Prepare a reconciliation pack that connects the source extracts, transformed data and loaded results. Where totals differ, explain the reason and obtain approval rather than accepting an unexplained variance because it appears small.
For finance, ask the accounting owner to define the balances and open items to compare. For inventory, ask the operations owner to define quantities, locations and any valuation checks appropriate to the agreed scope. Keep these checks separate from a broader review of accounting policy or regulatory obligations. The migration team should not silently resolve policy questions through a transformation rule.
- Compare agreed totals using the same date, scope and business definitions.
- Trace selected records from their source through to their final destination.
- Investigate missing references, unexpected duplicates and rejected rows.
- Document exceptions with an owner, corrective action and acceptance decision.
Let users complete realistic working scenarios
Ask users to test with their intended roles, not only with an administrator account. Have the sales team locate a migrated customer and review an open order. Ask operations to find the relevant product and stock information. Have finance inspect selected opening items and explain how they will continue work. Adapt each scenario to the applications and workflows actually included in your project.
Separate a data defect from a training gap or an unfinished configuration. A user who cannot complete a scenario needs a clear resolution, but changing the migration file is not always the right answer. Keep a shared issue register with the scenario, expected result, observed result and responsible owner. Retest the affected workflow after a correction and preserve the evidence of the result.
Role-based preparation belongs alongside the technical rehearsal. Digital Economics lists end-user training, key-user training, tailored materials and post-go-live coaching within its training service. Use the rehearsal to identify the instructions your team needs for its actual working tasks rather than relying only on a general product demonstration.
Explore training and adoption support
Rehearse the cutover and the recovery decision
Write a cutover runbook that names who freezes legacy updates, takes the final extract, runs the agreed checks and releases access. Decide how to handle transactions created between the rehearsal and the final move. Rehearse the sequence and record the time each activity actually takes; do not schedule the final handover using an estimate that nobody has tested.
Agree stop conditions and a recovery decision before the cutover begins. Specify who can call a halt, how the team will communicate, and what must be verified before anyone resumes work in the previous environment. Test the recovery approach in the appropriate controlled setting. A backup file on its own should not be treated as evidence that the business can resume safely.
- Confirm the final extraction and legacy update arrangements.
- Assign an owner and evidence requirement to every release check.
- Define the authority, conditions and communication route for stopping cutover.
- Agree post-go-live monitoring, issue triage and access to historical records.
Make go-live an evidence-based decision
Close the rehearsal with a short readiness review. List the reconciliations that passed, the workflows users accepted and the exceptions still open. Give each unresolved item a business impact and a named decision maker. If a material condition has not been met, update the plan and repeat the relevant tests rather than replacing evidence with confidence.
Digital Economics lists data mapping and validation, parallel-run support and tested cutover planning within its migration offering. Bring your scope, sample data, open questions and acceptance criteria to the discussion. The useful starting point is not simply asking when data can be uploaded, but agreeing how your team will know it is ready to work.
Explore Odoo migration and upgrades
Plan your Odoo migration rehearsal
Talk to Digital Economics about your data scope, validation responsibilities and cutover readiness before choosing your final go-live plan.