Odoo Database Merge

Consolidating databases is messy. It doesn’t have to be risky.

Merging Odoo databases is where the hard problems live: ID conflicts, master-data duplication, chart-of-accounts misalignment, different customization stacks, different module versions, different integrations. We handle it as a structured engagement, not a single migration script.

What the merge actually includes

• ID conflict resolution — two source databases can both have an res.partner with ID 42. We rewrite IDs on one or both sides so the target database has a single clean namespace, and preserve every foreign-key reference across the rewrite.
• Master data reconciliation — customers, vendors, products, employees, chart of accounts, fiscal positions, taxes. Duplicates go through a match-and-confirm step before the target load.
• Chart of accounts unification — a common CoA that covers all sources, with a per-source mapping you sign off on.
• Module consolidation — where source databases have different customizations, we decide together which behavior wins in the target, or we port both behaviors as configurable.

Two shapes for a merge

1. Full historical — all records from every source become records in the target. Reporting continues to work against the unified history.
2. Forward-only — the new multi-company database starts from the merge date, and the sources are archived for audit but not actively used. Faster and cleaner where historical reporting against legacy entities isn’t required.