Skip to content
Get a quote

Dynamics 365 to Odoo CRM migration

We migrate Accounts, Contacts, Leads, Opportunities, and Activity history from Microsoft Dynamics 365 Sales into Odoo CRM, preserving pipeline stage histories and owner assignments through the Dataverse Web API, while flagging every Power Automate workflow and report that requires manual rebuild at the destination because Odoo does not import these as code.

Short answer

FlitStack AI migrates companies, contacts, leads, opportunities and pipeline and stages from Dynamics 365 to Odoo CRM, 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-10 weeks.

By

Source Dynamics 365
DestinationOdoo CRM
CompanyContactLeadOpportunityPipeline and Stage
Mapped field by field · sample run · one-click rollback

What moves from Dynamics 365 to Odoo CRM?

Moving from Microsoft Dynamics 365 Sales to Odoo CRM means leaving the Microsoft Dataverse ecosystem for an open-source, PostgreSQL-backed platform with a fundamentally different CRM object model.

Read the full summary

Dynamics 365 separates Leads from Opportunities with an explicit qualification pipeline; Odoo CRM uses a unified Opportunities object with a Stage field that covers both unqualified and qualified deals. We resolve that structural difference during scoping, map Accounts to Companies, preserve opportunity probability and close-date history, and use the Dataverse bulk export API with batch chunking for large datasets. Custom fields require pre-creation in Odoo's Studio interface before our import job writes data. Power Automate workflows, Dataverse plug-ins, and Dynamics reports do not migrate; we deliver a written inventory of every active automation and report that the customer's Odoo admin rebuilds using Odoo Studio and automated actions. Odoo's per-app pricing model, starting at €25 per user per month for the CRM app, typically reduces subscription costs by 40-70 percent compared to Microsoft Dynamics 365 Sales Professional at $80 per user per month after the October 2024 increase.

1:1

Account → Company

Dynamics 365 Accounts map to Odoo Companies, which serve as the organizational parent record for Contacts.

How it maps

We preserve Account Name, Industry, Website, Address fields, and the primary contact association. Odoo Companies do not have a native Account Number field, so we map the Dynamics Account Number to the Company's Company Registry or VAT field, or to a custom Char field depending on the customer's use of those identifiers. The Company is created before any Contact import so that the Contact's Company_id lookup resolves at insert time.

1:1

Contact → Contact

Dynamics 365 Contacts map directly to Odoo Contacts.

How it maps

We preserve FirstName, LastName, Email, Phone, Mobile, Job Title, and the parent Company lookup. The Dynamics ParentContact relationship (for assistant or spouse links) maps to a custom Many2one field or is flattened into a note. Contact ownership (OwnerId) maps to the Odoo Salesperson field on the contact record, which controls activity assignment and pipeline visibility under Odoo's access control model.

1:1

Lead → Lead

Dynamics 365 Leads map to Odoo CRM Leads.

How it maps

We preserve Lead Score, Lead Source, the qualification status fields (state, status reason), and all custom lead fields. The Dynamics Lead-to-Opportunity conversion produces a new Opportunity record; we map both the pre-conversion Lead and the resulting Opportunity separately so that the full qualification history is preserved even after the customer transitions the opportunity through the pipeline.

1:1

Opportunity → Opportunity

Dynamics 365 Opportunities map to Odoo CRM Opportunities (the crm.lead record type of type=opportunity).

How it maps

We preserve the Estimated Revenue (Expected Revenue), Close Date (Date Deadline), Probability (mapped to Odoo's probability percentage per stage), and StageName (mapped to the Odoo Stage ID within the sales team pipeline). Loss Reason and Win Reason from Dynamics custom fields become Odoo Lost Reason values or custom Char fields. The parent Account maps to the Opportunity's Partner_id (the linked Company), and the primary Contact maps to Partner_id's primary contact role.

configuration

Pipeline and Stage → Pipeline and Stage

Dynamics 365 pipeline configurations (one or more pipelines with named stages and probability percentages) map to Odoo Sales Teams and Stage configurations within each team.

How it maps

We create an Odoo Sales Team per Dynamics pipeline, map each Dynamics stage name to a corresponding Odoo Stage with the same sequence order, and preserve the probability percentage as the Odoo Stage's probability value. Stages with no Odoo equivalent are created as custom stages before migration.

1:1

Quote → Quotation

Dynamics 365 Quotes map to Odoo Sale Orders in the Quotation state.

How it maps

We preserve the Quote Number, Description, line items with product references and quantities, pricing from the assigned Price List, Discount, and Tax fields. The Quote's expiration date maps to Odoo's Valid Until field. The parent Account and Opportunity lookups map to the Sale Order's Partner_id and Opportunity_id (if the Odoo CRM Opportunity is linked to the Sale Order via the sale_crm module). Revoked or expired Quotes in Dynamics are imported as Cancelled or Lost Odoo quotations.

What moves14 objects
Dynamics 365Odoo CRM
  • AccountCompany1:1
  • ContactContact1:1
  • LeadLead1:1
  • OpportunityOpportunity1:1
  • Pipeline and StagePipeline and Stagetransformed
  • QuoteQuotation1:1

+ 8 more in the mapping below

How Dynamics 365 and Odoo CRM 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.

DimensionDynamics 365Odoo CRM
Lead vs pipeline modelSeparate Lead and Opportunity objects with explicit qualification and convert flowUnified Opportunities object with Stage field covering both unqualified and qualified pipeline stages
Object namingAccounts, Contacts, Leads, Opportunities, Quotes, Orders, InvoicesCompanies, Contacts, Leads, Opportunities (CRM app), Quotations, Sales Orders
Customization ceilingProfessional tier caps at 15 custom tables; Enterprise and Premium allow unlimitedAll tiers support unlimited custom fields via Studio; no hard table count limit
Pricing modelPer-user per month at $65-$105+; $15 increase from October 2024; mandatory partner overheadPer-user per month from €25 for CRM app on Standard; Community edition free with no per-user fees
Workflow and automationPower Automate flows, Dataverse plug-ins, and business rules at the platform layerAutomated Actions, Server Actions, and Odoo Studio workflows; no native Power Automate import
Data portabilityLocked to Dataverse; data export requires API or third-party toolsPostgreSQL backend; data portable via direct database access or XML/CSV export
ERP bundlingSeparate Sales, Finance, Supply Chain modules at per-module pricingCRM, Sales, Accounting, Inventory, Project, and Manufacturing share one database and one user model

What to watch for in a Dynamics 365 to Odoo CRM migration

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

high

Odoo requires Studio pre-creation of custom fields before API import

Odoo does not allow creating custom fields via the XML-RPC API at migration time — all custom fields must first exist in the database schema through Odoo Studio or Python model definition before any import job writes data to them.

How we handle it

This is the opposite of Dynamics 365, which allows field creation through the UI but requires the same pre-creation step. We coordinate with the customer's Odoo administrator during the discovery phase to pre-create every target custom field, custom model, and field type (Char, Float, Date, Many2one, etc.) in a staging Odoo instance. Any missing fields discovered during the migration job are logged and deferred to a schema creation window before that object type is retried. Skipping this step results in silent field drops on import.

high

Dynamics Power Automate workflows do not migrate to Odoo Automated Actions

Power Automate flows built on Dataverse connectors, Dynamics triggers, and Power Platform actions have no migration path to Odoo.

How we handle it

Odoo uses its own action system (Automated Actions, Server Actions, UI Actions) with different triggers, conditions, and effects. We do not import flows as code. We audit every active Power Automate flow during discovery, document its trigger, conditions, actions, and the Odoo equivalent Automated Action or workflow rule, and deliver the inventory to the customer's admin for rebuild. Dataverse plug-ins, business rules, and real-time workflows are included in this inventory.

high

Dynamics reports and dashboards require full rebuild in Odoo

Reports and dashboards built in Dynamics 365 using FetchXML, Power BI, or the native reporting module do not port to Odoo.

How we handle it

The data model differs (Dataverse entity relationships versus Odoo's PostgreSQL schema), and Odoo Reporting uses its own views, groupby, and measure definitions. We export a list of all active Dynamics reports and their parameters during discovery and deliver it to the customer's Odoo admin as a rebuild specification. Odoo's native reporting, Pivot, and Graph views handle most CRM reporting needs; Power BI connectivity is available as an optional integration for customers who need cross-module analytics.

medium

Multi-currency and pricing precision require explicit mapping

Dynamics 365 stores monetary values with full decimal precision from the associated Price List currency.

How we handle it

Odoo's monetary fields store values in the company's default currency, and pricing rules compute at display time. If the customer's Dynamics environment uses multiple currencies on Price Lists (common for international sales), we need to confirm the Odoo company's currency and configure Odoo's Multi-Currency settings before migrating Price List data. Exchange rates are pulled from the Odoo.currency.rate table or an external rate provider. Any Dynamics monetary field imported into Odoo's Float field without currency context may display incorrectly if the company currency differs from the original Price List currency.

medium

Activity records with inactive owners require a fallback mapping

Dynamics 365 assigns every Activity (Task, Email, Phone Call, Appointment) an OwnerId from the User table.

How we handle it

When the owner is inactive or unlicensed at the destination, Odoo will either reject the activity or assign it to a null user, removing it from the sales rep's activity list. We audit all OwnerId values during discovery, identify inactive Dynamics users, and map them to a designated migration administrator user in Odoo or to a dedicated Legacy Owner contact record that serves as the placeholder for inactive user activities. This is applied consistently before the activity migration phase begins.

How the migration runs

  1. Discovery and environment assessment

    We audit the source Microsoft Dynamics 365 Sales environment across tier (Professional, Enterprise, Premium), custom table count, active Power Automate flows, pipeline count and stage structure, engagement volume (activity records), price list complexity (currencies, quantity breaks), and any Dataverse tables above the 15-table Professional tier limit.

    What this step covers

    We pair this with an Odoo environment assessment: edition (Community free with in-house hosting versus Odoo Online/Standard at €25+ per user per month), enabled apps (CRM, Sales, Accounting, Inventory), and any existing Odoo configuration that must be preserved. The discovery output is a written migration scope, a custom field inventory, a Power Automate flow inventory, and an Odoo edition recommendation.

  2. Odoo schema pre-build in staging

    We coordinate with the customer's Odoo administrator to pre-create all destination custom fields, custom models, stage configurations, sales team structures, and pricelists in a staging Odoo database.

    What this step covers

    This includes creating every Dynamics custom field as an Odoo Studio field with the correct type (Char, Float, Date, Many2one, etc.), defining pipeline stages that match Dynamics stage names and probabilities, and configuring sales teams that map to Dynamics territories or business units. Schema is validated in staging before any production migration begins. We also configure Odoo's Multi-Currency settings if the source uses multiple Price List currencies.

  3. Dataverse bulk export and data extraction

    We extract all CRM records from Dynamics 365 using the Dataverse Web API with batch operations and page-size limits (default 5,000 records per page).

    What this step covers

    For large datasets (over 100,000 records), we use the Dataverse bulk export with delta queries to chunk the extraction and avoid timeout. The export runs in phases in dependency order: Accounts, Contacts, Leads, Opportunities, Products, Price List Items, Quotes, Orders, Activities. We flag any records with invalid OwnerId references during extraction and produce an owner reconciliation list for the customer's admin to resolve before the import phase.

  4. Sandbox migration and reconciliation

    We run a full migration into the staging Odoo database using production-like data volume.

    What this step covers

    The customer's RevOps lead or Odoo administrator reconciles record counts against the Dynamics source (Accounts in, Companies in; Contacts in, Contacts in; Opportunities in, Opportunities in; Activities in, Activities in), spot-checks 25-50 randomly selected records for field accuracy, and validates that pipeline stage assignments, owner assignments, and monetary values are correct. Any field mapping corrections are applied to the migration scripts at this stage. This is the last validation gate before production migration.

  5. User provisioning and owner reconciliation

    We extract every distinct Dynamics User referenced on CRM records (OwnerId) and match by email against the destination Odoo User table.

    What this step covers

    Users without a matching Odoo account are placed in a reconciliation queue, and the customer's Odoo administrator provisions the missing users. Inactive Dynamics owners are mapped to the designated migration administrator or Legacy Owner placeholder. OwnerId references on all record types are resolved against this user map before each import phase. Migration cannot proceed past this step because Opportunity, Activity, and Note records require a valid user_id at insert.

  6. Production migration in record dependency order

    We run production migration in strict dependency order: Companies (from Accounts), Contacts (with Company_id resolved), Leads, Opportunities (with Partner_id and user_id resolved, stage mapped to Odoo Stage ID), Products and Pricelists, Quote/Quotation records, Sale Orders, Activity history (Tasks, Emails, Phone Calls, Appointments as Odoo Mail Activity records via XML-RPC), Notes and Attachments.

    What this step covers

    Each phase emits a row-count reconciliation report and a validation summary before the next phase begins. A final delta pass captures any records modified during the migration window.

  7. Cutover, validation, and automation rebuild handoff

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

    What this step covers

    We deliver the Power Automate flow inventory document (with Odoo Automated Action equivalents documented per flow) and the Dynamics report list (with Odoo reporting rebuild notes) to the customer's Odoo administrator. We support a two-week hypercare window where we resolve any record reconciliation issues raised by the customer's sales team. Rebuilding Power Automate flows as Odoo Automated Actions, rebuilding Dynamics reports in Odoo, and training sales teams on Odoo navigation are outside the standard migration scope and are handled as separate engagements or internal admin tasks.

Dynamics 365 Odoo CRM
  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 · Odoo CRMRollback 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-10 weeksTypical, smaller accounts
14-22 weeksLarge or heavily customised accounts

A quote scales with record volume, custom field count, pipeline complexity, and the number of Power Automate workflows requiring written documentation. Odoo subscription cost (typically €25-€70 per user per month depending on the apps enabled) sits outside the migration fee and replaces the customer's Dynamics 365 licensing. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Dynamics 365 to Odoo CRM →

Why teams move from Dynamics 365 to Odoo CRM

  • Odoo delivers 40-70 percent lower total cost of ownership than Dynamics 365 according to migration consultants and TCO analyses. The savings come from per-app rather than per-module pricing (CRM app from €25 per user per month versus Microsoft Dynamics 365 Sales Professional at $80 per user per month after the October 2024 increase), no mandatory implementation partner fee (Odoo Studio enables in-house admins to build custom fields and automations), and PostgreSQL database portability that eliminates Microsoft Azure lock-in. Organizations with 20-100 sales users typically cut their annual CRM subscription by $60,000-$200,000 after migrating to Odoo.
  • Dynamics 365 requires certified implementation partners to configure the system properly, adding 30-50 percent to total project cost beyond licensing fees. Odoo's modular architecture and Studio interface allow mid-sized businesses to implement only the CRM applications they need without mandatory partner involvement, and customization can be handled in-house by technical administrators or Odoo community partners at lower rates than Microsoft-certified consultants.
  • Steep learning curves and complex role hierarchies in Dynamics 365 create adoption friction that Odoo's straightforward interface reduces. Reviewers on G2 and in comparison guides cite steep onboarding requirements and the need for dedicated IT support as reasons teams move to Odoo, which offers a more intuitive navigation model and faster time-to-value for sales teams without dedicated CRM administrators.
  • Implementation timelines for Dynamics 365 typically span 6-12 months with significant consulting overhead, while Odoo deployments for CRM-focused migrations commonly complete in 2-4 months. The shorter implementation cycle reduces the total project cost and allows sales teams to start using the new CRM faster, which is particularly important for organizations that are mid-transition from an undersized or misconfigured Dynamics environment.
  • Microsoft's mandatory $15 per user per month price increase across all Microsoft Dynamics 365 Sales tiers from October 2024 applies at renewal for existing customers, creating a bill shock for organizations already considering a switch. Migration cutover aligned with the renewal cycle allows organizations to avoid one additional invoice cycle at the higher rate while replacing that subscription with Odoo's lower-cost model.

Questions, answered

Dynamics 365 to Odoo CRM migration questions

How long does a Microsoft Dynamics 365 Sales to Odoo CRM migration take?

Most migrations land between six and ten weeks for environments under 20,000 Accounts, 40,000 Contacts, and 5,000 Opportunities with straightforward pipeline stage mapping and no custom Dataverse tables above the 15-table limit. Migrations with large engagement histories (over 300,000 activity records), complex multi-currency price list hierarchies, custom Dataverse tables, or parallel ERP scope (moving Dynamics Finance or Supply Chain to Odoo Accounting or Inventory) extend to fourteen to twenty-two weeks because of Dataverse bulk export throttling, Odoo Studio schema pre-build time, and the Power Automate inventory documentation scope.

Do Dynamics 365 Power Automate workflows migrate to Odoo?

No. Power Automate flows built on Dataverse connectors, Dynamics triggers, and Power Platform actions have no migration path to Odoo. Odoo uses its own Automated Actions, Server Actions, and UI Actions with different trigger models, conditions, and effect types. We do not import workflows as code. We deliver a written inventory of every active Power Automate flow with its trigger, conditions, actions, and a recommended Odoo Automated Action equivalent. The customer's Odoo administrator or an Odoo partner rebuilds them post-migration. Dataverse plug-ins, business rules, and real-time workflows are included in this inventory. Power Automate flows that integrate Dynamics with non-Microsoft systems (third-party SaaS, SharePoint, Azure) require a separate integration review because the destination endpoints may also change.

Can we migrate Dynamics 365 Reports and Dashboards to Odoo?

No. Dynamics 365 Reports built in the native reporting module, FetchXML, or Power BI do not migrate to Odoo because the underlying data models are structurally different. We export a complete list of all active Dynamics reports and dashboards during discovery and deliver it as a rebuild specification to the customer's Odoo administrator. Odoo's native reporting views, pivot tables, and graph visualizations handle most CRM reporting needs for pipeline, win/loss, and activity analysis. Customers who rely on Power BI for cross-module analytics can reconnect Power BI to Odoo's PostgreSQL database as a separate integration step.

Do we lose historical activity data (tasks, emails, calls, meetings) when moving to Odoo?

No. We migrate the full engagement history from Dynamics 365 Activities to Odoo Mail Activity records using Odoo's XML-RPC API. Each activity type (Task, Email, Phone Call, Appointment) maps to the corresponding Odoo activity_type_id. The activity subject, description, date, duration, and owner transfer to the Odoo record. Activity records with inactive Dynamics owners are mapped to a designated migration administrator user at the destination to prevent orphaning. Attachments stored in SharePoint or Dataverse blob storage are downloaded and re-uploaded as Odoo ir.attachment records linked to the parent CRM record.

How does the Lead and Opportunity model difference affect migration?

Dynamics 365 separates Leads (unqualified prospects) from Opportunities (qualified deals with an Account and revenue estimate). Odoo CRM uses a single Opportunities object (crm.lead with type=opportunity) where both unqualified and qualified deals live in the same table with a Stage field distinguishing pipeline position. We handle this by mapping Dynamics Leads to Odoo Opportunities at the Lead stage (Stage 0 or a dedicated New stage) and mapping Dynamics Opportunities to Odoo Opportunities at the corresponding qualified stage. The original Dynamics Lead Score and Status are preserved as Odoo custom fields so that qualification history is not lost. Leads that were never converted to Opportunities in Dynamics are migrated as Odoo Opportunities in the early pipeline stages with a Lost Reason of Not Converted if applicable.

What happens to Dynamics 365 custom tables above the Professional tier's 15-table limit?

Sales Professional enforces a hard cap of 15 custom tables. If the source environment has more than 15 custom tables, records referencing tables above the limit cannot be imported without either an Enterprise license upgrade or schema simplification before migration. We detect the exact count during scoping, identify the tables above the limit, and present the customer with a concrete list of tables to merge or drop. Schema simplification typically involves combining related tables into a single table with a Type or Category field, or archiving legacy tables that are no longer actively used. We do not proceed past scoping until the customer has confirmed their custom table strategy, because exceeding the 15-table limit at migration time will result in record rejection on the affected custom object imports.

Can FlitStack AI migrate the ERP portion (Dynamics Finance or Supply Chain) alongside the CRM migration?

Yes. A parallel ERP migration is a common pattern for organizations moving from a full Dynamics 365 suite to Odoo. The ERP scope (General Ledger, Subledgers, Accounts Payable/Receivable, Inventory, Purchase Orders) follows a separate migration track because it requires additional financial validation, chart of accounts mapping, and open invoice reconciliation that CRM data alone does not. We scope the ERP and CRM migrations independently and run them sequentially or in parallel based on the customer's cutover preference and internal resource availability. The combined CRM and ERP migration timeline typically extends to twenty-two to thirty weeks because of the additional financial data validation requirements and the chart of accounts reconciliation phase.

Get a quote

Moving from Dynamics 365 to Odoo CRM?

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

Get a quote