Odoo services · Odoo Migration Services
Move to Odoo without losing your history.
Migration is where implementations fail quietly. A bulk import that "worked" can leave you with balances that do not tie out and stock that does not exist. We validate against the source system at every checkpoint instead of trusting one big load.
—— Where it hurts
The problems this work actually solves.
The hard part of a migration is rarely the copying. It is the years of quiet workarounds inside the old system that surface the moment you try to move — and those are exactly what this service is built to handle.
Years of dirty data
The customer list has the same company entered four different ways. Product codes changed convention twice and nobody wrote down when. None of it hurt day to day, so nobody fixed it — but an import will faithfully copy every duplicate into the new system.
How we handle itThe source audit profiles duplicates, orphans and format drift before anything moves, and we agree written cleanup rules with you — merge, fix or drop — so the data lands clean.
Customisations with no home in the new system
Your old system carries custom fields, reports and workflows built up over years — some by vendors who no longer exist. A straight data move leaves them behind, and the team discovers the gap in week one.
How we handle itWe inventory every customisation during the audit and decide each one with you: covered by standard Odoo, worth rebuilding, or safe to drop. Nothing disappears by accident.
A chart of accounts that will not map
The legacy chart of accounts grew organically — accounts reused for the wrong things, sub-accounts multiplying, statutory formats bolted on late. Forcing it one-to-one into Odoo carries every old workaround into the new books.
How we handle itWe build the mapping table with your accountant, restructure only where it earns its keep, and have opening balances signed off before a single journal posts.
Open transactions at cutover
On any real cutover date there are open sales orders, half-received purchase orders, unreconciled payments and stock in transit. Migration plans that only account for closed, tidy data stall exactly here.
How we handle itThe cutover plan names every open-item type and how each one moves, and we rehearse the whole sequence on staging before the real weekend.
The old system has no owner
The vendor who built the system is unreachable, the export menu covers half the tables, and the one employee who understood it left last year. You cannot plan around data you cannot see.
How we handle itWe work from a database backup rather than the export menu, reconstruct the data model ourselves, and document it as we go — the audit does not depend on anyone's memory.
—— Learn from other projects
Mistakes we see, and how to avoid them.
Migrating everything 'just in case'
Ten years of transactions feel safer to bring than to leave behind, but the extra history slows every report, multiplies cleanup cost, and gets opened perhaps twice a year. We agree a retention cut-off up front and keep the rest as a read-only archive — nothing is lost, and nothing drags on the new system.
Planning to clean the data after go-live
'Import now, fix later' turns the live audit trail into a repair log, because every correction posts as a real transaction in the new books — and 'later' rarely comes once the team is busy running the business. We clean in staging, before load, where a fix is an edit rather than an accounting entry.
Skipping the trial run
Many teams attempt the migration for the first time on go-live weekend, then discover at two in the morning that one batch takes six hours instead of one. A cutover should be a repeat performance, not a premiere. We run the full migration at least once on staging, with a stopwatch, before touching the real date.
Treating migration as an IT project
When only IT signs off, opening balances get approved by people who never have to reconcile them, and accounting and the warehouse inherit numbers they never checked. Every dataset we load is signed off by the department that will live with it — accounting approves the balances, the warehouse approves the stock.
Going live on 'looks fine'
Without written acceptance criteria, go-live becomes a feeling — someone scrolls a few screens and declares victory, and the discrepancies surface at month-end close when the old system may already be gone. Before we retire anything, a written checklist must tie out against the source: trial balance, open receivables and payables, stock valuation.
—— Ways to engage
Three ways to start with us.
Migration assessment
A short, fixed-fee study of your source system that ends in a written migration plan and a firm quote. Useful on its own, whoever ends up doing the move.
- Data profiling report — duplicates, gaps and format issues, quantified
- Field mapping and cleanup rules agreed in writing
- A fixed quote and timeline for the migration itself
Full migration delivery
We run the whole move — extraction, cleanup, staged loading, cutover and the parallel-run period — with one consultant owning it end to end.
- Validated batches with a reconciliation report after each one
- A rehearsed, timed cutover with a rollback point at every step
- Parallel-run support until you sign off and retire the old system
Stalled migration rescue
For migrations started elsewhere that will not reconcile. We find where the numbers diverged and get you to a clean sign-off — repairing what is sound, reloading what is not.
- Discrepancy audit tracing Odoo records back to the source
- A written repair-or-reload decision for every dataset
- Reconciliation evidence your accountant and auditor can accept
Your implementation partner
A partner, not a licence reseller.
We are not chasing licence volume — we design, build and stay accountable for systems that companies run their operations on. The consultant who scopes your project stays through go-live and the support that follows, and everything we commit to is written into a fixed scope per phase.
—— What done looks like
Outcomes you can verify yourself.
A trial balance that ties out
Opening balances in Odoo reconcile line by line against the source system, and your accountant has signed the comparison. Month-end close works from the first month because the starting numbers were proven, not assumed.
Every record traceable to its source
The mapping tables and cleanup rules are delivered as documents, not tribal knowledge. Years later, anyone can trace an Odoo record back to the legacy system and see exactly what changed on the way across.
A freeze window you knew in advance
Because the full migration was rehearsed and timed on staging, the real cutover ran to a known schedule. Your team stopped entering data for an agreed window — and knew before the weekend exactly how long it would be.
The old system retired on evidence
The legacy system is switched off only after the parallel run reconciles and each department has signed its own data. What remains is a read-only archive that satisfies your document retention obligations.
—— How we work
What the engagement looks like.
Source audit
We profile what you actually have — duplicates, orphans, encodings, dates in three formats. Every legacy dataset has these.
Batch and validate
Masters first, then transactions, then balances. Each batch is reconciled against the source before the next begins.
Parallel run
Both systems run together for a period so discrepancies surface while the old system can still answer questions.
—— Why us
What you get that you would not elsewhere.
Reconciled, not just imported
Every batch is tied back to the source. "It loaded" is not the same as "it is correct".
Reversible checkpoints
Nothing is a one-way door until you sign it off. A bad batch is rolled back, not patched over.
History preserved
Closed periods, historic invoices and audit trail come across. You do not restart your accounting life at zero.
Not sure where to start? A short call sorts it.
Talk to an Odoo specialist ➜—— Why us
What working with us is actually like.
An Official Odoo Partner doing the move
We are an Official Odoo Partner through the India programme, which gives us partner-level access to Odoo's versions and upgrade tooling. For moves from older Odoo versions, that access matters daily, not occasionally.
One consultant, first call to go-live
The person who audits your source data is the same person standing by on cutover weekend. Mapping decisions made in week one do not get lost in a handover, because there is no handover.
Fixed written scope per phase
The assessment is quoted as one fixed fee, the migration as another, each with its deliverables in writing. If something found mid-move changes the scope, you get a written change to approve — not a bigger invoice to discover.
Reconciliation sessions in Thai
Balance sign-off fails when the accounting team cannot interrogate the numbers in their own language. Our Bangkok office runs reconciliation sessions natively in Thai, with documentation delivered in both Thai and English.
Honest licence maths for the move
Leaving a per-user legacy ERP is usually the moment licence costs get renegotiated. We tell you plainly that Odoo Community is $0, and if Enterprise fits your case better, Odoo bills you directly — we never mark up the licence.
Cutover cover across three time zones
With offices in Thailand, the USA and India, a cutover weekend does not depend on one office staying awake. Long extraction and load jobs are watched around the clock without heroics.
We will tell you what not to migrate
The cheapest record to migrate is the one you archive instead. Because our fee is fixed per phase rather than billed by the hour, we have no incentive to haul data you will never open.
Quotes only after we have seen the data
Migration cost is driven by data quality, not record count, so any quote given before the audit is a guess. We keep the assessment small and fixed, then quote the migration on what we actually found.
—— Partner tiers, explained
What an Odoo partner tier does and does not tell you.
Odoo ranks partners by certifications held and licence volume sold. A tier signals commitment to the programme — it does not tell you who will actually staff your project. Ask that question of any partner, including us.
Learning Partner
New to the programme, building their first certified consultants and reference projects. Not a red flag — everyone starts here — but ask for hands-on proof.
Official Partner
Certified consultants and active delivery. This is where we sit, enrolled through the India programme, delivering from Thailand, the USA and India.
Silver & Gold
Higher tiers earned mainly through licence sales volume and headcount of certified staff. A strong signal of scale — not automatically of fit for your project.
—— Who this is for
Built for your size, not resized for it.
Growing companies (5–100 people)
Most companies this size are moving off QuickBooks, Zoho, a local accounting package or a wall of spreadsheets. The move is smaller than you fear — if the data is treated with respect.
- A single-entity move from an accounting package typically completes in weeks, not months.
- Odoo Community's $0 licence means the migration itself is usually the main cost — and it is quoted fixed.
- The freeze window is typically a weekend, planned around your billing cycle.
- You work with one consultant throughout — no project bureaucracy to feed.
Mid-market (100–500 people)
At this size the move usually involves multiple entities, heavier history and an ERP such as SAP Business One or an old, customised Odoo. Discipline matters more than tooling.
- Multi-entity and multi-currency structures are mapped before any data moves.
- Each department signs off its own dataset — accounting, warehouse, sales.
- A parallel-run period keeps the legacy system answering questions until the numbers prove out.
- Customisations from the old system are inventoried and decided one by one, in writing.
—— Risks
What usually goes wrong — and how we prevent it.
Data lost mid-move
A migration without checkpoints is a leap of faith. We move data in validated batches with a rollback point at every step.
Columns that match, meanings that do not
Fields that look alike do not always mean alike. We map semantics, not just columns, and reconcile record counts after every batch.
Operations frozen for the cutover
A cutover that halts trading costs more than it saves. We run parallel with the legacy system until the numbers reconcile.
—— Pricing
What this costs.
Priced after the source audit, because the cost is driven by data quality rather than record count. We would rather quote late and accurately.
—— Editions & hosting
Community, Enterprise, and where it runs.
The licence and the hosting are separate decisions, and both are yours — we implement either edition and hand over whichever infrastructure you choose.
$0 licence
Odoo Community
Open source and free to license. Covers sales, purchasing, inventory, invoicing, manufacturing and more. You pay for implementation, not rent.
Per user, billed by Odoo
Odoo Enterprise
Adds studio, advanced accounting and localisations, mobile apps and official support. Billed by Odoo directly — never marked up by us.
Odoo.sh · VPS · on-premise
Your server or the cloud
Odoo.sh, a VPS we manage, or your own hardware. We recommend based on your compliance and budget, then document the choice so it stays portable.
—— The toolkit
What this service usually touches.
—— Related
Explore what else we do.
—— FAQ
Questions teams ask about this service.
How much history can we bring?
Technically all of it. Practically, most companies bring two to three years of transactions plus all open items, and archive the rest — it keeps the database fast and the migration affordable.
We are on an old Odoo version. Same process?
Similar, and usually easier — the data model is familiar. The work concentrates on customisations written against the old version, which is where the real cost sits.
How long does a migration take?
A single company moving from an accounting package is usually measured in weeks; a multi-entity ERP with heavy customisation runs a few months. The honest number comes out of the assessment, which is exactly why we run it first. The timeline goes in writing alongside the quote.
Will the business have to stop during the move?
No. Batches are loaded from snapshots while your team keeps working in the old system. The only pause is the final cutover freeze — typically a weekend — and because we rehearse it on staging first, you know its length before you commit to a date.
Can you migrate from a system you have never worked with?
Yes, provided we can get a database backup or a raw export. The source audit exists precisely to learn an unfamiliar data model, and we work at the database level rather than trusting whatever the export menu offers. Undocumented systems take longer to audit, and the quote reflects that honestly.
What happens to the old system after go-live?
Keep it read-only through the parallel run, then archive it. Tax and audit rules in every country we work in require records kept for years, so the archive — read-only access, a full export, or both — is planned as part of the migration, not as an afterthought.
What if we find wrong numbers after go-live?
That is what the parallel-run period is for — the old system is still there to arbitrate. Because every batch has a reconciliation report and a documented mapping, we trace a wrong figure to its batch and correct it at the source rather than patching records one by one. Discrepancies found during the parallel run are fixed under the same written scope.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.