Skip to content
Get a quote

Dynamics 365 to monday CRM migration

We migrate Accounts, Contacts, Leads, Opportunities, and activity history from Microsoft Dynamics 365 Sales into Monday.com CRM, converting the relational Dataverse entity model into Monday's board-item architecture and resolving owner lookups, pipeline stage mapping, and custom field type incompatibilities before the first record lands in production.

Short answer

FlitStack AI migrates company boards, people board items, deals board items, products boards and update log or sub-item on parent boards from Dynamics 365 to monday 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: 4-6 weeks.

By

Source Dynamics 365
Destinationmonday CRM
Company boardPeople board itemDeals board itemProducts boardUpdate log or sub-item on parent board
Mapped field by field · sample run · one-click rollback

What moves from Dynamics 365 to monday CRM?

Moving from Microsoft Dynamics 365 Sales to Monday.com CRM is an architectural migration, not a table-to-table copy.

Read the full summary

Dynamics 365 structures data in normalized Dataverse entities with typed fields, option sets, lookups, and owner assignments; Monday.com CRM uses boards, groups, and items with a flexible column model. We bridge that structural gap by mapping Accounts to People and Company boards, Contacts to item records, and Opportunities to Deals items with pipeline columns. The Dataverse Web API handles extraction with batched reads and owner-lookup resolution, and we use Monday.com's REST API with item creation and column-value updates for import. Dynamics Power Automate workflows, Dataverse business rules, and Dynamics reports do not migrate; we deliver a written automation inventory and report list for the customer's admin to rebuild in Monday.com Automations and dashboard widgets.

1:1

Account → Company board (People or Company board)

Dynamics Account records map to item records on a Monday.com Company board.

How it maps

Primary fields mapped include Account Name (item name), Website, Industry, Address fields, Phone, and Annual Revenue. OwnerId from Dynamics maps to a Person column in Monday.com, resolved by email lookup against Monday.com workspace members. We pre-create the Company board and all target columns in Monday.com before migration begins because Monday.com requires column definitions before item creation API calls can populate column values.

1:1

Contact → People board item or linked record

Dynamics Contact records map to item records on a Monday.com People board, with the Contact Name as the item name and standard fields (Email, Phone, Job Title, Department) mapped to text or dropdown columns.

How it maps

The parent Account lookup resolves to a Link column or a lookup integration pointing to the Company board item. Lifecycle Stage from Dynamics maps to a Status or dropdown column. If the destination uses a single unified board rather than separate People and Company boards, Contacts appear as items with a Contact Type column set to 'Contact' to distinguish from Account items.

1:1

Lead → People board item (Lead status)

Dynamics Lead records do not have a direct Monday.com CRM equivalent; Monday.com has no separate Lead entity.

How it maps

We map Leads to item records on the People board with a Contact Type column value of 'Lead' and a Lead Status dropdown column carrying the Dynamics leadscore, status, and source attribution. Original Lead score and source fields migrate to custom number and text columns. Leads that have been qualified into an Opportunity at the source carry a reference that we document for manual linking in Monday.com after migration.

1:1

Opportunity → Deals board item

Dynamics Opportunity records map to item records on a Monday.com Deals board.

How it maps

Opportunity Name becomes the item name; Estimated Value maps to a Number column; Close Date maps to a Date column; Pipeline Stage maps to a Status column with group-level stage values matching the Dynamics stage names. Probability migrates as a Number column or as a formula column if the customer uses Monday.com Pro or Enterprise. The parent Account and Contact links resolve to Link columns or integration lookups pointing to the corresponding Company and People board items.

1:N split

Quote / Order / Invoice → Deals board sub-items or linked records

Dynamics Quotes, Orders, and Invoices form a commercial document chain with line items and product references.

How it maps

Monday.com CRM has no native quoting or order management. We map the Quote as a sub-item on the Deals board item with Quote Number, Total Amount, and Status columns. If the customer uses Order or Invoice records, we map them as additional sub-items or as separate items on a commercial documents board, noting that Monday.com does not have native order-to-invoice automation. Product line items from Quotes map to a text column listing product names and quantities, or to sub-items with item name, quantity, and price columns.

1:1

Product and Price List → Products board

Dynamics Products and Price Lists map to a Products board in Monday.com.

How it maps

Product Name is the item name; Product Code maps to a Text column; Standard List Price maps to a Number column. Price list assignments on Opportunities are documented as a text or dropdown column on the Deals item rather than as a formal lookup relationship, since Monday.com does not enforce referential integrity between boards in the same way Dataverse does.

What moves10 objects
Dynamics 365monday CRM
  • AccountCompany board1:1
  • ContactPeople board item or linked record1:1
  • LeadPeople board item1:1
  • OpportunityDeals board item1:1
  • QuoteDeals board sub-items or linked recordssplit
  • Product and Price ListProducts board1:1

+ 4 more in the mapping below

How Dynamics 365 and monday 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 365monday CRM
Entity modelNormalized Dataverse entities with typed fields, option sets, and lookupsBoard-item structure with flexible column types (text, number, date, person, dropdown)
Lead handlingDedicated Lead entity with qualification status and source attributionLeads tracked as item records on a People board with lifecycle status as a dropdown column
Opportunity pipelineOpportunity entity with stage field, probability, and estimated close dateDeals items organized by Status group columns or dedicated pipeline view
Custom objectsCustom tables available (15-table limit on Professional, unlimited on Enterprise)Custom columns on boards; no standalone custom object concept
Custom field typesOption sets, two-option booleans, customer lookups, multi-select option setsText, number, date, person, dropdown, link, file; limited typed-field parity
Activity timelineActivities stored as separate entity records with type, date, owner, and bodyActivity history logged as updates or sub-items on the parent record board
Pricing modelPer-user named tiers: Professional $65, Enterprise $105 (October 2024 increase of $15 applied)Per-seat tiers: Standard $12, Pro $16, Enterprise (custom quote)
Automation enginePower Automate cloud flows with hundreds of connectors and triggersMonday.com Automations with board-specific triggers and limited connector set

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

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

high

Monday.com has no separate Lead entity or qualification workflow

Dynamics 365 uses a dedicated Lead entity with qualification stages, lead scoring, and a Convert-to-Opportunity action.

How we handle it

Monday.com CRM has no equivalent. Leads must be modeled as item records on the People board with a Contact Type column. The qualification workflow (Lead-to-Opportunity conversion, disqualified reason, account creation on convert) has no Monday.com equivalent and must be rebuilt as automations or manual processes. We document the existing Lead lifecycle stages and map them to Monday.com status dropdowns, but the convert action itself does not exist in Monday.com and the customer's admin must define the replacement process during the staging window.

high

Dynamics Power Automate workflows and business rules do not migrate

Dynamics 365 workflows built in Power Automate or the legacy workflow designer, and Dataverse business rules (field-level validation and visibility), are platform-specific configurations that have no portable representation.

How we handle it

Monday.com Automations use a different trigger-action model with different connector support. We do not migrate them as code. We deliver a written inventory of every active Dynamics workflow and business rule with its trigger, conditions, and actions, plus a recommendation for the equivalent Monday.com Automation. The customer's admin rebuilds them post-migration. This is the most common source of post-migration process gaps if not planned for during scoping.

medium

Dynamics custom field types lack direct Monday.com equivalents

Dynamics 365 option-set fields (picklists with integer values), two-option booleans, customer lookups (reference to Contact or Account), and multi-select option sets do not map 1:1 to Monday.com column types.

How we handle it

Monday.com dropdowns store text values, not integer IDs, so option-set label-to-value conversion must be handled explicitly in the migration transform. Customer lookups (which point to a specific Contact or Account record) can only map as a text reference or as a Monday.com integration link, not as a native relational reference. We detect each field type during scoping and apply a type-specific transformation strategy before migration runs.

medium

Dynamics Dynamics reports and dashboards use FetchXML and do not migrate

Dynamics 365 reports use FetchXML queries against the Dataverse and are tied to specific entity contexts and parameter passing.

How we handle it

Monday.com does not have a report engine with equivalent FetchXML-backed querying. We export a list of all active Dynamics reports and dashboards during scoping so the customer knows what reporting is at risk. In Monday.com, charts and widgets on boards replace some reporting needs, but complex pipeline analytics that require multi-entity joins (Opportunity joined to Account and Contact, with date-range and territory filtering) cannot be replicated without a BI tool such as Power BI or a Monday.com integration to a data warehouse.

medium

Professional tier 15-custom-table ceiling forces schema simplification before migration

Microsoft Dynamics 365 Sales Professional enforces a hard cap of 15 custom tables.

How we handle it

Teams running Enterprise tier with more than 15 custom tables face a structural decision before migration: either upgrade to Enterprise for the migration (adding $40 per user per month ongoing), or simplify the schema by merging custom tables before migration begins. We detect the exact custom table count during scoping, present the list with a merge recommendation, and hold migration until schema simplification is confirmed by the customer. This gotcha is pair-specific because Monday.com has no native custom object model at all, making the ceiling less relevant post-migration but still relevant to the extraction scope.

How the migration runs

  1. Discovery and architecture planning

    We audit the Dynamics 365 environment via the Dataverse Web API and Power Platform admin center, cataloging all entities in scope (Accounts, Contacts, Leads, Opportunities, Quotes, Orders, Invoices, custom tables, products, price lists, and activities), their record counts, custom field types, owner distribution, and active Power Automate flows.

    What this step covers

    We compare this against Monday.com's board-item model to determine the target architecture: whether to use a single unified CRM board, separate People and Deals boards, or a multi-board setup with integration links. We also identify incompatible field types (option sets, customer lookups, multi-select) and present a field-level transformation strategy to the customer's admin before schema build begins.

  2. Monday.com schema build and column mapping

    We create the target boards and columns in Monday.com using the REST API, setting up the People board with Name, Email, Phone, Job Title, Company, Contact Type, and Lifecycle Stage columns; the Deals board with Name, Value, Close Date, Stage, Probability, and Owner columns; and any custom boards for commercial documents or custom objects.

    What this step covers

    We pre-create every column before item import because Monday.com does not allow inserting column values on undefined column types via API. We map Dynamics option-set integer values to Monday.com dropdown text labels during this phase so the migration script uses the correct string values rather than raw integers.

  3. Sandbox migration and reconciliation

    We run a full migration into a Monday.com test workspace using a representative sample of production data, focusing on the board structure, column type behavior, attachment upload, and activity log format.

    What this step covers

    The customer reviews the migrated records, confirms that picklist values appear correctly in dropdowns, verifies that date formats render as expected, checks that Person columns resolve to the correct workspace members, and validates that Deals pipeline ordering matches the Dynamics pipeline stage. Any mapping corrections happen in this sandbox phase before production migration begins.

  4. Data quality preparation

    We run a pre-migration data quality pass on the Dynamics source.

    What this step covers

    This includes resolving all OwnerId references against the Monday.com member list (inactive owners are mapped to a designated migration admin account), identifying and either correcting or flagging records with malformed email addresses, removing duplicate Accounts based on name and domain similarity, and handling any records locked by active Dynamics workflows that would prevent extraction. Custom table records above the 15-table Professional ceiling are documented for the customer to resolve before migration resumes.

  5. Production migration in dependency order

    We run production migration in the correct dependency sequence: Company board items first (Accounts are referenced by Contacts and Opportunities), People board items second (with Account link resolved to the Company item), Deals board items third (with Account and Contact links resolved), product records fourth, quote and order sub-items fifth, and activity history last.

    What this step covers

    Each phase produces a row-count reconciliation report comparing records extracted from Dynamics against records created in Monday.com. We use exponential backoff and batch chunking on the Monday.com API to handle rate limits on large record sets. The delta window between final Dynamics read-only freeze and Monday.com go-live is kept to a single business day to minimize data divergence.

  6. Cutover, validation, and automation handoff

    We freeze Dynamics as read-only at cutover, run a final delta migration of any records modified during the migration window, and enable Monday.com as the system of record.

    What this step covers

    We deliver the migration completion package: a record-count reconciliation report, an unmapped-fields log, a Power Automate inventory document with Monday.com Automation equivalents for each flow, and a Dynamics report inventory with recommendations for rebuilding each report as a Monday.com chart widget or Power BI dashboard. We support a one-week hypercare window for data quality issues raised by the sales team. We do not rebuild Dynamics workflows or automations as Monday.com Automations inside the migration scope; that is a separate engagement.

Dynamics 365 monday 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 · monday 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

4-6 weeksTypical, smaller accounts
10-14 weeksLarge or heavily customised accounts

A quote scales with record volume, custom table count, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Dynamics 365 to monday CRM →

Why teams move from Dynamics 365 to monday CRM

  • Microsoft Dynamics 365 Sales carries a steep learning curve that requires constant IT intervention for routine tasks. Reviewers on Reddit and G2 cite poor usability for sales reps as the primary driver for switching, describing the platform as too complex for frontline adoption without dedicated admin support. Monday.com's board-based interface reduces that friction significantly for teams that do not need the full Dataverse data model.
  • Microsoft increased Microsoft Dynamics 365 Sales pricing by $15 per user per month across all tiers starting October 1, 2024. For a 20-person sales team on Professional tier, that is an additional $3,600 per year. Monday.com Standard at $12 per user per month represents a substantial ongoing cost reduction, making the per-seat savings a recurring financial argument for switching.
  • Dynamics 365 requires certified implementation partners to properly configure the system, adding 30-50% to total project cost beyond licensing fees. Businesses cite unexpected partner costs and poor partner experiences as a pain point. Monday.com's self-service setup reduces the need for specialist involvement, lowering the total cost of ownership for smaller teams without dedicated IT staff.
  • Monday.com's flexibility as a work management platform allows sales teams to customize their CRM board structure without a developer. Dynamics 365 requires schema changes through Advanced Settings, solution publishing, and sometimes plugin registration for complex customizations. Teams that have outgrown Dynamics' configuration overhead but do not need its full enterprise feature set move to Monday.com for faster iteration on sales process design.
  • Non-Microsoft integrations in Dynamics 365 require additional configuration or third-party middleware, limiting flexibility for teams using non-Microsoft tools. Monday.com's Zapier integration and REST API provide more generic webhook and connector support for teams with heterogeneous technology stacks that do not already run the Microsoft 365 ecosystem.

Questions, answered

Dynamics 365 to monday CRM migration questions

How long does a Microsoft Dynamics 365 Sales to Monday.com CRM migration take?

Most migrations land between four and six weeks for accounts under 10,000 Contacts and 2,000 Opportunities with no Enterprise-tier custom tables. Migrations with large activity histories (over 200,000 records), multiple custom tables, or complex option-set field transformations move to ten to fourteen weeks because of schema design time, board architecture decisions, and reconciliation testing. The migration itself (data extraction, transformation, and import) runs in days; the timeline is driven by discovery, schema design, sandbox validation, and the customer's review and sign-off cycle.

Do Dynamics Power Automate workflows and business rules migrate to Monday.com Automations?

No. Power Automate flows and Dataverse business rules are platform-specific configurations with no portable representation. Monday.com Automations use a different trigger-action model with board-specific triggers (when status changes, when a date arrives, when someone is added) and a narrower set of actions. We do not migrate workflows as code. We deliver a written inventory of every active Dynamics workflow and business rule with its trigger conditions, actions, and a recommended Monday.com Automation equivalent. The customer's admin rebuilds them post-migration. This is the most common source of post-migration process gaps if not planned during scoping.

Can we keep Dynamics 365 for other teams while moving Sales to Monday.com?

Yes. A common pattern is a one-time migration of CRM objects (Accounts, Contacts, Leads, Opportunities, Activities) to Monday.com for the sales team, while Dynamics 365 continues to serve operations, finance, or service teams that rely on its deeper entity model. We scope the migration to the CRM object set only and leave the non-CRM Dynamics modules intact. Ongoing data synchronization between Dynamics and Monday.com after migration is a separate integration scope that requires a third-party sync tool such as Zapier, a Power Automate flow maintained by the customer's IT team, or a custom API integration.

Do we lose historical activity data (calls, emails, meetings, tasks) during migration?

No. We migrate the full activity history from Dynamics 365 as Updates or as items on a dedicated Activity board, depending on the approach chosen during scoping. The activity type, date, description, and owner all transfer. Email body content and call disposition notes migrate as text in the activity record. Attachment files stored in Dynamics SharePoint or Dataverse blob storage are downloaded and re-uploaded as Monday.com file attachments on the relevant item. The activity timeline ordering is preserved by setting the activity item's date column to the original Dynamics timestamp.

What happens to Dynamics 365 reports and dashboards after migration?

Dynamics 365 reports use FetchXML queries against the Dataverse and are tied to specific entity contexts, parameters, and the Dynamics reporting engine. Monday.com does not have an equivalent FetchXML-backed report engine. Reports do not migrate. We export a list of all active Dynamics reports and dashboards during scoping so the customer knows exactly what reporting is at risk. In Monday.com, chart widgets on boards cover basic pipeline visualization, but multi-entity pipeline analytics (Opportunity joined to Account and Contact with territory and date-range filtering) require rebuilding in Power BI or another BI tool. We provide a report-rebuild recommendations document as part of the migration completion package.

How do we handle Dynamics option-set fields that use integer values in Monday.com?

Dynamics option-set fields store integer values in the database (for example, a status field might store 1 for New, 2 for Qualified, 3 for Lost). Monday.com dropdown columns store text labels. During the migration transform, we resolve each integer value to its corresponding text label from the Dynamics option-set metadata, then write the text label to the Monday.com dropdown column. This ensures that dropdown values appear as readable labels in Monday.com rather than raw integers. We capture the full option-set metadata during discovery and apply it during the transform phase before any records are written to Monday.com.

What custom field types from Dynamics 365 do not have Monday.com equivalents?

Three Dynamics field types require special handling. Multi-select option sets store multiple integer values per record; Monday.com has no multi-select column type, so we either concatenate the values into a text column or split them into separate single-select columns with a note to the admin. Customer lookup fields point to a specific Contact or Account record; Monday.com can represent this as a link column (if using Monday.com integrations) or as a text reference, but there is no enforced relational integrity. Two-option boolean fields map cleanly to Monday.com's Checkbox column type. We document every field with an incompatible type during scoping and agree on a handling strategy with the customer before migration begins.

Get a quote

Moving from Dynamics 365 to monday CRM?

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

Get a quote