How to split a multi-company Odoo database
Divestitures, carve-outs, and over-grown multi-company setups all eventually need one company pulled cleanly out of a shared database. Here is how the split actually works — and the shared records that trip teams up.
Splitting a multi-company Odoo database is one of the migration shapes most partners will not touch. It is fiddly, the edge cases are unforgiving, and a sloppy job leaves you with broken accounting on both sides. Done properly, it is methodical and safe. Here is the shape of the work.
Why businesses need a split
- Divestiture — you are selling a company and the buyer needs its data, cleanly separated from yours.
- Carve-out — a division is becoming its own legal entity with its own systems.
- Untangling — a multi-company setup grew organically and now one company needs to stand alone for performance, governance, or audit reasons.
What makes it hard: shared records
In a multi-company database, plenty of records are shared across companies, and the database does not always make the boundaries obvious. The split has to make a clean decision about each:
- Partners (customers/vendors) — often shared. Which move, which are copied, which stay?
- Products and pricelists — frequently global. The extracted company needs its own copy.
- Chart of accounts and journals — company-specific, but inter-company entries link them.
- Users and access rights — who follows the company, who keeps access to what remains.
- Inter-company transactions — the hardest part. Open balances between the two companies have to be settled or represented correctly on both sides after the split.
How we run it
- Inventory and decision matrix. Every shared model gets an explicit rule: move, copy, or leave. No record is split on a guess.
- Extract to a fresh database. The departing company is rebuilt in its own clean database with only its data and a copy of what it shares.
- Reconcile both sides. Accounting on the remaining database and the new one must both balance. Inter-company open items get settled or carried as opening balances.
- Validate before anyone goes live. Trial balances, AR/AP aging, and stock valuation are checked on both databases against the pre-split state.
The non-negotiables
- A documented decision for every shared model — never improvise.
- A full rehearsal on replicas of both outcomes before the real cutover.
- A data-loss and reconciliation report signed off by finance on both sides.
- A tested rollback path.
This is precision work. Our database split service covers the full path, and the inverse — consolidating after an acquisition — is its sibling, the database merge. If you are weighing a split, the project estimator captures the variables that drive complexity.