Migrate from noCRM.io to Microsoft Dynamics 365 Sales

noCRM Leads with status Won or Lost map to Salesforce-style Contacts (or Cases if service history matters) — the noCRM status determines the destination. noCRM Leads with status To-Do or Standby map to Microsoft Dynamics 365 Sales Lead for continued qualification. We use the noCRM lead status field and any custom status fields to drive the split rule, and preserve the original noCRM status in a custom field nocrm_original_status__c on the destination record for audit trail and future segmentation.

Each noCRM Pipeline Step becomes a Dynamics 365 Opportunity StageName value within a Sales Process we create per noCRM Pipeline. The step order, probability, and stage category (Open, Won, Lost) migrate to the corresponding Dynamics stage configuration. Step transition history is preserved as a custom field transition_log__c in JSON format since Dynamics does not natively track stage-change audit at the field level.

noCRM Pipelines (Expert and Dream tiers; Starter limited to one) map to Microsoft Dynamics 365 Sales Record Types on Opportunity. Each Record Type gets its own Sales Process whitelisting only the relevant Stage values, so that a B2B pipeline's stages do not appear on an SMB pipeline's UI. Starter accounts with one pipeline create one Record Type and one Sales Process.

noCRM Prospecting Lists store a membership list of Leads. We export list membership and map it to Dynamics 365 Customer Insights - Journeys Segments (if the customer licenses that module) or to a custom Static List entity in Dataverse. Membership is re-established by matching the Lead email to the migrated Contact or Lead record in Dynamics.

noCRM tags are freeform string labels applied to Leads. We preserve all tags and map them to a Dynamics multi-select picklist field on the Lead or Contact record. If the tag count exceeds the Dynamics multi-select picklist limit of 150 values, we create a custom Tag entity with a many-to-many relationship to Lead and Contact and populate TagAssignment records.

Each noCRM Lead carries a chronological activity log with comments, status changes, and manual entries. We map these to Dynamics Note records linked via Annotation to the migrated Lead or Contact, with the original timestamp and author preserved. Status-change entries that represent milestones (e.g., To-Do to In Progress) are also written as Task records with a milestone subject for timeline visualization.

Files attached to noCRM Leads export as binary blobs with file name and mime type. We re-attach them in Dynamics as Note records with an is_document flag or as SharePoint file attachments on the related Account or Contact record. SharePoint document storage requires the SharePoint Integration feature to be enabled in Dynamics; if not available in the customer's current license, we attach files directly to Note records instead.

noCRM Users assigned to Leads map to Dynamics 365 User records resolved by email match. Role and permission structures are account-specific in noCRM and do not transfer directly; we document the role mapping during scoping and the customer's Dynamics admin re-establishes role assignments post-migration. Inactive noCRM users who still own historical records are mapped to inactive Dynamics users to preserve the owner reference.

noCRM Predefined Fields are custom properties configured under Admin > Sales process. We extract the field definitions (label, type, required flag, options) and map them to equivalent Dynamics custom fields on the Lead or Contact entity with matching field types. If a noCRM field type has no direct Dynamics equivalent (e.g., a URL field stored as plain text), we use the closest Dynamics type and document the mapping assumption. Field-level security and validation rules in Dynamics must be configured by the customer's admin after migration.