Migrate from cMercury to Zoho CRM

cMercury Subscribers are the primary contact record, carrying email address, subscription status, engagement score, custom profile fields, tags, and email verification badges. We map active, engaged Subscribers to Zoho CRM Leads. Subscribers with a defined account or company association map to Zoho Contacts tied to an Account. The split rule is defined during scoping based on the customer's subscriber lifecycle model. Email verification badges (valid, invalid, risky, catch-all) transfer to a custom Zoho field email_verification_status__c for downstream filtering.

cMercury stores company associations on Subscribers who have a business affiliation. We extract these company records and map them to Zoho CRM Accounts, using the company name as the Account Name and the domain as the Website field. Accounts are imported before any Subscriber or Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. Subscribers without a company association become standalone Leads.

cMercury Segments are defined by filter rules on subscriber properties (source, engagement, custom field values). We translate segment membership rules into Zoho CRM Filter views and optionally into a static Custom Module that replicates the segment list. Complex nested segment conditions with multiple AND/OR levels may require simplification in Zoho; we document any constraints during scoping and flag them in the mapping spec.

cMercury Campaign records include subject line, send date, content block references, and aggregate performance stats (opens, clicks, bounces, unsubscribes). We map these to Zoho CRM Campaign records with campaign type set to Email and the performance metrics stored in custom fields. Campaign content blocks migrate as Notes attached to the Campaign record; images are downloaded from the Asset Library and re-uploaded to Zoho's media library.

Tags are flat labels applied to Subscribers in cMercury. We export all tags and their assignments per Subscriber and recreate them in Zoho CRM as a multi-select picklist field on the Lead and Contact layout. If the customer has more than 150 unique tags, we discuss a threshold with them: tags above the frequency cutoff are prioritised and lower-frequency tags are grouped under a generic label.

Custom profile fields on cMercury Subscribers (text, number, date, dropdown) are exported with their data types and mapped to equivalent Zoho CRM custom fields on the Lead or Contact module. We preserve field order, display label, and data type. Dropdown fields in cMercury become Zoho picklist fields with the same option values. Validation rules in Zoho that restrict values to a picklist are coordinated with the customer's admin before import to avoid record rejection.

cMercury stores email, call, meeting, and task engagement history per Subscriber. We map these to Zoho CRM Activities: emails map to Notes with an Email check flag; calls map to Zoho Calls with duration and disposition; meetings map to Events with start time, end time, and location; tasks map to Tasks with due date and status. Activity records are linked to the parent Lead or Contact via the WhoId reference. Historical timestamps are preserved by setting ActivityDate to the original cMercury timestamp.

cMercury Verify stores per-email validation status (valid, invalid, risky, catch-all) as a badge on each Subscriber record. We export these badges and map them to a Zoho CRM custom picklist field email_verification_status__c on both Lead and Contact. This allows the customer's sales and marketing teams to filter by deliverability quality before sending from Zoho or any integrated email tool.

cMercury tracks per-Subscriber engagement scores as numeric values. We export the raw score and map it to a Zoho CRM custom number field engagement_score__c on Lead and Contact. If Zoho CRM Plus or higher is in use, this field can feed into Zoho CRM's native scoring model. For Standard tier, the field serves as a read-only reference value that the customer's admin uses manually for segmentation.

cMercury templates use a proprietary block structure for the drag-and-drop editor. We extract the HTML source and image asset URLs from each template and store them as Notes on a Template documentation record in Zoho CRM. The actual email template cannot be rebuilt automatically because Zoho's email template format is structurally different; we document the layout structure and image placements so the customer's admin can reconstruct templates in Zoho's Email Template editor.

cMercury sending domains are configured with DKIM, SPF, and DMARC records tied to cMercury's mail infrastructure. These records cannot be exported or transferred to Zoho CRM. We document each sending domain's current DNS configuration during discovery and provide a DNS reconfiguration checklist (new DKIM records, updated SPF, DMARC policy alignment) for the customer's IT team to apply before cutover. Deliverability history associated with the sending domain does not carry over.