Odoo Database Split

One database, many companies — sometimes that needs to change

A multi-company Odoo database is convenient until it isn’t. Divestitures, subsidiary independence, data-isolation requirements, and pure performance have all driven clients to ask us to split.

What we actually do

• Map every record to its owning company.
• Decide with you how shared records are handled (contacts used everywhere, products shared across the group, account templates).
• Provision one target database per company being extracted.
• Migrate records preserving referential integrity on each target.
• Reconcile inter-company transactions so your finance team can close them out cleanly.
• Run UAT per target and cut over on a schedule.

Shared-record strategies we support

Strategy	When it fits
Duplicate into each target	Contacts and products your teams edit independently going forward
Keep a shared source	A central product catalog maintained by the group, with downstream syncs
Curate per target	Sensitive contacts or product lines that shouldn’t cross company boundaries

Why a split without us is painful

The hard part isn’t the split — it’s the edge cases. Accounting periods straddling the split date, manufacturing orders with components from one company and a customer from another, subscriptions billed centrally, stock transfers in flight. We inventory every edge case and resolve it before production migration.