---
title: "monday CRM to Dynamics 365 Migration | FlitStack AI"
description: "Migrate monday CRM to Dynamics 365 with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/monday-crm/to/dynamics-365-sales"
---

# monday CRM to Dynamics 365 migration

We migrate People contacts, Deals, and pipeline data from monday CRM into Microsoft Microsoft Dynamics 365 Sales with the flat board-and-item model resolved into Accounts, Contacts, and Opportunities, monday's stage values mapped to typed Sales Processes, and every subitem enumerated individually because the bulk export excludes them by default.

Short answer

FlitStack AI migrates contact or leads, opportunities, sales process + record types, account or custom entities, task, note and or custom entity records from monday 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/monday-crm/to/dynamics-365-sales#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source monday CRM ![](https://flitstack.ai/platforms-trim/monday-crm.webp)

Destination Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Contact or Lead Opportunity Sales Process + Record Type Account or custom entity Task, Note, or custom entity record

Mapped field by field · sample run · one-click rollback

## What moves from monday CRM to Dynamics 365?

Moving from monday CRM to Microsoft Microsoft Dynamics 365 Sales is a structural migration that reshapes a flat, board-centric data model into a relational object hierarchy. monday CRM has no native Account object separate from Items; contacts live in the People feature and deals are Items attached to a Pipeline.

Read the full summary

Microsoft Microsoft Dynamics 365 Sales uses Accounts to represent organizations, Contacts to represent people, and Opportunities to represent deals with explicit Account and Contact lookups. We resolve the monday-to-Dynamics schema gap during scoping, extract People records and map them to Contacts (or Leads for unqualified prospects), and map Pipeline stage values to Opportunity stages configured in the destination before any data moves. Subitems require individual API enumeration per parent Item, which multiplies API call volume beyond what the bulk export suggests. We do not migrate monday automations or board views; we deliver a written inventory of automation rules and view configurations for the customer's admin to rebuild in Dynamics or Power Automate.

1:N split

### People (Contacts) → Contact or Lead (split required)

monday CRM People records store name, email, phone, and CRM-specific properties as a distinct entity.

How it maps

We map each Person to a Dynamics 365 Contact by email match. If the monday Person has no associated Deal Item or is marked as a prospect without a named organization, we create a Lead record instead and flag it for sales qualification. The original monday Person ID is preserved in a custom field monday\_person\_id\_\_c on Contact for audit. No monday board Item is created as a side effect of this mapping; we treat People as the authoritative contact source.

1:1

### Deal (CRM Item) → Opportunity

Deals in monday CRM are CRM-typed Items attached to a Pipeline.

How it maps

Each Deal has standard columns (deal value, close date, stage) plus optional custom columns. We map each Deal to a Dynamics 365 Opportunity with StageName set from the Pipeline stage column, EstimatedValue from the deal value column, and CloseDate from the close date column. If the Deal references a monday Person, we resolve the ContactId by email match before inserting the Opportunity. Closed-Lost and Closed-Won status map to Dynamics 365 stage names that the customer's admin configures as part of the Sales Process design.

configuration

### Pipeline → Sales Process + Record Type

Each monday CRM Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the stage names.

How it maps

Stage order and probability percentages from monday map to StageProbability values on each stage in Dynamics. If monday has multiple Pipelines (e.g., one per business line), we create one Record Type per Pipeline and assign it to the appropriate Page Layouts during schema design.

lookup

### Board (CRM Board) → Account or custom entity

monday CRM Boards are containers that expose CRM column types.

How it maps

Non-CRM boards used for pre-sale tracking or project-level data that maps to Account-level metadata (industry, size, territory) become custom fields on the Account object in Dynamics 365. CRM-specific boards that manage deal activity (call logs, proposal status) are preserved as Notes and Tasks attached to the Opportunity rather than as standalone objects, because Dynamics 365 has no direct board equivalent.

configuration

### Item (standard board row) → Task, Note, or custom entity record

Non-CRM monday board Items that represent activities (meeting notes, task lists, discussion threads) migrate as Task or Note records attached to the parent Opportunity or Contact.

How it maps

Items with custom column structures that do not map cleanly to standard Dynamics 365 fields become records in a custom entity with custom fields, deployed via the Dataverse API before migration. We flag any Item type that has no clear Dynamics 365 equivalent during scoping so the customer can decide whether to create a custom entity or collapse the data into Notes.

configuration

### Subitem → Task, Note, or custom entity record

Subitems are nested rows inside a monday Item.

How it maps

They do not appear in the bulk account export or standard Excel export; we enumerate them individually via the monday API using each parent Item ID. This multiplies API call volume significantly and is the primary reason monday migrations with heavy subitem usage require extended timeline estimates. We resolve the parent Item's migrated Opportunity or Contact ID and attach the subitem as a Task or Note. Subitems with structured column data (numbers, dates, people) map to custom Task fields.

******What moves 10 objects

monday CRM Dynamics 365

- People Contact or Lead split
- Deal Opportunity 1:1
- Pipeline Sales Process transformed
- Board Account or custom entity transformed
- Item Task, Note, or custom entity record transformed
- Subitem Task, Note, or custom entity record transformed

\+ 4 more in the mapping below

## How monday 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.

| Dimension               | monday CRM                                                                      | Dynamics 365                                                                                    |
| ----------------------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Object model            | Flat board-and-item model; no native Account; People as separate entity         | Relational: Account (organization), Contact (person), Opportunity (deal) with explicit lookups  |
| Pipeline representation | Pipeline object with ordered Stages; Deals are Items in a Pipeline              | Opportunity with StageName; Sales Processes and Record Types scope stages per business line     |
| Contact ownership       | People feature stores contacts separately from board Items                      | Contacts linked to Accounts via AccountId lookup; Leads separate for unqualified prospects      |
| Custom fields           | Custom columns on Items; \~20 column types including formula and dependency     | Custom fields on any standard or custom entity; formula fields available at all paid tiers      |
| API call limits         | 1,000/day on Basic/Standard; 10,000/day on Pro; 25,000/day on Enterprise (soft) | 60,000 API calls per minute per app across Dataverse; bulk operations preferred for large loads |
| Automation model        | No-code Recipe builder (deprecated) or new monday workflows; plan-gated actions | Power Automate (cloud flows) or Dynamics workflows; available from Professional tier            |
| Reporting               | Chart views, formulas, and dashboards are Pro and Enterprise gated              | Native reporting from Professional; Power BI integration at all tiers                           |

## What to watch for in a monday 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

### Subitems are excluded from monday bulk exports

The monday.com account data export and standard Excel export do not include Subitems — they only export the parent Item rows.

How we handle it

Subitems must be enumerated individually via the monday API using each parent Item's ID, which multiplies API call volume significantly. For accounts with thousands of Items each containing multiple Subitems, this can exhaust the daily API limit on Basic and Standard plans (1,000 calls/day) and extend the migration timeline to multiple days. We include a subitem enumeration step in every monday CRM migration plan and flag the total subitem count during scoping so the customer understands the additional API load and timeline impact before migration begins.

high

### monday has no native Account object

monday CRM's flat item model does not enforce an Account-to-Contact relationship.

How we handle it

Organizations, companies, or organizations referenced in Deals are often stored as text in a Name column or as a separate People record without a link to the Deal Item. We must disambiguate these during migration: text-based organization names become new Account records created on the fly, and People records without an associated organization create orphaned Contacts. We flag these disambiguation decisions during scoping and provide a reconciliation sheet for the customer's admin to validate before production migration.

medium

### Dynamic mapping fields in monday apps are deprecated

monday's Dynamic Mapping fields feature, used by custom apps to map Item data to external platforms, is being deprecated in favour of the new monday workflows infrastructure.

How we handle it

Teams using monday integrations built on the dynamic mapping API will find those integrations non-functional post-migration if they attempt a live sync during cutover. We capture the dynamic mapping configuration during pre-migration review and document it as part of the integration inventory, flagging which monday apps need rebuilding as Power Automate flows or Dynamics 365 native integrations.

medium

### Legacy Sentence Builder automations are not portable

monday.com is deprecating the Sentence Builder automation infrastructure in favour of the new monday workflows system.

How we handle it

Customers migrating out of monday with automations built on the old system find those automation definitions are not exportable. We capture automation rule definitions during pre-migration review (trigger, conditions, actions) and deliver a written inventory sorted by board so the customer's admin has a complete map of every automation requiring rebuild. We do not migrate automations as code because they are workflow logic, not data, and the underlying trigger models are incompatible.

medium

### Data quality gaps from monday's flexible schema compound in Dynamics 365

monday's flexible column system lets teams create custom fields without schema governance, which means phone numbers may be stored in text columns, dates in free-form text, and organization names duplicated across both People and Item name fields.

How we handle it

Dynamics 365 enforces typed fields and required lookups that monday does not. We profile the monday data before migration, flag records with missing required fields (email, phone format, date format), and apply cleansing transforms during the migration pipeline. Records that fail validation after cleansing are held in an exception queue for the customer to resolve.

## How the migration runs

1. ### Discovery and API scoping

   We audit the source monday CRM account across plan tier, People count, CRM board count, pipeline count, Deal volume, subitem volume per board, custom column definitions, active automations, and API call history.

   What this step covers

   This determines whether the migration can complete within the daily API limit on the current plan tier or whether a temporary plan upgrade is required. We also extract the monday User list and match by email against the target Dynamics 365 tenant to identify any users requiring provisioning before migration begins.

2. ### Schema design and pipeline mapping

   We design the Dynamics 365 destination schema: create Account records or record types for monday organization data, configure Sales Processes and Record Types for each monday Pipeline, define custom fields on Opportunity to receive monday custom column data, and create any custom entities required for monday board Items that do not map to standard Dynamics 365 objects.

   What this step covers

   The Lead-versus-Contact decision is made here based on whether the monday Person has a closed-won Deal or is attached to a named organization. Schema is deployed to a Dynamics 365 Sandbox via the Dataverse API before any data moves.

3. ### Sandbox migration and reconciliation

   We run a full migration into the Dynamics 365 Sandbox using production-equivalent data volume.

   What this step covers

   The customer's sales ops lead reconciles record counts (People in vs Contacts in, Deals in vs Opportunities in), spot-checks 25-50 records against the monday source, and validates that pipeline stage values appear correctly in Dynamics 365. Any mapping corrections and data quality transforms are applied here before the production migration plan is finalized.

4. ### Subitem enumeration and data cleansing

   We enumerate Subitems individually via the monday API using each parent Item ID, apply data quality transforms (phone number formatting, date parsing, organization name deduplication), and load into a staging table.

   What this step covers

   Records with missing required fields are flagged in an exception report with the original monday field value so the customer can supply the correct data before production migration.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Accounts (from monday organization data), Contacts (from monday People with AccountId resolved), Leads (from monday People without organization), Opportunities (with AccountId, ContactId, OwnerId, and RecordTypeId resolved), custom entity records, Activity history (Tasks, Notes, EmailMessages via Dataverse API), and Subitems (last, attached to their parent Opportunity or Contact).

   What this step covers

   Each phase emits a row-count reconciliation report. We throttle jobs to stay within monday's daily API limit, use exponential backoff on 429 responses, and schedule bulk jobs during off-peak hours on Basic and Standard plan accounts.

6. ### Cutover, validation, and automation rebuild handoff

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

   What this step covers

   We deliver the automation inventory document listing every monday automation rule with trigger, conditions, and recommended Power Automate equivalent, and the board-view documentation for the customer's admin to rebuild as Dynamics 365 views or Power BI dashboards. We support a one-week hypercare window for reconciliation issues and do not rebuild monday automations as Power Automate flows inside the migration scope; that is a separate engagement.

![](https://flitstack.ai/platforms/monday-crm.svg) monday CRM ![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Dynamics 365 Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**7-12 weeks** Large or heavily customised accounts

A quote scales with record count, subitem volume, and pipeline complexity. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for monday CRM to Dynamics 365 →](https://flitstack.ai/contact)

## Why teams move from monday CRM to Dynamics 365

- monday CRM's flat board-and-item model creates structural friction as sales teams scale. With no native Account object, contacts and organizations are not explicitly linked, leading to duplicate entries and ambiguous deal ownership. Microsoft Microsoft Dynamics 365 Sales enforces the Account-Contact-Opportunity hierarchy, which provides referential integrity and enables territory-based reporting that monday's pipeline view cannot support without exporting to a BI tool.
- Pro and Enterprise features required for forecasting, AI insights, chart views, and advanced automation create a pricing cliff as teams grow. Microsoft Dynamics 365 Sales Professional at $65/user/month includes pipeline management, forecasting, and Power BI integration without the feature-gating that forces monday teams to the highest tier. Reviewers on Capterra and G2 cite the Pro-only automation limit of 25,000 actions as a pain point for teams with high-volume sales processes.
- Microsoft ecosystem integration drives the switch for organizations already running M365, Teams, Azure AD, and SharePoint. Microsoft Dynamics 365 Sales provides native Outlook and Teams integration, Azure AD-based SSO, SharePoint document management, and LinkedIn Sales Navigator connectivity that monday CRM cannot match without third-party middleware. Power BI dashboards connect to live CRM data without an additional export step.
- monday's legacy Sentence Builder automations are being deprecated in favour of monday workflows, which creates a migration window risk. Teams with business-critical automations built on the old system face forced rebuilds if they do not migrate out before the deprecation deadline. Migrating to Microsoft Dynamics 365 Sales with Power Automate provides a structured replacement for automation logic without waiting for monday's new workflow infrastructure to stabilize.
- Per-seat pricing on monday CRM scales linearly and annual billing is non-refundable, creating cost lock-in for teams that overbought. Microsoft Dynamics 365 Sales Enterprise at $105/user/month offers unlimited pipelines, custom objects, and record types versus monday's tiered feature gates, making the per-seat cost more predictable for mid-market teams with complex data models.

Questions, answered

## monday CRM to Dynamics 365 migration questions

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

Most migrations land between three and five weeks for accounts under 10,000 People, 3,000 Deals, and manageable subitem counts. Migrations with high subitem volumes (requiring individual API enumeration per parent Item), multiple monday Pipelines mapping to multiple Dynamics 365 Record Types, or large activity histories move to seven to twelve weeks because of API throttling and the disambiguation work required to resolve monday's flat organization data into the Account-Contact-Opportunity hierarchy.

Do monday automations, board views, and dashboards migrate to Microsoft Dynamics 365 Sales ?

No. monday automations (Sentence Builder and monday workflows) are workflow logic, not data, and the underlying trigger models are incompatible with Dynamics 365 Power Automate flows. We do not migrate them as code. We deliver a written inventory of every active monday automation with its trigger, conditions, and actions, plus a recommended Power Automate equivalent. Board views (Kanban, Calendar, Chart), saved filters, and dashboard widgets do not export via the standard API endpoint; we recommend documenting these configurations before migration and rebuilding them as Dynamics 365 views or Power BI paginated reports.

How do we handle monday's flat object model when Dynamics 365 requires Accounts and Contacts?

The monday CRM data model has no native Account object, so organizations referenced in Deals are stored as text, as People records, or not at all. During scoping, we disambiguate: text-based organization names in Deal Items create new Account records, People records with a named organization link to an existing Account, and People records without an organization become Leads for sales qualification. We provide a reconciliation sheet for the customer to validate the disambiguation decisions before production migration so that no organization data is incorrectly assigned.

Can we migrate historical activity data (updates, notes, attachments) from monday?

Yes. monday Updates migrate as Note records attached to the parent Opportunity or Contact, preserving text content and timestamps. File attachments migrate as Notes with a file annotation pointing to the monday-hosted URL. Subitems used to track activity (call logs, meeting notes, line items) migrate as Task records attached to the parent. We do not re-upload files to Dynamics 365 SharePoint as standard scope; file migration to SharePoint is a separate deliverable. Activity timeline ordering is preserved by setting the ActivityDate to the original monday timestamp.

How do monday's API rate limits affect the migration timeline?

Basic and Standard plans are capped at 1,000 API calls per day, which means a migration with 5,000 Deals plus subitem enumeration can require multiple days to complete even with throttling. We throttle migration jobs to stay within the daily limit, use exponential backoff on 429 responses, and schedule bulk jobs during overnight windows to maximise the available daily call budget. If the subitem count is high, we recommend a temporary upgrade to Pro (10,000 calls/day) for the migration window to reduce total elapsed time.

What happens to monday CRM integrations after migration?

Any monday integrations built on the dynamic mapping API or Recipe infrastructure will not function after migration because they rely on monday-specific data structures. We document each integration during pre-migration discovery and recommend replacing them with Dynamics 365 native integrations or Power Automate flows. The Microsoft ecosystem integrations (Outlook, Teams, SharePoint, LinkedIn Sales Navigator) are available natively in Dynamics 365 without additional middleware.

Do we need a Microsoft partner or Dynamics 365 consultant to complete the migration?

The data migration itself is handled by FlitStack AI. However, Dynamics 365 configuration work (Sales Process design, Record Type setup, security roles, Power BI report building) typically requires a Dynamics 365 admin or Microsoft partner. We provide the schema design document and field mapping specification as part of the migration deliverable, which gives the customer's admin or partner a clear blueprint for the Dynamics 365 configuration without requiring them to reverse-engineer the source data structure.

## Related migrations

[![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp) Migrate to **Dynamics 365** Every source we move into Dynamics 365, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/dynamics-365-sales)

### [Dynamics 365 implementation](https://flitstack.ai/services/dynamics-365-implementation)

[Set up Dynamics 365 and migrate into it as one engagement.](https://flitstack.ai/services/dynamics-365-implementation)

[See the service →](https://flitstack.ai/services/dynamics-365-implementation) [**Dynamics 365 to monday CRM** The same pair in reverse](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/monday-crm) [**Convertkit to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/convertkit/to/dynamics-365-sales) [**Copper to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/copper/to/dynamics-365-sales) [**Salesforce to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/salesforce-sales-cloud/to/dynamics-365-sales) [**Sugarcrm to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sugarcrm/to/dynamics-365-sales) [**Bella FSM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bella-fsm/to/dynamics-365-sales) [**Jonas Enterprise Service & Construction Software to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jonas-enterprise-service-construction-software/to/dynamics-365-sales) [**monday CRM to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monday-crm/to/zoho-crm) [**monday CRM to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monday-crm/to/salesforce-sales-cloud) [**monday CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monday-crm/to/hubspot)

## Sources: official documentation

1. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
2. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
3. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)
4. [Execute Batch Operations on Dataverse — Microsoft Learn](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/execute-batch-operations-using-web-api)
5. [Migrate your data from Work Management to CRM — monday Support](https://support.monday.com/hc/en-us/articles/19933608666514-Migrate-your-data-from-Work-Management-to-CRM)
6. [Import from Excel to monday CRM — monday Support](https://support.monday.com/hc/en-us/articles/14244473062290-Import-from-Excel-to-monday-CRM)
7. [Importing items in bulk — monday Developers](https://monday.com/developers/)

Get a quote

## Moving from monday 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](https://flitstack.ai/contact)
