Migrate your cMercury data

Subscribers are the core contact records in cMercury. Each record carries email address, subscription status, engagement metrics, custom profile fields, and tags. We export all subscriber fields 1:1 and map them to the destination contact object, preserving custom field schemas.

Segments are defined by filter rules (source, engagement, custom field values). We translate segment membership rules into destination filter logic, noting that some complex nested conditions may require manual recreation in the target platform.

Campaign records include send history, subject lines, content blocks, send date, and aggregate performance stats (opens, clicks, bounces, unsubscribes). We migrate campaign metadata and content; aggregated stats are preserved as import notes on each record.

Templates use a proprietary block structure for the drag-and-drop editor. We extract HTML and image assets from templates and reassemble them into the destination system's block format, noting that some custom styling may require minor reformatting.

Automations are named workflow sequences with triggers, delays, and actions. We document the automation tree structure and trigger conditions so they can be rebuilt in the destination platform. Complex branching logic is flagged for manual review.

Custom fields on subscriber profiles are exported with their data types (text, number, date, dropdown). We preserve the full field schema and map values directly during import.

Tags are flat labels applied to subscribers. We export all tags and their assignments per subscriber. Tags are recreated as labels or static segments in the destination platform.

Sending domains are configured per account for sender reputation management. We document domain configurations and DNS settings for re-setup in the destination platform, as domains cannot be transferred between providers.

Images and files stored in the Asset Library are downloaded and re-uploaded to the destination's media library. File names and folder organisation are preserved where the destination supports folder structures.

cMercury tracks per-subscriber engagement scores. These are exported as numeric values and mapped to equivalent scoring fields in the destination, or stored as a custom property if the target platform has no native scoring object.

cMercury Verify stores validation status per email address (valid, invalid, risky, catch-all). We preserve these badges as a custom field on each contact record so the new platform can honour the verification history without re-running validation.