CRM migration
Field-level mapping, validation, and rollback between Dynamics 365 Marketing and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Dynamics 365 Marketing
Source
monday CRM
Destination
Compatibility
6 of 8
objects map 1:1 between Dynamics 365 Marketing and monday CRM.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Dynamics 365 Marketing to Monday.com CRM is a structural migration from a Dataverse-backed marketing automation platform to a board-based Work OS with a CRM layer. Dynamics 365 stores Contact records in msdyn_contact on Dataverse, separates transactional and marketing contact billing, and holds Customer Journeys, Segments, and marketing email assets in msdynmkt_-prefixed tables that have no direct Monday.com CRM equivalent. We export contacts, accounts, opportunities, and marketing list memberships from the CRM layer, map them into Monday.com CRM Items with typed Columns, and handle the lookup resolution chain (Contact requires Account to exist first, Opportunities require both) during the load sequence. Marketing-specific tables, Journey definitions, Segment criteria, and email template assets do not migrate; we deliver a written inventory of these assets with field-level detail so the customer's admin can recreate them in Monday.com or a replacement marketing tool. The per-tenant Dynamics 365 Marketing price ($1,500/month) versus Monday.com CRM per-seat pricing represents a significant cost reduction for teams leaving the Microsoft stack entirely.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Dynamics 365 Marketing object lands in monday CRM, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Dynamics 365 Marketing
Contact
monday CRM
People Item
1:1Dynamics 365 Contact records (msdyn_contact on Dataverse) map to Monday.com CRM People items. Standard fields (full name, email, phone, address) map to corresponding Monday.com CRM Column types (Text, Email, Phone, Location). The Contact-to-Account lookup requires that the target Account exists in Monday.com CRM as a Company item before the Contact insert begins, so Account migration precedes Contact migration. Custom fields on the Contact entity must be defined in Monday.com CRM as Column types before import; we work from the schema exported via the Dynamics solution file to pre-create all custom Columns. The Dynamics contactid GUID does not migrate; Monday.com CRM generates its own item IDs.
Dynamics 365 Marketing
Lead
monday CRM
People Item (Lead status column)
1:1Dynamics 365 Lead records map to Monday.com CRM People items with a custom Status column (or Label/Tag column) set to Lead to distinguish them from converted Contacts. Lead status values (New, Contacted, Qualified, Disqualified) migrate as column values. The Lead-to-Contact lifecycle that D365 handles through the Lead entity state model is represented in Monday.com CRM through the status column. Any lead score or qualification data from custom Lead fields maps to a Number or Rating Column in Monday.com CRM.
Dynamics 365 Marketing
Account
monday CRM
Company Item
1:1Dynamics 365 Account records map directly to Monday.com CRM Company items. Industry classification, address, website, and annual revenue fields map to Monday.com CRM Column types (Dropdown for Industry, Text for Website, Number for Revenue). Account hierarchies in Dynamics (parent-account relationships) cannot be represented natively in Monday.com CRM's flat Company structure; we document the hierarchy in a custom Column (Parent Company) using the Company name as a text reference, or advise the customer to flatten the hierarchy in the destination. Accounts must load before Contacts because the Contact-to-Account relationship (customerid_account) must resolve at insert time.
Dynamics 365 Marketing
Opportunity
monday CRM
Deal Item
1:1Dynamics 365 Opportunities (msdyn_opportunity on Dataverse) map to Monday.com CRM Deal items on the Deals Board. Pipeline stage maps to a Monday.com CRM Status Column (or Label Column) with stage values recreated from the source pipeline. Estimated close date, estimated revenue amount, and probability percentage map to Date, Number, and Number Columns respectively. The Opportunity-to-Contact lookup ( OpportunityCustomerIdAccount ) resolves to the Monday.com CRM People item; the Opportunity-to-Account lookup resolves to the Monday.com CRM Company item. Owner ( OwningUser ) maps to the Monday.com CRM assignee (person Column) by email match. Closed-Won and Closed-Lost reasons from custom fields become Text Columns.
Dynamics 365 Marketing
Marketing List
monday CRM
Group or Board of People Items
lossyDynamics 365 Marketing Lists store member Contact records and are associated with Campaigns. We export Marketing List membership (the list itself and the contact IDs within each list) and recreate the lists in Monday.com CRM as either Groups within the People Board or as a dedicated Board with a Group per Marketing List. The member-to-contact relationship is preserved by marking each People item with the relevant list tags or adding them to the corresponding Group. Dynamic Marketing Lists (query-based membership) cannot be replicated as-is; we document the query criteria for the customer's admin to implement as a filter in Monday.com CRM or a separate segmentation tool.
Dynamics 365 Marketing
Campaign
monday CRM
Group or Board Item
lossyDynamics 365 Campaigns and Campaign Activities store campaign metadata (name, type, budget, start/end dates, objectives). We export Campaign records and recreate them as Board Items or Groups in Monday.com CRM, mapping campaign type and budget to Status, Text, and Number Columns. Campaign Activities (the action records linked to a Campaign) are documented as task items or Grouped items within the campaign Board. Since Monday.com CRM has no native Campaign object, the campaign context is preserved through consistent Board and Group naming conventions and column values rather than a typed object.
Dynamics 365 Marketing
ActivityPointer (Tasks, Emails, Notes)
monday CRM
Item or Update on Board
1:1Dynamics 365 Activity records (Task, Email, PhoneCall, Appointment) stored in ActivityPointer and its child tables map to Monday.com CRM Items on a Work Items Board or as Updates on the parent record's Board. Email body content migrates as a Text Column or as the item's first Update. Call duration and disposition migrate as Number and Text Columns. Appointment start and end times migrate as Date Columns. The RegardingObjectId lookup (linking the activity to a Contact, Account, or Opportunity) resolves to the Monday.com CRM item by matching the Dynamics record GUID to the item name or a custom external ID column that we create during migration. Activity history ordering is preserved by the createdon timestamp.
Dynamics 365 Marketing
Annotation (Attachments)
monday CRM
File Column on Item
1:1Dynamics 365 Annotations (notes with file attachments) export individually. We preserve the objectid and objecttypecode to re-associate each attachment with its parent People, Company, or Deal item in Monday.com CRM. Files migrate as Monday.com CRM File Column attachments. Notes with text body (not file attachments) migrate as Updates on the parent item. The export pass runs after the parent items have been created to ensure the lookup resolution chain is intact.
| Dynamics 365 Marketing | monday CRM | Compatibility | |
|---|---|---|---|
| Contact | People Item1:1 | Fully supported | |
| Lead | People Item (Lead status column)1:1 | Fully supported | |
| Account | Company Item1:1 | Fully supported | |
| Opportunity | Deal Item1:1 | Fully supported | |
| Marketing List | Group or Board of People Itemslossy | Fully supported | |
| Campaign | Group or Board Itemlossy | Fully supported | |
| ActivityPointer (Tasks, Emails, Notes) | Item or Update on Board1:1 | Fully supported | |
| Annotation (Attachments) | File Column on Item1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Dynamics 365 Marketing gotchas
Marketing Contact billing triggers on record import
Configuration Migration Tool does not migrate high-volume transactional data
Customer Insights segments are stored separately from Dataverse CRM records
Marketing Lists and Campaign Activities have legacy schema dependencies
Custom entities require a managed solution schema, not a UI export
monday CRM gotchas
Subitems are not included in bulk exports
Daily API call limits vary sharply by plan
Legacy automations (Sentence Builder) are being deprecated
Excel and account exports only include table views
Enterprise admins can disable non-admin exports
Pair-specific challenges
Migration approach
Discovery and schema audit
We audit the source Dynamics 365 Marketing environment across the CRM layer (Contacts, Leads, Accounts, Opportunities, Activities) and the marketing layer (Marketing Lists, Campaigns, email templates, Journey definitions, Segment criteria). We identify custom entities from the managed solution schema file and document all custom fields per entity. We assess the volume of each object type and the activity history depth. The discovery output is a written migration scope document that distinguishes CRM-layer records (which migrate) from marketing-layer assets (which become the written inventory) and identifies any custom entity that requires a Monday.com CRM Column design pass.
Monday.com CRM Board and Column design
We design the destination schema in Monday.com CRM based on the Dynamics schema audit. This includes provisioning the People Board (with Contact and Lead fields as typed Columns), the Companies Board, the Deals Board (with pipeline stages as Status Columns), and any Boards needed for Campaigns and Work Items. Custom fields from Dynamics Dataverse map to Monday.com CRM Column types, with picklist values from Dynamics mapped to Monday.com Dropdown or Label Columns. We configure the Board structure before any data import so that Column types are locked and lookups can resolve at insert time.
Sandbox migration and reconciliation
We run a full migration into a Monday.com CRM test workspace using production-like data volumes. The customer's RevOps lead reviews record counts (Accounts in, Contacts in, Deals in, Activities in), spot-checks 25-50 records against the Dynamics 365 source for field accuracy and relationship integrity, and validates that Marketing List membership resolves to the correct People items. Mapping corrections, column type adjustments, and parent-record resolution failures surface in this phase, not in production. Sign-off on the sandbox pass clears the production migration to proceed.
Marketing asset inventory
We execute a separate export pass for marketing-layer assets that do not migrate to Monday.com CRM: Customer Journey definitions from msdynmkt_journey, Segment criteria from Customer Insights - Data, email template content from msdynmkt_email, and Marketing List query definitions. We deliver this as a structured written inventory document with each asset's name, object type, field names, configuration values, and trigger logic. The customer's marketing team or a Monday.com implementation partner uses this document to rebuild the assets in Monday.com or a replacement marketing automation platform. This step runs in parallel with the CRM-layer migration work.
Production migration in dependency order
We run the production migration in record-dependency order: Companies first (from Dynamics Accounts), then People (from Contacts and Leads with the status column distinguishing Lead from Contact), then Deals (from Opportunities with Account and Person lookups resolved), then Marketing List memberships (Group membership assignments on People items), then Activities and Attachments (as Updates and File Columns on the parent Items). Each phase emits a row-count reconciliation report. Delta records modified during the migration window are captured in a final pass before cutover.
Cutover, validation, and rebuild handoff
We freeze writes in Dynamics 365 Marketing during cutover, run a final delta migration of any records created or modified during the window, and confirm all Monday.com CRM Boards contain their expected record counts. We deliver the marketing asset inventory document to the customer's marketing team. We provide a one-week hypercare window for reconciliation issues raised by the customer. We do not rebuild Dynamics automations, Journeys, or marketing workflows inside the migration scope; those are separate rebuild engagements. We do not provide post-migration admin support, training, or Monday.com workflow design as standard scope.
Platform deep dives
Dynamics 365 Marketing
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Dynamics 365 Marketing and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Dynamics 365 Marketing and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Dynamics 365 Marketing and monday CRM.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Dynamics 365 Marketing: Dataverse Web API enforces organization-level throttling; specific limits vary by workload and are not publicly documented at fixed thresholds.
Data volume sensitivity
Dynamics 365 Marketing exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Dynamics 365 Marketing to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Dynamics 365 Marketing to monday CRM migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Dynamics 365 Marketing
Other ways to arrive at monday CRM
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.