Migrate from cMercury to HubSpot

cMercury subscribers map 1:1 to HubSpot contacts. Primary email address becomes the HubSpot contact email. First name, last name, phone, and custom properties migrate as standard or custom contact properties. Subscriber status (active/unsubscribed/bounced) maps to HubSpot's contact email status. If a subscriber lacks an email address, we flag the record for manual review and can assign a placeholder for import.

cMercury tags applied to subscribers translate to HubSpot static lists. Each unique tag becomes a static list in HubSpot. Subscribers with multiple tags land in multiple HubSpot lists. Dynamic segments (rules-based) map to HubSpot smart lists with equivalent filter conditions.

cMercury audience segments with static membership become HubSpot static lists. Segments with rule-based membership (behavioral triggers, property filters) become HubSpot smart lists with equivalent filter logic translated to HubSpot's criteria format. During migration, we verify that each segment's rule logic is correctly represented in HubSpot's filter builder, and we provide a mapping sheet for your review.

cMercury company records (when subscriber-to-company associations exist) map to HubSpot company records. Company name, domain, industry, employee count, and annual revenue fields map to HubSpot company properties. Parent-child company hierarchies in cMercury map to HubSpot's parent company field. If a company lacks a domain, we use the provided name as a fallback identifier.

cMercury allows N:N subscriber-to-company associations. HubSpot contacts have one primary company (AccountId) plus optional additional associations via Account Contact Relationships. We map the most-recently-associated company as primary and surface additional associations as relationship records. If you prefer a different primary company rule (e.g., alphabetical or manually flagged), we can adjust the mapping logic before migration runs.

cMercury campaign records (name, subject, send date, send status) migrate to HubSpot campaigns. The individual email content does not migrate as email template data but campaign metadata and send history are preserved as HubSpot campaign records linked to recipient contacts.

Per-subscriber engagement history (opens, clicks, unsubscribes, bounces) migrates as HubSpot contact timeline events. Each engagement type creates a separate timeline entry with the original timestamp and campaign context preserved as custom properties on the event. The timeline entries appear under the contact's 'Activity' section, allowing you to filter by engagement type and date range for reporting.

cMercury custom subscriber properties map to HubSpot custom contact properties. Property types (text, number, date, picklist, checkbox) are translated to HubSpot's corresponding field types. Picklist values require value-by-value mapping where cMercury picklist options differ from HubSpot's default options. During scoping, we provide a property mapping spreadsheet so you can review, rename, or consolidate fields before migration begins.

cMercury form submission data migrates as HubSpot contact records (for new contacts) plus a form submission timeline event containing the original form name, submission date, and field values. This preserves the lead capture context in HubSpot's contact timeline. The timeline entry also includes the page URL where the form was submitted, enabling you to track the source of each lead within HubSpot's analytics.

cMercury email automation sequences (welcome series, drip campaigns, behavioral triggers) do not have a direct HubSpot equivalent for automated migration. We export the automation definitions as a workflow specification document for your HubSpot admin to rebuild using HubSpot's workflow engine post-migration.