Migrate from Odoo Enterprise to Microsoft Dynamics 365 Business Central

Odoo's res.partner serves as both individual and organizational contact; Dynamics 365 separates these into Account (the company or organization) and Contact (the individual). We split at migration time using Odoo's partner properties: commercial companies and vendors map to Account; individuals and customer contacts map to Contact linked to an Account via the AccountID lookup. The original partner type (customer, vendor, both) is preserved in a custom field partner_type__c on both Account and Contact for segmentation and reporting.

Odoo product variants (size, color, dimension combinations) map to Dynamics 365 Item Variants. The base product template becomes the Dynamics Item with type = Inventory or Service. Variant attributes map to Item Variant records with distinct Item Tracking codes. We preserve the Odoo product routes (make-to-order, dropship) as warehouse setup in Dynamics. SKU (product.default_code) maps to Dynamics Item Number.

Odoo product templates with Bill of Materials (mrp.bom) map to Dynamics Production BOMs. Routing operations (mrp.routing.workcenter) map to Dynamics Work Centers and Machine Centers. We preserve consumption tracking, operation times, and work order dependencies. Note that Odoo's flexible BoM (multi-level, kit products) requires careful sequencing in Dynamics because production order explosion behaves differently between platforms.

Odoo sale orders map to Dynamics Sales Orders with Order Lines, scheduled shipment dates, and payment terms preserved. The Odoo linked delivery (stock.picking) and invoice state map to Dynamics shipment status and invoice status. We resolve the Odoo sales person (user_id) to the Dynamics User, and the Odoo pricelist to the Dynamics Price List at migration time.

Odoo purchase orders map to Dynamics Purchase Orders with vendor, lines, receipts, and bills. Receipt-to-bill matching (stock.picking linked to account_move) is preserved as receipt and invoice status on the Dynamics Purchase Order. Historical partially-received PO states are preserved.

Odoo customer invoices, vendor bills, and journal entries map to Dynamics Posted Invoices and Journal Entries. We separate open (draft) invoices from posted invoices because open invoices require account configuration before they can be posted in Dynamics. Credit notes map to Dynamics Sales Credit Memos. The Odoo fiscal position mapping to tax codes is preserved as Dynamics Tax Groups with country-matched configuration.

Odoo Chart of Accounts entries map to Dynamics G/L Accounts only when the destination instance uses an equivalent country localization. We do not attempt cross-country accounting localization migration without explicitly remapping every affected account code, account type, and tax receipt tag to the destination's country-matched Chart of Accounts template. This step requires the customer's finance team to validate account mapping before migration and is scoped as a configuration-heavy phase.

Odoo stock quants (on-hand quantities), stock moves (history), and pickings (transfers) map to Dynamics warehouse management entries. Lot and serial number traceability migrates to Dynamics Item Tracking Codes. Quant snapshots are migrated as inventory periods to preserve historical on-hand positions without generating new transactions in Dynamics.

Odoo projects and tasks map to Dynamics 365 Project Operations projects and tasks. Sub-task hierarchies, assignees, tags, and stage pipelines migrate. We flag any Odoo project automation (automated actions on project.task) as requiring rebuild in Dynamics Project Service Automation or Power Automate; automated stage logic does not migrate as code.

Odoo employee records (hr.employee) including contracts, department assignments, and employment status migrate to Dynamics 365 Human Resources Workers. Active employment status maps to Dynamics Worker status. Historical payslip data migrates as read-only records. Note that Odoo's payroll module is separate from its HR module; payroll data migration requires specific country localization configuration in Dynamics.

Odoo CRM leads that are unqualified prospects map to Dynamics 365 Leads. Leads that have progressed to a sales opportunity map to Dynamics Opportunities. The Odoo lead status and probability map to Dynamics Lead Status and Opportunity Stage. We flag Enterprise CRM features (CRM Enterprise automation, lead scoring, team selling) that require rebuild in Dynamics Sales Accelerator or Power Automate.

Odoo custom models created via Odoo Studio or ir.model.fields are accessible via xmlrpc and migrate as Dynamics 365 custom tables. We pre-create the destination schema including all field types, lookup relationships, and validation rules before data import. Custom module Python code does not migrate; we document the custom model's logic for the customer's developer to reimplement as a Dynamics extension.

Odoo stores attachments in PostgreSQL (ir_attachment with db_datas) and the filestore directory. We extract both, reconstruct the filestore tree, and relink attachments to their original records in Dynamics SharePoint or as Notes. For Dynamics 365 Business Central, SharePoint integration must be enabled and configured before attachment migration; we handle the setup during the configuration phase.

Odoo fiscal positions (tax and account mapping based on partner country/VAT) are critical for EU VAT compliance. We validate that the destination's country-specific tax codes can represent the same fiscal positions and flag any gaps. Tax Group configuration in Dynamics must be completed before invoice migration to ensure posted invoices carry the correct tax amounts.