Migrate from Microsoft Dynamics 365 Sales to Twenty CRM

Dynamics Accounts map directly to Twenty Companies. We use accountid as the dedupe key during import. Primary contact association, industry, website, address, and ownership fields migrate 1:1. Account is created before any Contact import so that the parent company lookup is satisfied at Contact insert time. If the Dynamics source has custom account fields beyond the standard set, those require pre-creation in Twenty's UI before the migration job runs.

Dynamics Contacts map 1:1 to Twenty Contacts. The parent accountid resolves to the Twenty Company created in the prior step. Email, phone, job title, lifecycle stage fields, and ownership migrate directly. Contact ownership maps to the Twenty user resolved from the Dynamics Owner mapping. Any custom contact fields require schema pre-creation in Twenty before the migration batch runs.

Dynamics Leads map to Twenty Contacts. We preserve the original lead score, lead source, qualification status, and created-on timestamp as custom fields on the Twenty Contact so that the sales team retains the full pre-conversion history. If the customer uses Dynamics Lead-to-Account mapping with a converted-account reference, we resolve that into the Twenty Company lookup at migration time. Lead conversion dates are stored as custom date fields if the audit trail requires them.

Dynamics Opportunities map to Twenty Deals. Estimated close date, amount, probability, and pipeline stage name migrate directly. The Dynamics sales process and stage probability map to Twenty stage values, with the probability percentage preserved as a custom numeric field if needed for reporting. Loss reason and closed-won reason custom properties migrate as text fields on the Twenty Deal. Parent accountid resolves to the Company created in step one; parent contactid resolves to the Contact created in step two.

Dynamics Quotes do not have a direct Twenty equivalent. We map them as Activity records with a custom activity type discriminator capturing quote ID, total amount, status, and line item summary as structured text fields. If the customer requires full quote document reconstruction, the Quote PDF content (stored in SharePoint or Dataverse) requires a separate document migration pass and re-upload to Twenty. We flag this as a scope item during scoping and the customer decides whether to include it.

Dynamics Orders are mapped as Activity records with a custom activity type discriminator holding order ID, total amount, status, and product line summary. Order fulfillment and invoice linkage to ERP systems is out of scope for migration and requires re-configuration at the destination. We document the full list of Dynamics orders with their IDs, dates, and amounts during scoping so the customer can re-establish ERP integration post-migration.

Dynamics Products map to a product table in Twenty. Product name, SKU, product description, and standard pricing migrate. Bundle relationships and quantity-based discount tiers from Dynamics price lists are captured as structured data in the Twenty product record or as related custom fields. If the Dynamics environment uses complex bundle hierarchies, we flatten them into individual product relationships during the transformation step.

Dynamics price list assignments are stored as related entities on Opportunities and Quote line items. We map price list names and the pricing tiers as structured fields on the Twenty Deal or Activity record. Exact price list enforcement at order time requires a post-migration configuration in Twenty or a third-party pricing integration. We document the full price list matrix for the customer's admin to configure.

All Dynamics activity types (Tasks, Emails, Phone Calls, Appointments, Letters) merge into the single Twenty Activity object. We preserve the original activity type as an activity_type discriminator field, along with subject, description, date, duration, outcome, and owner. The WhoId (Contact or Lead) resolves to the migrated Twenty Contact; the WhatId (Opportunity, Account) resolves to the migrated Deal or Company. Activity timestamps are preserved exactly to maintain the engagement timeline sequence.

Dynamics Notes (plain text annotations) migrate as Comment records in Twenty attached to the relevant parent record (Contact, Company, or Deal). Rich text notes with embedded images require conversion to plain text or image re-upload via Twenty's attachment API. We run the conversion during the transformation step and flag any image-heavy notes for manual review if the customer requires full fidelity.

Dynamics file attachments stored in SharePoint or Dataverse blob storage require a separate download-and-upload pass. We extract the files during the discovery phase, map them to the corresponding Twenty record by the SharePoint relative URL, and re-upload to Twenty's file storage. Large attachment sets (over 10,000 files) require staging and a bulk file migration job coordinated with the customer's IT team. We document the full attachment inventory during scoping with file count, total size, and parent record mapping.

Dynamics custom tables migrate to Twenty custom objects. We detect the current Dynamics tier during scoping and flag any custom table above the Professional 15-table threshold. Custom tables with lookup relationships to Accounts, Contacts, or Opportunities require pre-creation of the matching custom object and fields in Twenty before migration. Custom table data migrates after all standard objects so that parent-record lookups are already satisfied. We coordinate the schema creation with the customer's admin during the scoping phase.

Dynamics Users (licensed individuals) map to Twenty Users by email address. We extract every distinct Owner ID referenced on any migrating record and match by email against the Twenty user table. Any Dynamics Owner without a matching Twenty User goes to a reconciliation queue: the customer's admin provisions the new user before migration resumes, or we map the orphaned records to a designated migration admin account. Inactive Dynamics users require explicit admin decision on whether to provision an inactive Twenty user or reassign ownership before migration.

Power Automate cloud flows and Dataverse business rules are platform-level configurations with no portable representation. We do not migrate them. We deliver a written inventory of every active Power Automate flow (trigger type, conditions, actions, and affected entities) and every Dataverse business rule (entity, field scope, and logic) during the scoping phase. The customer's admin or a Microsoft partner rebuilds them in Power Automate or evaluates native Twenty workflow options post-migration.

Dynamics reports built in the reporting wizard or Power BI and dashboards tied to specific Dataverse entity contexts do not migrate. We export the complete list of active reports and dashboards during scoping, including the report name, entity scope, and last-run date, so the customer's admin can prioritize which reports to rebuild in Twenty or a third-party BI tool post-migration. Custom FetchXML reports require a complete rewrite in the destination query language.