Migrate from cMercury to Microsoft Dynamics 365 Sales

cMercury Subscribers map to Microsoft Dynamics 365 Sales Contact records. We use the subscriber email address as the primary key and derive a Company Name field (or use a custom company field) to create or match a parent Account. For subscribers with a recognisable domain, we group them under a matching Account during import. All cMercury custom profile fields translate to Dataverse custom fields on the Contact record. Tags migrate as a multi-select custom field or as a separate Tag custom entity with a lookup to Contact. The Account is created first so that the Contact-to-Account lookup is satisfied at insert time.

cMercury stores per-subscriber engagement scores as numeric values. Microsoft Dynamics 365 Sales has no native engagement scoring field. We create a custom decimal field on Contact — typically named cm_engagement_score__c — and import the numeric value directly. If the customer uses a tiered scoring model (e.g., cold/warm/hot), we optionally create a second custom picklist field to preserve the tier label alongside the raw score.

cMercury Verify stores validation status per email address (valid, invalid, risky, catch-all). We preserve this as a custom picklist field on Contact — typically cm_verification_status__c — with the original cMercury status value. This allows the customer's sales team to see delivery risk at a glance without re-running verification. We do not suppress invalid addresses automatically; the customer decides their policy on bounced or risky contacts.

cMercury Segments are defined by filter rules against subscriber properties, engagement behaviour, and custom field values. We document each segment's filter conditions during discovery and translate them into Microsoft Dynamics 365 Sales Contact views or Power Automate-based dynamic lists. Complex nested conditions that exceed the Dynamics filter builder are noted as requiring manual segmentation or a Power Automate flow to maintain equivalent membership over time.

cMercury campaign records include send history, subject lines, and aggregate open, click, bounce, and unsubscribe rates. Microsoft Dynamics 365 Sales has no native campaign performance module comparable to marketing automation platforms. We preserve aggregate campaign metrics as a custom CampaignHistory entity linked to Contact, storing campaign name, send date, opens, clicks, and bounces per campaign per subscriber. Alternatively, for simpler migrations, we attach campaign summaries as Notes on each affected Contact record. The customer chooses the approach during scoping.

cMercury templates use a proprietary block structure for the drag-and-drop editor. We extract HTML content and image assets from each template. HTML is converted to Dynamics 365 Email Template format or stored in a SharePoint Document Library with a naming convention matching the cMercury template folder structure. Image assets are downloaded and re-uploaded to the SharePoint media library. Layout fidelity depends on the complexity of the original template; heavily customised block-based designs may require manual adjustment in Dynamics.

cMercury sending domains are configured with DKIM, SPF, and DMARC records pointing to cMercury infrastructure. These records cannot be transferred to any destination. We provide a DNS checklist during cutover that documents the existing record values from cMercury so that the customer can configure equivalent DNS records for Microsoft Dynamics 365 Sales or their chosen sending platform. The checklist covers TXT records for SPF, CNAME records for DKIM, and DMARC policy records. Deliverability testing follows DNS propagation.

Images and files stored in the cMercury Asset Library are downloaded and re-uploaded to a SharePoint Document Library that the Microsoft Dynamics 365 Sales environment is connected to. Folder organisation and file names are preserved where SharePoint folder structure supports it. Image references in migrated templates are updated to point to the new SharePoint URLs. This preserves the visual assets used in historical and future email campaigns.