Migrate from monday CRM to Microsoft Dynamics 365 Sales

monday CRM People records store name, email, phone, and CRM-specific properties as a distinct entity. 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.

Deals in monday CRM are CRM-typed Items attached to a Pipeline. 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.

Each monday CRM Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the stage names. 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.

monday CRM Boards are containers that expose CRM column types. 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.

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. 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.

Subitems are nested rows inside a monday Item. 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.

monday column types map to Dynamics 365 field types: text columns become Single Line of Text or Multiple Lines of Text, number columns become Whole Number or Decimal, date columns become Date and Time, status columns become Option Set, person columns become Customer or Lookup. Formula columns and dependency columns require manual rebuild in Dynamics 365 as calculated fields or Power Automate flows. We include a column-type mapping matrix in the pre-migration schema document.

monday account Users map to Dynamics 365 Users by email match. We extract every monday User referenced as an owner, assignee, or collaborator on People, Deal, Item, or Subitem records. Users without a matching Dynamics 365 User are held in a reconciliation queue for the customer's admin to provision before record import resumes. monday's multi-level permissions and SAML SSO (Enterprise-only) do not migrate; the Dynamics 365 admin configures security roles post-migration.

monday Updates are per-Item comment threads. We preserve update text and timestamps as Note records attached to the parent Opportunity or Contact. If the monday update contains @mention references to Users, we convert those to a text annotation noting the mentioned user rather than creating a Dynamics 365 User lookup, since Notes do not support @-mention resolution.

Files uploaded to monday board Items are stored in monday's file storage. We retrieve attachment URLs via the monday API and attach them to the migrated Opportunity or Contact as Notes with a file annotation pointing to the monday-hosted URL. We do not re-upload files to Dynamics 365 SharePoint storage as part of standard scope; file migration to SharePoint is a separate deliverable if the customer requires it.