Skip to content
Get a quote

Odoo ERP to Business Central migration

We migrate Partners, Products, Sales Orders, Invoices, Projects, Tasks, Manufacturing Orders, and Bills of Materials from Odoo ERP into Microsoft Dynamics 365 Business Central or Finance and Operations, resolving the chart-of-accounts structure, the dimensional accounting model, and the multi-company or multi-address segmentation before any records land in the destination system.

Short answer

FlitStack AI migrates contact and customer or vendors, item and item variants, item ledger entry and warehouse entries, sales headers and sales invoice header and sales cr. memo headers from Odoo ERP to Business Central, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 6-8 weeks.

By

Source Odoo ERP
DestinationBusiness Central
Contact and Customer or VendorItem and Item VariantItem Ledger Entry and Warehouse EntrySales HeaderSales Invoice Header and Sales Cr. Memo Header
Mapped field by field · sample run · one-click rollback

What moves from Odoo ERP to Business Central?

Odoo ERP and Microsoft Dynamics 365 take fundamentally different approaches to accounting architecture, which shapes every migration from the source side.

Read the full summary

Odoo stores accounts, journals, and fiscal positions directly within each record and uses analytic tags for cost segmentation; Dynamics 365 separates the Chart of Accounts into dedicated tables referenced by Dimensions (financial dimension sets) applied at the posting layer. We do not copy Odoo's Automation rules or Odoo Studio customizations as code; we deliver a written inventory of every active automation, Studio-created field, and custom module for the customer's admin team to rebuild in Dynamics. The migration scope covers master data, transactional history, and manufacturing structures, with a dedicated reconciliation phase for posted invoices and stock quants because these are non-editable on the destination platform once committed.

1:N split

res.partner → Contact and Customer or Vendor

Odoo Partners (res.partner) serve as both contacts and companies in a single record with type flags (customer, vendor, employee).

How it maps

Dynamics 365 splits these into separate Contact and Customer/Vendor entities. We extract the partner name and addresses into Dynamics Contact records and the commercial relationship into Customer or Vendor records. Multi-address per partner (billing, delivery, other) maps to separate Contact addresses with distinct Address Type codes. Partner categories map to a Customer Group or Vendor Group lookup that we pre-configure before migration.

1:1

product.template and product.product → Item and Item Variant

Odoo product.template with product.product variants maps to Dynamics Item with variant tracking via the Item Variant Code or Item Cross Reference entities.

How it maps

We preserve the product type (stockable, consumable, service) and map the list_price and standard_cost to Unit Price and Standard Cost on the Item. Vendor-specific pricing in Odoo product.supplierinfo maps to Vendor Catalog entries in Dynamics. Attribute combinations on the source product.template generate separate variant records that we map to Dynamics Item Variants with matching Variant Code values.

mapping

stock.quant → Item Ledger Entry and Warehouse Entry

Odoo stock.quant tracks on-hand quantity per location (stock.location hierarchy).

How it maps

We map the source warehouse locations to Dynamics warehouse codes in the InventLocation table and create Item Ledger Entries reflecting the on-hand quantity at migration cutover. Lot and serial number traceability migrates to Item Tracking Code assignments and Item Tracking Legend entries, but customers must verify lot/serial counts manually post-import because Dynamics requires explicit Item Tracking Code configuration before any tracked inventory can be received.

1:1

sale.order → Sales Header

Odoo Sales Orders map to Dynamics Sales Header records.

How it maps

The order state (draft, confirmed, done, cancel) maps to the Dynamics Document Status (Quote, Order, Released, Cancelled). Odoo order lines map to Sales Line records with product references resolved to Item numbers, quantities preserved, and unit prices transferred from the source order. If Odoo fiscal positions affect tax computation on the source order, we replicate the tax group assignment on the destination sales line to maintain tax correctness at migration.

1:1

account.move (out_invoice, out_refund) → Sales Invoice Header and Sales Cr. Memo Header

Odoo 17+ unified invoices into account.move with move_type distinctions.

How it maps

We map posted out_invoice records to Dynamics Sales Invoice Header, posted out_refund records to Sales Cr. Memo Header, and posted in_invoice records to Purchase Invoice Header. Posted invoices are non-editable in Dynamics 365; we do not attempt to re-import or adjust them after posting. We preserve the Odoo invoice number as the External Document Number and the Odoo invoice date as the Posting Date. Any posted Odoo invoice with a partial payment history must be reconciled by the customer's accountant post-migration against the payment journal entries.

1:1

account.account → G/L Account

Odoo Chart of Accounts (account.account) maps to Dynamics G/L Account records.

How it maps

We transfer the account code, account name, and account type (asset, liability, equity, revenue, expense). However, Dynamics requires that G/L Accounts be assigned an Account Category (Income, Expense, Asset, Liability, etc.) that drives the financial statement grouping, which Odoo does not have. We flag accounts without a clear category assignment during scoping and defer those rows until the customer configures Account Categories in Dynamics.

What moves15 objects
Odoo ERPBusiness Central
  • res.partnerContact and Customer or Vendorsplit
  • product.template and product.productItem and Item Variant1:1
  • stock.quantItem Ledger Entry and Warehouse Entrytransformed
  • sale.orderSales Header1:1
  • account.moveSales Invoice Header and Sales Cr. Memo Header1:1
  • account.accountG/L Account1:1

+ 9 more in the mapping below

How Odoo ERP and Business Central differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionOdoo ERPBusiness Central
Chart of AccountsEmbedded in account.move lines and fiscal positions per moduleDedicated Chart of Accounts table with G/L Account entities and Dimension sets
Company segmentationMulti-company in one PostgreSQL database with res.company hierarchyBusiness Central: separate companies or consolidation journals; FinOps: separate legal entities with inter-company setup
Address architectureone2many address records (contact_address) per partner with type flagsSeparate Address and GAB (Global Address Book) entries; one address per role enforced per entity
Analytic accountingAnalytic accounts and analytic tag lines attached to any documentDimensions (financial dimension sets) assigned at posting level, not line level by default
Invoice vs Sales OrderAccount.move unified model; SO lines linked to invoice lines via invoice_linesSeparate Sales Invoice Header / Sales Line and Sales Order Header / Sales Line entities with order-to-invoice flow
Product variantsproduct.template with product.product variants via attribute combinationsItem tracking by product variants or Item Substitution with separate Item Cross References
Manufacturing scopemrp.production with workorders, BoM with nested components, and routing dependenciesProduction Order and Production Bill of Materials with work centers and capacity resources

What to watch for in a Odoo ERP to Business Central migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Odoo external ID conflicts silently overwrite on re-import

When a CSV import in Odoo includes an ID column matching an existing External ID, Odoo performs an update rather than a create.

How we handle it

If External IDs are not unique or are accidentally reused during a migration run, records silently merge or overwrite. We enforce unique External ID prefixing (e.g. flitstack_migrate_partner_001) before every import batch and cross-reference against the destination Dynamics Customer or Contact number sequence to prevent ID collisions during the Odoo-to-Dynamics extraction phase. This is particularly important when Odoo multi-company setups share partner records across companies.

high

Chart of Accounts mapping requires pre-configuration in Dynamics

Odoo account.account records do not map directly to Dynamics G/L Accounts because Dynamics requires each G/L Account to be assigned an Account Category (Income, Expense, Asset, Liability) and linked to a Posting Setup table that defines the balance account for each combination of Business Posting Group and Product Posting Group.

How we handle it

Odoo's fiscal positions and tax group assignments add a further layer of complexity. We flag every Odoo account that lacks an unambiguous account type during scoping and require the customer to configure Account Categories in Dynamics before any G/L Account records can be imported, because Dynamics will reject any G/L Account insert without a valid Account Category.

medium

Posted invoices are non-editable in Dynamics 365

Odoo posted invoices (account.move with state: posted) are editable only through credit note reversals, but the credit note mechanism differs from Dynamics 365's credit memo and reversal workflow.

How we handle it

We preserve the full Odoo invoice header and line data and create posted Sales Invoice records in Dynamics, but any Odoo invoice with partial payments applied requires manual reconciliation by the customer's accountant post-migration against the payment journal entries. This reconciliation step is a manual activity outside the migration scope and must be scheduled after cutover.

medium

Multi-company Odoo setups require business-unit mapping in Dynamics

Odoo Community and Enterprise support multiple companies in a single database with the res.company hierarchy, where partners and documents can belong to different companies.

How we handle it

Dynamics 365 Business Central requires each company to be either a separate company within the same database or managed via consolidation journals, while Finance and Operations uses separate legal entities. We map Odoo company_ids to Dynamics company or legal entity assignments during scoping, but inter-company transaction mapping (where one Odoo company invoices another) requires explicit inter-company configuration in Dynamics that does not exist in Odoo as a standard setup.

medium

Odoo Studio custom fields have no automated migration path

Odoo Studio creates custom fields stored in ir.model.fields with ttype and selection options that do not exist in the standard Dynamics 365 data model.

How we handle it

We capture the Studio field definitions (name, type, selection options, default values) and map them to Dynamics custom fields (with the appropriate field type selected from the Dynamics metadata) or to extension fields added via the Power Platform ALM pipeline. However, any Studio-created automation, view layout, or business rule built around a custom field must be documented and rebuilt by the customer's admin because we do not migrate Odoo Studio configurations as application code.

How the migration runs

  1. Discovery and Odoo version audit

    We audit the source Odoo instance across version (Community vs Enterprise, major version number, on-premise vs Odoo Online vs Odoo.sh), active modules, custom fields created via Odoo Studio, external ID usage patterns, and multi-company configuration.

    What this step covers

    We identify which Odoo apps are in scope for migration (CRM, Sales, Accounting, Inventory, Manufacturing, Project) and document the relationship between Odoo modules and their corresponding Dynamics 365 modules. The discovery output is a written scope document, an Odoo-to-Dynamics object mapping draft, and a Dynamics 365 edition recommendation (Business Central Essentials, Premium, or Finance and Operations).

  2. Schema pre-configuration in Dynamics

    We pre-configure the Dynamics 365 environment before any data import.

    What this step covers

    This includes provisioning the Chart of Accounts with Account Categories and Posting Setup, setting up Dimensions and Dimension combinations, configuring Tax Groups and Tax Posting Setup, defining Number Sequences for Customer, Vendor, Item, and Sales Invoice, creating Location and Warehouse codes, and establishing the Job and Worker structures for HR data. Any custom fields required to capture Odoo Studio fields are added to the Dynamics metadata before import begins. Schema configuration is deployed to a Dynamics Sandbox first for validation.

  3. Sandbox migration and reconciliation

    We run a full migration into a Dynamics 365 Sandbox environment using production-equivalent data volumes.

    What this step covers

    The customer's finance lead and operations lead reconcile record counts and spot-check 25-50 records against the Odoo source across each object (Partners, Products, Inventory, Orders, Invoices, Projects, Tasks, Production Orders). Any field mapping corrections, dimension assignment errors, or account category gaps identified during sandbox reconciliation are resolved before production migration begins. The customer signs off on the sandbox reconciliation report as the gate for production migration.

  4. Partner and product extraction in dependency order

    We extract Odoo data in record-dependency order.

    What this step covers

    Partners (res.partner) are extracted first because they are referenced by Sales Orders, Invoices, Purchase Orders, and Manufacturing Orders. We resolve partner categories against the Dynamics Customer Group and Vendor Group lookups, and we split partner addresses into separate Contact address lines with distinct Address Type codes. Products (product.template and product.product) follow, with variant tracking configured in Dynamics before product variants are imported. The Odoo External ID mapping table is maintained throughout this phase and cross-referenced against Dynamics primary keys.

  5. Transactional data migration and Bulk API import

    Sales Orders, Purchase Orders, and Manufacturing Orders are imported using the Dynamics 365 Data Management Framework with entity-specific import jobs.

    What this step covers

    We chunk large datasets (over 10,000 records) into batches of 1,000 rows and run import jobs sequentially to avoid rate-limit responses from the Dynamics API. For Finance and Operations migrations, we use the OData batch endpoint with recursive import patterns. Odoo analytic tag lines are transformed into Dynamics Default Dimension assignments using the Dimension Default combination table. Production Orders and BoM structures are imported last because they reference Items and Locations that must already exist.

  6. Cutover, validation, and automation inventory delivery

    We freeze Odoo write access during the cutover window, run a final delta migration of any records modified during the migration window, and enable Dynamics 365 as the system of record.

    What this step covers

    We deliver a written inventory of every Odoo Automation Rule, Studio-created custom field, Odoo Studio view layout, and scheduled action that requires rebuild in Dynamics 365. The inventory includes the Odoo automation name, trigger conditions, actions, and a recommended Dynamics equivalent (Power Automate flow, Power Platform custom field, or configuration change). We do not rebuild automations inside the migration scope; that work is handled by the customer's Dynamics admin or a certified partner.

Odoo ERP Business Central
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · Business CentralRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

6-8 weeksTypical, smaller accounts
14-20 weeksLarge or heavily customised accounts

A quote scales with transactional volume, chart-of-accounts complexity, and manufacturing depth. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Odoo ERP to Business Central →

Why teams move from Odoo ERP to Business Central

  • Odoo's partner ecosystem is significantly smaller than Microsoft's in most regions. Reviewers on Reddit and ERP comparison forums note that certified Odoo implementation partners are scarce outside major markets, which increases implementation risk, inflates hourly rates, and delays go-live for companies that rely on local partner support. Dynamics 365's partner network includes hundreds of certified consultancies with established methodologies, which reduces implementation risk for mid-market companies moving from a platform with fewer local support options.
  • Odoo continues to rebuild core functionality in each major release. The accounting module was fundamentally rewritten in recent versions, and Odoo Studio customizations and custom modules frequently break during version upgrades. Reviewers cite this as a version upgrade trap requiring ongoing developer contracts. Business Central follows a twice-yearly upgrade cycle managed by Microsoft on Azure with a published API surface, reducing the risk of custom code breaking on upgrade and lowering the long-term maintenance burden for companies leaving Odoo.
  • Companies already operating within the Microsoft stack (Microsoft 365, Azure, Power BI, Teams) report that Dynamics 365 Finance and Operations or Business Central integrates more tightly with existing tools than Odoo's open-source integration layer. ERP comparison sites note that Excel-based finance workflows, Power BI reporting pipelines, and Azure AD-based identity management translate directly into Dynamics without middleware, which is a material factor for finance teams that depend on Excel-heavy processes.
  • Odoo's per-module and per-user pricing can escalate unpredictably as teams add modules. Reviewers on ERP research forums and Reddit note that hidden costs emerge when organizations discover per-module licensing nuances or need additional apps beyond the base plan. Dynamics 365 Business Central uses a per-user Essentials or Premium tier model with published pricing, which provides more predictable total cost of ownership for companies planning a multi-year ERP investment.
  • Manufacturing depth at the mid-market and above drives the switch. Odoo covers approximately 80 percent of Dynamics 365 Finance and Operations manufacturing features, but discrete and process manufacturing with advanced routing, capacity planning, and demand forecasting requires capabilities that Odoo does not offer natively. Companies evaluating ERP for manufacturing at scale consistently move to Dynamics 365 because the production planning, shop floor execution, and quality management modules are purpose-built for regulated and complex manufacturing environments.

Questions, answered

Odoo ERP to Business Central migration questions

How long does an Odoo ERP to Microsoft Dynamics 365 migration take?

Most Odoo ERP migrations land between six and eight weeks for accounts under 50,000 Partners, 20,000 Products, and no active Manufacturing module. Migrations that include Manufacturing Orders, multi-level BoM structures, multi-company configurations, or large historical posted invoice volumes (over 100,000 account.move records) move to fourteen to twenty weeks because of chart-of-accounts pre-configuration, dimensional mapping design, workorder re-sequencing, and the posted-invoice reconciliation phase. Odoo Community self-hosted migrations may require additional time for database extraction and environment preparation.

Do Odoo Automation Rules and Odoo Studio customizations migrate to Dynamics 365?

No. Odoo Automation Rules and Odoo Studio configurations are application-level customizations that do not have a direct equivalent in Dynamics 365. We do not migrate them as code. We deliver a written inventory of every active Automation Rule and Studio-created field, view, or action with its trigger conditions, action steps, and a recommended Dynamics 365 equivalent (Power Automate, custom field via Power Platform, or configuration change). The customer's Dynamics admin or a certified Microsoft partner rebuilds them post-migration. Odoo workflows (estate actions, server actions, base.automation) are included in this inventory.

Can we migrate our Odoo Manufacturing Orders and Bills of Materials to Dynamics 365?

Yes. Odoo Manufacturing Orders (mrp.production) and Bills of Materials (mrp.bom) migrate to Dynamics 365 Production Orders and Production BOM records. We transfer the production state, product to manufacture, component lines, and routing references. However, workorder-specific trackings, time allocations, and capacity planning assignments require re-configuration in Dynamics because Dynamics Operations uses a separate routing and work center model that Odoo does not expose via its standard API. Customers with complex routing dependencies should plan for a separate configuration sprint after the migration data is loaded.

How do we handle Odoo posted invoices in Dynamics 365?

Posted Odoo invoices (account.move with state: posted) migrate as posted Sales Invoice or Purchase Invoice records in Dynamics 365. They cannot be edited after posting in either platform, but the credit note reversal mechanism differs. Any Odoo posted invoice with partial payments applied requires a manual reconciliation step by the customer's accountant post-migration because Dynamics enforces payment application through its own Payment Journal and Customer Ledger Entries workflow. We flag these records during migration scoping and deliver a separate payment reconciliation guide as part of the cutover documentation.

What happens to our Odoo multi-company setup in Dynamics 365?

Odoo's multi-company configuration (res.company hierarchy sharing a single PostgreSQL database) maps to either separate companies within a Business Central database or separate legal entities in Dynamics 365 Finance and Operations. We map each Odoo company to a Dynamics company or legal entity during scoping. Inter-company transactions (where one Odoo company invoices another) require explicit inter-company configuration in Dynamics that does not exist in Odoo as a standard setup; we flag these records and deliver a separate inter-company setup guide. Companies with three or more Odoo legal entities should plan for a dedicated configuration phase post-migration.

How does FlitStack AI handle the Odoo Chart of Accounts migration to Dynamics 365?

Odoo account.account records migrate to Dynamics G/L Account records, but Dynamics requires each G/L Account to be assigned an Account Category (Income, Expense, Asset, Liability, etc.) and linked to a Posting Setup table that defines the balance account for each combination of Business Posting Group and Product Posting Group. We map the Odoo account code, name, and type directly, flag accounts without a clear category assignment during scoping, and require the customer to configure Account Categories in Dynamics before any G/L Account records can be imported. The Dynamics Data Management Framework rejects any G/L Account insert without a valid Account Category.

Get a quote

Moving from Odoo ERP to Business Central?

Tell us roughly how many records and objects you have. We scope the mapping and the Business Central setup with you, then send a quote.

Get a quote