Migrate from cMercury to Salesforce Sales Cloud

cMercury Subscribers map to Salesforce Contacts if they represent customers or qualified buyers. Subscribers that represent marketing list members or unconverted prospects map to Salesforce Leads. We compute the split using cMercury's subscription status flag and engagement score: high engagement with purchase history suggests Contact; low engagement with no purchase history suggests Lead. The original cMercury subscriber status and engagement score migrate as custom fields (cmercury_status__c and cmercury_engagement_score__c) on both Lead and Contact for audit and re-segmentation.

cMercury Segments (filter-rule audience definitions) map to Salesforce Campaign records as static Contact lists. Each segment member's SubscriberId resolves to the migrated ContactId or LeadId. Salesforce Campaigns support CampaignMember status tracking (Sent, Responded, Opened, Clicked) which we populate from the segment's last associated campaign send history. Complex nested segment conditions that cannot be expressed as static lists are documented as Salesforce Report filters or List Views for the admin to maintain.

cMercury Campaign records map to Salesforce Campaign. Campaign name, subject line, send date, and aggregate performance stats (opens, clicks, bounces, unsubscribes) migrate as custom fields on the Salesforce Campaign record (cmercury_opens__c, cmercury_clicks__c, cmercury_bounces__c, cmercury_unsubscribes__c). Individual subscriber-level engagement history (open timestamps per subscriber) migrates to Salesforce CampaignMember records with MemberStatus set to Open or Clicked. Campaign content blocks are documented as a template reference note on the Campaign record.

cMercury templates use a proprietary drag-and-drop block structure. We extract the HTML output and image assets from each template. Pure HTML templates migrate to Salesforce Classic EmailTemplate (with IsActive and Encoding set). Templates built with cMercury's visual block editor require manual recreation in Salesforce Content Builder because block-level component mapping is not exportable. We deliver a template inventory document listing each cMercury template, its estimated block count, and a Content Builder reconstruction note. Image assets from the template are stored separately in Salesforce ContentDocument linked to the template or email send record.

cMercury Automations are trigger-delay-action sequences tied to subscriber lifecycle events. Salesforce has no equivalent automation import mechanism. We do not migrate automations as code. We document every active automation during discovery: trigger type (subscriber action, date-based, segment entry), conditions, delays, and actions. The output is a written automation inventory with recommended Salesforce Flow equivalents. The customer's admin rebuilds each automation in Flow. Complex automations with multiple branching paths require a separate scoping session before rebuild begins.

cMercury custom fields on subscriber profiles (text, number, date, dropdown) migrate to Salesforce custom fields on Contact (for customer records) or Lead (for prospect records). Field data types map to Salesforce equivalents: cMercury text to Text(255), cMercury number to Number, cMercury date to Date, cMercury dropdown to Picklist. If the same custom field applies to both Contact and Lead splits, we create it on both objects. Required field settings in Salesforce are applied per the customer's validation requirements, noting that making migrated data required may block import if source values are null.

cMercury tags are flat labels applied to subscribers. We export all tags and their per-subscriber assignments. Tags migrate to Salesforce as a custom multi-select picklist field on Contact or Lead (cmercury_tags__c). Alternatively, tags used for campaign audience classification migrate to Salesforce Campaign with the segment name stored as a Campaign custom field. The customer chooses the tag strategy during scoping.

cMercury sending domains are configured with DKIM, SPF, and DMARC records tied to cMercury's infrastructure. Sending domains cannot be transferred to Salesforce because they are bound to cMercury's DNS delegation. We document each sending domain's current DNS configuration (DKIM selector, SPF record, DMARC policy) during discovery and provide a DNS setup checklist for the customer to configure equivalent records in their domain registrar pointing to Salesforce's mail servers during cutover. This is a manual step the customer's IT or DNS administrator executes.

Images and files stored in cMercury's Asset Library are downloaded and re-uploaded to Salesforce Files (ContentDocument). Folder organization in cMercury maps to Salesforce ContentWorkspace (Library) if the destination org uses Content Libraries, or to a flat file structure with naming convention preservation. Image file names and alt text migrate as ContentVersion Title and Description fields. Files linked to specific campaigns carry a ContentDocumentLink to the corresponding Salesforce Campaign record.

cMercury tracks per-subscriber engagement scores as numeric values derived from opens, clicks, and conversion actions. We export these as numeric values and map them to a custom Number field cmercury_engagement_score__c on Contact and Lead. If the destination Salesforce org uses a scoring app from AppExchange (e.g., Salesforce Engage, High Velocity Sales scoring), we can populate the native scoring field instead if the app is installed before migration.

cMercury Verify stores per-subscriber validation status: valid, invalid, risky, or catch-all. These badges carry signal value for deliverability: previously verified addresses can be trusted on arrival to Salesforce. We preserve verification status as a custom picklist field cmercury_verification_status__c on Contact and Lead. Salesforce does not run its own email verification natively; the migrated field allows the customer's admin to suppress sending to risky or invalid addresses in Salesforce Flow or a third-party verification tool post-migration.

cMercury stores subscription status per subscriber: subscribed, unsubscribed, bounced, spam-reported. These flags map to Salesforce's standard HasOptedOutOfEmail (for unsubscribed), plus custom fields cmercury_bounce_flag__c (boolean) and cmercury_spam_report__c (boolean) on Contact and Lead. Bounce and spam report flags are preserved for suppression in any future email send from Salesforce or a connected marketing tool to prevent deliverability damage.