/services
Migrate to Odoo 19 without losing your history
Version upgrades and platform migrations (SAP/QuickBooks/spreadsheets → Odoo); data integrity; parallel-run plan
- 41 Migrations delivered since 2020
- 0 Rollbacks in six years
- 2 Parallel-run cycles as standard
/the-work
What is included
- A field-level source-to-target mapping document, signed before anyone writes an extraction script
- A full-volume trial load onto a copy of your production database
- Opening balances and part-settled transactions reconciled to the ledger
- Serial and lot history carried across in full, not summarised into an opening figure
- Custom modules ported to the target version and re-tested — or retired where standard now covers them
- Two parallel-run cycles, each with a written variance report
- A rollback plan with a named decision-maker and a cut-off time
/what-it-prevents
Why each one is there
- A go-live where finance cannot close the first month
- Stock valuations that disagree with the ledger from day one
- Traceability gaps that surface at an audit rather than before it
- Customisations that worked on 16 and break silently on 19
- A second cycle that only proves the first one was lucky
- A cutover weekend where nobody is authorised to stop
/how-we-run-it
How we run a migration.
-
01
Data audit and mapping
Every table in the source system classified: migrate, archive, or leave behind. The mapping document is signed before extraction begins, and the exclusions are signed too.
2 weeks
-
02
Trial load
A full-volume load onto a copy of your production database. The first variance report goes to your finance lead, not to us.
2–3 weeks
-
03
Configuration and module port
The target build configured against the mapping. Custom modules ported and re-tested, or retired where the standard product has caught up — we will tell you which.
4–6 weeks
-
04
Parallel run
Both systems live, both closed, both compared. Two cycles as standard; the second exists to prove the first was not luck.
2 cycles
-
05
Cutover
A rehearsed sequence with a written go/no-go at a fixed hour, and one named person on your side authorised to call it off.
1 weekend
-
06
Hypercare
The migration engineer stays on the account. Ninety days, then handover to support with the documentation already written.
90 days
/what-you-get
What you get at the end.
The mapping document
Field-level source-to-target mapping, signed off, with every decision and every exclusion recorded and dated.
/02The reconciliation pack
Trial-balance, stock-valuation and open-item comparisons for each parallel cycle, with the variances explained.
/03The ported codebase
Custom modules in your repository, version-tagged against Odoo 19, with the tests that prove they still work.
/04The runbook
The cutover sequence exactly as executed, the rollback plan, and the escalation contacts with response times.
/where-this-fits
The services either side of this one.
/next
Tell us what you are running today.
Thirty minutes, no slides. We will tell you straight if Odoo is not the answer.