Skip to content
Get a quote

Twenty CRM to Dynamics 365 migration

We migrate People, Companies, Opportunities, Tasks, and Notes from Twenty CRM into Microsoft Microsoft Dynamics 365 Sales , resolving Twenty's dependency-ordered import sequence, its 20,000-record export cap, and the soft-delete uniqueness constraint before any data moves across.

Short answer

FlitStack AI migrates accounts, contacts, opportunities, tasks and annotations from Twenty CRM to Dynamics 365, 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: 3-5 weeks.

By

Source Twenty CRM
DestinationDynamics 365
AccountContactOpportunityTaskAnnotation
Mapped field by field · sample run · one-click rollback

What moves from Twenty CRM to Dynamics 365?

Moving from Twenty CRM to Microsoft Microsoft Dynamics 365 Sales is a structural migration across platforms with different data models and API constraints.

Read the full summary

Twenty's five standard objects (People, Companies, Opportunities, Tasks, Notes) plus any Custom Objects require explicit mapping to Dynamics 365's Account, Contact, Opportunity, Task, and Annotation entities backed by Dataverse. We handle the import sequencing requirement where Companies must load before People (which reference companyId foreign keys), pre-configure Twenty's export view to expose all columns before extraction, and account for Twenty's soft-delete uniqueness constraint so that restored records do not create duplicates in Dynamics 365. Dynamics 365's tiered licensing (Sales Professional at $65/user/month, Sales Enterprise at $105/user/month) requires careful role-mapping against Twenty's unlimited-user self-hosted deployments. Workflows, email sequences, and automations in Twenty do not migrate; we deliver a written inventory for the customer admin to rebuild in Dynamics 365.

1:1

Companies → Account

Twenty Companies map directly to Dynamics 365 Account.

How it maps

The domain field in Twenty becomes the Account Website field and is used as a deduplication key during import. Account is imported first in the migration sequence because both People (via companyId) and Opportunities reference it. We pre-create the destination Account schema including industry, size, and location fields before any dependent imports begin.

1:1

People → Contact

Twenty People map to Dynamics 365 Contact.

How it maps

Email is the unique reference key used for deduplication matching. We resolve the companyId foreign key against imported Account records to populate the Contact's parentcustomerid_account AccountId lookup at migration time. Job title, phone, and name fields map directly to typed Contact fields. Any People record referencing a companyId that fails resolution is held in a reconciliation queue.

1:1

Opportunities → Opportunity

Twenty Opportunities map to Dynamics 365 Opportunity.

How it maps

We map stage name values explicitly to Microsoft Dynamics 365 Sales Process stage values to avoid silent mismatches. Amount and close date transfer directly. We resolve the companyId to AccountId and personId (if populated) to ContactId before insert. Closed-Won and Closed-Lost reason fields migrate from Twenty custom fields if they exist.

1:1

Tasks → Task

Twenty Tasks map to Dynamics 365 Task.

How it maps

We preserve the record-to-task relation by resolving the target record's ID in Dynamics 365 and setting the WhatId (related to) or WhoId (related contacts) reference accordingly. Title, due date, completion status, and assignee migrate with status mapped to Dynamics 365 Task Statecode and Priority.

1:1

Notes → Annotation

Twenty Notes map to Dynamics 365 Annotation (the Dataverse entity backing the Notes wall on Account, Contact, and Opportunity forms).

How it maps

We map the relational target to the corresponding record ID in Dynamics 365 and migrate note body content as the Annotation's notetext field. Note attachments migrate as Dynamics 365's documentattachment entity linked to the Annotation.

1:1

Custom Objects → Custom Entity (Dataverse)

Twenty Custom Objects migrate to Dataverse custom entities.

How it maps

We pre-create the destination schema including all custom fields, lookup relationships to standard entities (Account, Contact, Opportunity), and picklist option sets before any data import. Customer must hold a Dynamics 365 Enterprise license or a Dataverse database license to host custom entities. Self-hosted Twenty deployments may have Custom Objects that have no direct Dynamics 365 equivalent; we document these as custom entity requirements during scoping.

What moves8 objects
Twenty CRMDynamics 365
  • CompaniesAccount1:1
  • PeopleContact1:1
  • OpportunitiesOpportunity1:1
  • TasksTask1:1
  • NotesAnnotation1:1
  • Custom ObjectsCustom Entity1:1

+ 2 more in the mapping below

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

DimensionTwenty CRMDynamics 365
Contact modelSingle People object with companyId relationSeparate Account (company) and Contact (person) objects with explicit relationship via AccountId on Contact
Custom objectsUnlimited custom objects on Organization cloud tierAvailable on Enterprise tier or via Dataverse; Professional requires full Dataverse licensing
Export cap20,000 records per export operation, visible columns onlyNo equivalent native export limit; API and Data Export Service govern volume
Pricing modelFree self-hosted under AGPL-3.0; cloud at $9-$19/user/monthSales Professional $65/user/month; Sales Enterprise $105/user/month; per-seat not per-record
Email sequencingNo native sequencing or cadence toolsNo native sales engagement cadence; requires Microsoft Dynamics 365 Sales Insight or a third-party outreach platform
API structureREST and GraphQL APIs on paid cloud tiers with 100-200 req/min limitsDataverse Web API (OData 4.0) with per-user throttling; Bulk API available for high-volume loads
Workflow automationFunctional but limited multi-step workflow builderPower Automate and Dynamics 365 workflow engine require separate configuration post-migration

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

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

high

Twenty export caps at 20,000 records and visible columns only

The Twenty built-in export function limits output to 20,000 records per operation and includes only columns visible in the active view.

How we handle it

We pre-configure the export view to expose all fields before extracting, and chunk migrations exceeding 20K records into multiple exports partitioned by date range or record ID window. Skipping this pre-configuration step results in silent column truncation and missing fields in Dynamics 365.

high

Import order is enforced and critical

Twenty requires CSV imports in a specific sequence: Companies first, People second with companyId references, Opportunities third, and Custom Objects last.

How we handle it

Dynamics 365 similarly requires Account to exist before Contact insert because of the AccountId lookup. We enforce this ordering rigorously because foreign key constraints block import of any record referencing a parent that does not yet exist.

medium

Soft-deleted records trigger uniqueness conflicts

Twenty's uniqueness check runs against all records including soft-deleted ones.

How we handle it

Importing a record with the same email as a soft-deleted Twenty Person may restore the deleted record in Twenty rather than creating a new one, creating a mismatch with what was intended for migration. We detect this condition during scoping and coordinate with the customer on whether to purge deleted records or map to existing records before migration.

medium

API rate limits cap at 200 req/min on Organization tier

Twenty's paid cloud tiers enforce per-minute API quotas — 100 req/min on Pro, 200 req/min on Organization.

How we handle it

For migrations above 10,000 records, we distribute writes across throttled request batches with exponential backoff to respect limits without triggering 429 responses. Self-hosted Twenty deployments do not enforce these quotas, but cloud-tier migrations require careful pacing.

medium

Workflows and sequences do not migrate between platforms

Twenty's workflow automation rules and any email cadence or sequence configuration have no structural equivalent in Microsoft Dynamics 365 Sales .

How we handle it

We do not migrate them as code. We deliver a written inventory of every active Twenty workflow and sequence with its trigger, conditions, actions, and a recommended Dynamics 365 Power Automate or Sales Insight equivalent. The customer's admin rebuilds them post-migration. This is a manual step that requires business-user validation.

How the migration runs

  1. Discovery and scoping

    We audit the source Twenty deployment across plan tier (self-hosted, Pro cloud, or Organization cloud), total record counts per object, custom object definitions and their field schemas, active workflow rules, email sequences, and export volume estimates.

    What this step covers

    We assess the Dynamics 365 destination tenant for existing data, Dataverse capacity, and license tier (Sales Professional or Enterprise). The discovery output is a written migration scope, a record-count estimate, and a Dynamics 365 edition recommendation.

  2. Pre-configuration and export preparation

    We configure the Twenty export view to expose all fields before extraction.

    What this step covers

    For migrations exceeding 20,000 records, we partition the export by date range or record ID window to avoid the 20K cap. We extract Companies first (with all fields), then People, then Opportunities, then Tasks, then Notes, then Custom Objects. Each export is validated for column completeness before leaving Twenty.

  3. Destination schema design and sandbox migration

    We design the Dynamics 365 destination schema: Account, Contact, and Opportunity fields typed and mapped to Twenty equivalents; custom entities in Dataverse pre-created for any Custom Objects; Sales Process stages configured to match Twenty pipeline stages; and picklist option sets aligned.

    What this step covers

    Schema is deployed to a Dynamics 365 Sandbox environment first for validation. The customer reconciles record counts and spot-checks 25-50 records against the source before production migration begins.

  4. Owner reconciliation and user provisioning

    We extract every distinct Owner referenced in the Twenty export and match by email against the Dynamics 365 destination org's User table.

    What this step covers

    Owners without a matching User go to a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users. Migration cannot proceed past this step because OwnerId references are required on most standard objects in Dynamics 365.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Twenty Companies), Contacts (with AccountId resolved from companyId), Opportunities (with AccountId, ContactId, and OwnerId resolved), Tasks, Annotations, Custom Objects, and Activity history (calls, emails, meetings via Dataverse Web API).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We use Dataverse Bulk API for large batches and exponential backoff for rate-limit responses.

  6. Cutover, validation, and workflow handoff

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

    What this step covers

    We deliver the Workflow and Sequence inventory document to the customer's admin team for rebuild in Power Automate. We support a one-week post-cutover window where we resolve reconciliation issues. We do not rebuild Twenty Workflows as Power Automate flows inside the migration scope; that is a separate engagement.

Twenty CRM Dynamics 365
  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 · Dynamics 365Rollback 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

3-5 weeksTypical, smaller accounts
6-10 weeksLarge or heavily customised accounts

A quote scales with record volume, custom object complexity, and engagement history size. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Twenty CRM to Dynamics 365 →

Why teams move from Twenty CRM to Dynamics 365

  • Teams hit Twenty's operational maturity ceiling at v1.0. Reviewers on Reddit and community threads note that Twenty's recent release status means limited production hardening compared to established CRMs with multi-year operational track records. Enterprises requiring SOC 2 Type II, enterprise SLA coverage, and vendor support contracts with escalation paths find Microsoft Dynamics 365's mature certification and Premier Support infrastructure more aligned with their risk posture.
  • No native email sequencing or cadence tools forces teams to layer a separate outreach platform on top of Twenty. Microsoft Dynamics 365 Sales pairs with Sales Insight and Microsoft Copilot for sales engagement features, and integrates directly with Microsoft 365 Outlook and Teams for native activity logging. Teams migrating from Twenty to Dynamics 365 gain inbox-level email tracking, meeting scheduling, and cadence management within a single licensed ecosystem.
  • Self-hosting free tier understates real total cost. Reviewers consistently note that Twenty's $0 software label ignores infrastructure spend ($20-$100/month for cloud hosting), DevOps hours for updates and backups, and the opportunity cost of engineering time maintaining a self-hosted CRM. Dynamics 365's per-seat SaaS model ($65-$105/user/month) bundles support, uptime guarantees, and automatic updates, which procurement and finance teams find more predictable for budgeting purposes.
  • Limited native integrations on Twenty push teams toward custom API work or Zapier/Make connectors for essential tooling. Microsoft Dynamics 365 Sales benefits from deep Microsoft 365 ecosystem integration (Outlook, Teams, SharePoint, Power Platform) and a mature AppSource marketplace with pre-built connectors for ERP, CPQ, and revenue intelligence tools. Microsoft-centric organizations already running Microsoft 365, Azure AD, and Power BI find Dynamics 365's native interoperability reduces integration overhead significantly.
  • Workflow automation depth in Twenty is functional but constrained for complex multi-step sales motions, according to early adopters. Dynamics 365 offers Power Automate for complex process automation, Power Apps for custom forms and apps, and built-in business process flows for guided selling motions. Teams with sophisticated lead scoring, territory routing, or multi-stage approval workflows find Dynamics 365's automation stack better suited to enterprise sales operations.

Questions, answered

Twenty CRM to Dynamics 365 migration questions

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

Most migrations land between three and five weeks for accounts under 15,000 records with no custom objects. Migrations with custom objects, large engagement histories (over 200,000 activity records), or multiple integration dependencies move to six to ten weeks because of chunked export handling, parent-record resolution across the Account-Contact-Opportunity chain, and sandbox validation cycles.

Do Twenty's workflows, email sequences, and automations migrate to Dynamics 365?

No. Twenty's workflow automation rules and email cadence or sequence configurations have no direct equivalent in Microsoft Dynamics 365 Sales . We do not migrate them as code. We deliver a written inventory of every active Twenty workflow and sequence with its trigger, conditions, actions, and a recommended Dynamics 365 Power Automate or Sales Insight equivalent. The customer's admin rebuilds them post-migration.

Can we migrate all 20,000+ records if Twenty's export cap applies?

Yes. We pre-configure the Twenty export view to expose all fields before extraction, then partition large migrations into multiple exports by date range or record ID window. The partition strategy is agreed upon during scoping. We validate that the combined export set covers the full record set before beginning destination writes. This approach adds one to two days to the scoping phase but prevents silent truncation.

How do we handle Twenty's soft-deleted records during migration?

We detect soft-deleted records (records in Twenty's 'See deleted records' view) during scoping. Because Twenty's uniqueness check runs against all records including soft-deleted ones, importing a record with the same email as a soft-deleted Person may restore the deleted record rather than creating a new one. We coordinate with the customer on whether to purge soft-deleted records from Twenty before migration or to map the migration to the existing restored record and update its fields.

Do we lose historical activity data (calls, emails, meetings) when migrating to Dynamics 365?

We migrate the full engagement history by mapping Twenty's call, email, and meeting engagements to Dynamics 365 Task (TaskSubtype=Call), EmailMessage, and Event records respectively. Activity timestamps are preserved. The parent-record resolution step (matching Twenty's companyId and personId to Dynamics 365 AccountId and ContactId) must complete before engagement records insert, because Dynamics 365 requires valid WhatId and WhoId references on activity records.

What happens to Twenty's custom objects in Dynamics 365?

Twenty Custom Objects migrate to Dataverse custom entities. The customer must hold a Dynamics 365 Enterprise license or a standalone Dataverse database license to host custom entities. We pre-create the destination schema including all custom fields, lookup relationships, and option sets before any data import. If a Twenty custom object has lookup relationships to standard objects (Companies, People, Opportunities), we resolve those references during migration to maintain relational integrity in Dynamics 365.

Can FlitStack AI migrate data from a self-hosted Twenty deployment as well as a cloud-hosted one?

Yes. We support both deployment models. For self-hosted Twenty (running on the customer's PostgreSQL infrastructure), we connect directly to the PostgreSQL database to extract records, which bypasses the 20,000-record export cap and API rate limits entirely. For cloud-hosted Twenty, we work with the REST and GraphQL APIs under the applicable rate-limit tiers. We confirm the deployment model during discovery and adjust extraction strategy accordingly.

Get a quote

Moving from Twenty CRM to Dynamics 365?

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

Get a quote