CRM migration
Field-level mapping, validation, and rollback between Microsoft Dynamics 365 Sales and monday CRM. We move data and schema; workflows are rebuilt natively in monday CRM.
Microsoft Dynamics 365 Sales
Source
monday CRM
Destination
Compatibility
7 of 10
objects map 1:1 between Microsoft Dynamics 365 Sales and monday CRM.
Complexity
BStandard
Timeline
4-6 weeks
Try the reverse
Overview
Moving from Microsoft Dynamics 365 Sales to Monday.com CRM is an architectural migration, not a table-to-table copy. 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.
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.
Source platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Destination platform
monday CRM platform overview
Scorecard, SWOT, gotchas, and pricing for monday CRM.
Data migration guide
The complete monday.com CRM migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Source platform guide
Microsoft Dynamics 365 Sales migration guide
Understand the data you're exporting from Microsoft Dynamics 365 Sales before mapping it.
Destination checklist
monday.com CRM migration checklist
Pre- and post-cutover tasks for moving onto monday CRM.
Source checklist
Microsoft Dynamics 365 Sales migration checklist
Exit checklist for unwinding your Microsoft Dynamics 365 Sales setup cleanly.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Microsoft Dynamics 365 Sales 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.
Microsoft Dynamics 365 Sales
Account
monday CRM
Company board (People or Company board)
1:1Dynamics Account records map to item records on a Monday.com Company board. 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.
Microsoft Dynamics 365 Sales
Contact
monday CRM
People board item or linked record
1:1Dynamics 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. 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.
Microsoft Dynamics 365 Sales
Lead
monday CRM
People board item (Lead status)
1:1Dynamics Lead records do not have a direct Monday.com CRM equivalent; Monday.com has no separate Lead entity. 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.
Microsoft Dynamics 365 Sales
Opportunity
monday CRM
Deals board item
1:1Dynamics Opportunity records map to item records on a Monday.com Deals board. 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.
Microsoft Dynamics 365 Sales
Quote / Order / Invoice
monday CRM
Deals board sub-items or linked records
1:manyDynamics Quotes, Orders, and Invoices form a commercial document chain with line items and product references. 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.
Microsoft Dynamics 365 Sales
Product and Price List
monday CRM
Products board
1:1Dynamics Products and Price Lists map to a Products board in Monday.com. 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.
Microsoft Dynamics 365 Sales
Activity (Task, Email, Phone Call, Appointment)
monday CRM
Update log or sub-item on parent board
lossyDynamics activity records (Tasks, Emails, Phone Calls, Appointments) are stored as separate Dataverse entities with type, date, owner, and description. Monday.com does not have a native activity timeline object. We map activities as Updates on the parent board item (the Contact, Lead, or Deal it is attached to), with the activity type, date, and body as the update text. Alternatively, for customers who need a separate activity record, we create a dedicated Activity board and map activities as items with a Type dropdown, Date column, and Person column for owner assignment. The mapping approach is chosen during scoping based on the customer's reporting needs.
Microsoft Dynamics 365 Sales
User / Owner
monday CRM
Workspace member (Person column)
1:1Dynamics Owner records map to Monday.com workspace members by email match. We extract all OwnerIds referenced on CRM records, match them against the Monday.com workspace member list, and use the Monday.com member ID as the Person column value on items. Any Owner without a matching Monday.com member is flagged in the pre-migration reconciliation report for the admin to provision before migration resumes. We also flag inactive Dynamics owners that would otherwise create orphan assignments at the destination.
Microsoft Dynamics 365 Sales
Custom Table (Professional Tier)
monday CRM
Custom board or columns on existing board
lossyDynamics custom tables on the Professional tier (up to 15) map to Monday.com boards with a column structure that mirrors the custom table's fields. Option-set fields on Dynamics custom tables become Monday.com dropdown columns; text fields become text columns; number fields become number columns. We flag any Dynamics custom table using a field type that has no Monday.com equivalent (complex multi-select option sets, customer lookup fields) and document the limitation with a recommended workaround, either a text column with concatenated values or a separate lookup board.
Microsoft Dynamics 365 Sales
Note and Attachment
monday CRM
Update or file attachment on board item
1:1Dynamics Notes migrate as text updates on the corresponding Monday.com board item. Attachments stored in Dynamics (SharePoint or Dataverse blob storage) are downloaded and re-uploaded as file attachments on the Monday.com item using Monday.com's file upload API. SharePoint attachment URLs that require authentication do not transfer as live links; we download the file content and attach it directly. Large attachment sets (over 5 GB total) require a staged upload plan coordinated with the customer.
| Microsoft Dynamics 365 Sales | monday CRM | Compatibility | |
|---|---|---|---|
| Account | Company board (People or Company board)1:1 | Fully supported | |
| Contact | People board item or linked record1:1 | Fully supported | |
| Lead | People board item (Lead status)1:1 | Fully supported | |
| Opportunity | Deals board item1:1 | Fully supported | |
| Quote / Order / Invoice | Deals board sub-items or linked records1:many | Fully supported | |
| Product and Price List | Products board1:1 | Fully supported | |
| Activity (Task, Email, Phone Call, Appointment) | Update log or sub-item on parent boardlossy | Fully supported | |
| User / Owner | Workspace member (Person column)1:1 | Fully supported | |
| Custom Table (Professional Tier) | Custom board or columns on existing boardlossy | Fully supported | |
| Note and Attachment | Update or file attachment on board 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.
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
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 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. 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.
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. 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.
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. 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.
Data quality preparation
We run a pre-migration data quality pass on the Dynamics source. 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.
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. 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.
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. 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.
Platform deep dives
Microsoft Dynamics 365 Sales
Source
Strengths
Weaknesses
monday CRM
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. All 8 core objects map 1:1 between Microsoft Dynamics 365 Sales and monday CRM.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Microsoft Dynamics 365 Sales and monday CRM.
Object compatibility
All 8 core objects map 1:1 between Microsoft Dynamics 365 Sales 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
Microsoft Dynamics 365 Sales : Per-user and per-environment request limits enforced across Power Platform; exact limits vary by license tier and environment capacity.
Data volume sensitivity
Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales to monday CRM migration scoping. Not seeing yours? Book a call.
Walk through your Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales
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.