Migrate from Microsoft Dynamics 365 Sales to Odoo CRM

Dynamics 365 Accounts map to Odoo Companies, which serve as the organizational parent record for Contacts. 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.

Dynamics 365 Contacts map directly to Odoo Contacts. 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.

Dynamics 365 Leads map to Odoo CRM Leads. 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.

Dynamics 365 Opportunities map to Odoo CRM Opportunities (the crm.lead record type of type=opportunity). 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.

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. 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.

Dynamics 365 Quotes map to Odoo Sale Orders in the Quotation state. 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.

Microsoft Dynamics 365 Sales Orders map to Odoo Sale Orders in the Sale Order state (confirmed, not quotation). We preserve the Order Number, line items, quantities, pricing, taxes, and the parent Account and Opportunity references. The Order's state (Fulfilled, Invoiced, Cancelled) maps to the corresponding Odoo Sale Order state. If the customer uses Odoo Accounting, the Sale Order's Invoice Status is set to indicate whether an invoice has been created.

Dynamics 365 Products map to Odoo Products. We preserve Product Name, Product Number (mapped to Odoo's Reference or Barcode field), Unit of Measure, Product Type (Stockable, Consumable, Service), and Cost (Standard Price). Dynamics Product Type (Sales, Miscellaneous) maps to Odoo's Product Type selection. The Product's default vendor (Vendor Price on Dynamics) maps to Odoo's vendor on the Purchase tab of the Product form.

Dynamics 365 Price Lists map to Odoo Pricelists. Each Price List becomes an Odoo Pricelist with the same name and type (Sales Pricelist). Price List Item rows map to Odoo Pricelist Rule lines: Dynamics Unit Price becomes the Base Price on the rule, quantity-based discounts map to Odoo's Min Quantity and Price computation fields, and percentage discounts map to Odoo's Percentage (discount) field. Currency on the Dynamics Price List maps to the Odoo Pricelist's Currency setting. If the customer uses multiple currencies, we configure a product.category-based pricelist fallback in Odoo before migration.

Dynamics 365 Activities (Tasks, Emails, Phone Calls, Appointments) map to Odoo Mail Activity records linked to the target CRM record. The activity type, subject, description, date, and duration transfer to Odoo's activity_type_id, summary, note, date_deadline, and duration fields. OwnerId from Dynamics maps to Odoo's user_id on the activity, which drives the sales rep's activity list. Activity records that reference inactive Dynamics owners are mapped to a designated migration administrator user at the destination to avoid orphaning.

Dynamics 365 Notes migrate as Odoo Mail Messages with a note subtype, attached to the parent CRM record (Company, Contact, Lead, or Opportunity). The Note body transfers as plain text or HTML. Attachments stored in SharePoint or Dataverse blob storage are downloaded during extraction and uploaded to Odoo as ir.attachment records linked to the same parent record via res_model and res_id. Attachment file names and content types are preserved.

Dynamics 365 Users who own CRM records map to Odoo Users. We match by email address as the primary key. Each Dynamics Business Unit maps to an Odoo Access Control Group (res.groups) to replicate visibility boundaries. Inactive Dynamics Users without corresponding Odoo User records are placed in a reconciliation queue; the customer's Odoo administrator provisions the missing users before the migration resumes. OwnerId references on Opportunities, Activities, and Notes are resolved against this user map before import.

Dynamics 365 custom tables above the Professional tier's 15-table limit require schema simplification or Enterprise licensing before migration. For environments within the limit, each Dynamics custom table maps to an Odoo custom model created via Odoo Studio before migration: the table name becomes the model name (x_<tablename>), columns become fields, and lookup relationships to standard entities (Account, Contact, Opportunity) map to Odoo Many2one fields on the custom model. We coordinate with the customer's admin to pre-create all destination custom models and fields in a staging environment before the import job runs.

Dynamics 365 Territory management (available on Enterprise tier only) maps to Odoo Sales Teams or to Tags on CRM records. Each Dynamics Territory becomes an Odoo Sales Team with its own pipeline and member list, or alternatively, the Territory name is stored as a tag on Opportunities and Accounts. The customer selects the mapping strategy during scoping based on whether they plan to use Odoo's multi-team reporting features. Territory hierarchies flatten to a single level in the destination, as Odoo Sales Teams do not support nested hierarchies natively.