Migrate from cMercury to HighLevel

cMercury Subscriber records map directly to GoHighLevel Contact records. Email address serves as the primary dedupe key. Subscription status, profile custom fields, and tags transfer as native GoHighLevel Contact fields and tag assignments. cMercury Verify badges (valid, invalid, risky, catch-all) migrate to a custom Contact field cmercury_verify_status__c so the destination honours prior verification results without re-running validation. Engagement scores migrate to a numeric custom field cmercury_engagement_score__c for segmentation and reporting.

cMercury Segments defined by filter rules (engagement level, custom field values, subscription status) translate to GoHighLevel Smart Lists with the equivalent filter conditions. Simple segments (single-condition rules) map cleanly. Complex nested conditions with three or more AND/OR layers may require a GoHighLevel Advanced Filter or a manual Smart List reconstruction by the admin during post-migration setup.

cMercury Campaign records (subject, content, send date, aggregate open/click/bounce stats) migrate to GoHighLevel Campaign records with the historical performance data stored as campaign custom fields. The campaign content body does not auto-populate a GoHighLevel email template; we extract the HTML and map it to a GoHighLevel Email Template during migration, noting that cMercury's block structure may require manual formatting adjustment in the GoHighLevel editor.

cMercury templates use a proprietary block structure for the drag-and-drop editor. We extract the HTML output and reassemble it into a GoHighLevel Email Template. Image assets embedded in templates download from cMercury's Asset Library and re-upload to GoHighLevel's Media Library, preserving file names. Layout fidelity depends on block complexity; templates with heavy use of cMercury's specific layout components may require a visual review and manual adjustment post-migration.

Custom fields on cMercury Subscriber profiles (text, number, date, dropdown, checkbox) map directly to GoHighLevel Contact Custom Fields with equivalent data types. We preserve field labels and API names where possible and drop any that conflict with GoHighLevel reserved field names by appending a __c suffix. Dropdown options in cMercury transfer as GoHighLevel picklist options on the equivalent custom field.

Tags are flat labels applied to cMercury Subscribers. We export all tags and their assignments per Subscriber and recreate them as GoHighLevel Tags on the migrated Contact records. Tags used for audience segmentation in cMercury inform the Smart List design but are applied as GoHighLevel Tags rather than segment memberships since GoHighLevel segments are filter-based rather than label-based.

Images and files stored in the cMercury Asset Library download in full and re-upload to GoHighLevel's Media Library. File names and folder organization are preserved where the destination supports folder structure. Large image assets (over 10 MB) are flagged for the admin to assess whether compression is needed before re-upload to avoid storage bloat.

cMercury tracks per-Subscriber engagement scores as a numeric value. These scores export as a number and map to a custom Contact field cmercury_engagement_score__c. GoHighLevel does not have a native engagement scoring object, so the score serves as a reference metric in Smart Lists and reporting rather than a native GoHighLevel scoring feature. Customers planning to use GoHighLevel's own automation-based scoring should set up new scoring logic post-migration.

cMercury sending domains are configured with DKIM, SPF, and DMARC records tied to cMercury's mail infrastructure. Domain ownership does not transfer between platforms. We document each sending domain's current DNS configuration during discovery and provide a DNS checklist for the admin to configure in GoHighLevel (LC Email via Mailgun) at cutover. Deliverability should be tested after DNS propagation before sending at volume from the new infrastructure.