Migrate from Simplicity Enterprise CRM to Microsoft Dynamics 365 Sales

Simplicity CRM Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (full name, email, phone, address) map cleanly. Because Simplicity's schema is configurable, we enumerate every active custom field on Contact during discovery and map each to a typed Dataverse column or custom field provisioned before import. Email address becomes the dedupe key during insertion.

Simplicity CRM Company records map to Microsoft Dynamics 365 Sales Account. Company name becomes the Account Name field, and any industry or classification custom fields translate to typed picklist or text fields on Account. Account is inserted before Contact so that the ParentAccountid lookup is satisfied at Contact import time.

Simplicity CRM Deal records map to Microsoft Dynamics 365 Sales Opportunity. Pipeline stages from Simplicity map to Opportunity StageName values, which we configure as a Sales Process in the destination org before migration. Deal value, close date, and probability migrate to Amount, CloseDate, and Probability fields. Any Simplicity deal custom fields map to custom Opportunity fields provisioned in Dataverse.

Each Simplicity pipeline becomes a Microsoft Dynamics 365 Sales Record Type on Opportunity with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages round to the nearest integer allowed by Salesforce Dataverse. Stage names translate through an explicit value-mapping table built during the discovery phase.

Simplicity CRM Activities (emails, calls, meetings, notes) linked to Contact or Company parents migrate to Microsoft Dynamics 365 Sales EmailMessage and ActivityPointer (Task) records. We preserve the parent-child relationship by resolving the Contact or Account lookup at migration time. Call duration and disposition map to custom Task fields. Meeting location and duration map to Event Location and Duration fields. Activity timestamps preserve ordering in the Dynamics timeline.

Simplicity CRM Campaign records migrate to Microsoft Dynamics 365 Sales Campaign. Campaign name, type, status, and budget amounts map directly. Campaign dates migrate to StartDate and EndDate. We do not migrate CampaignMember response records as Dynamics CampaignResponse entities unless explicitly scoped; instead, campaign-to-contact response history migrates as tagged activity records so that the behavioral signal is preserved in the contact timeline.

Simplicity CRM segment membership defines which contacts belong to behavioral or demographic groups. Segment membership does not map directly to a standard Dynamics object. We translate static segments to a custom Contact field (multi-select picklist) and dynamic segments to a Power Automate flow or a Dataverse calculated field logic that recreates the segment criteria. The customer chooses the strategy during scoping.

Simplicity CRM loyalty data (reward tiers, point balances, program membership) is relational and has no native Microsoft Dynamics 365 Sales equivalent. We provision a custom Dataverse entity with fields for membership ID, tier, point balance, and program name, then migrate membership records linked to Contact. If the destination org cannot accommodate a custom entity, we archive loyalty data as a structured JSON attachment on the Contact record. This is documented explicitly during scoping.

Simplicity CRM stores social follower and interaction data integrated within the platform. Microsoft Dynamics 365 Sales does not have a native social data object. We archive social data as Note or Annotation records attached to the relevant Contact, preserving the interaction type, date, and summary. The customer admin decides whether to surface these in the timeline or leave them as background reference.

Simplicity CRM's configurable data structure means custom fields exist on nearly every object. During schema discovery we enumerate every active custom field and its data type for the specific client instance. We provision matching custom fields in Dataverse before migration begins, including picklist values translated through an explicit option-set mapping. Custom field proliferation is the primary driver of migration complexity in this pair.