Migrate from ConvergeHub to Mailchimp

ConvergeHub Contacts migrate to Mailchimp Subscribers within the destination Audience. We map email address as the subscriber key (email_id), first name to FNAME, last name to LNAME, phone to PHONE, and any custom fields to Mailchimp merge fields (created as MERGEname format during scoping). Contact status in ConvergeHub (Active, Inactive) maps to subscribed/unsubscribed in Mailchimp. The Contact-to-Account linkage is preserved by creating a Mailchimp Company merge field carrying the Account name for reference.

ConvergeHub Leads with a populated email address migrate to Mailchimp Subscribers. Leads without an email address are flagged during scoping because Mailchimp requires a valid email for subscriber creation. Lead source, Lead status, and owner assignment are preserved in custom merge fields lead_source__c, lead_status__c, and owner_email__c so the customer can segment new subscribers by original lead origin.

Mailchimp supports a Company merge field and the Audiences -> Contact profiling feature which lets subscribers associate with a Company profile. We map ConvergeHub Account name to Company, Account industry to Industry, and Account size to the related Company merge fields. Company relationships are used for segmentation in Mailchimp but do not become separate objects; the subscriber remains the primary record.

ConvergeHub segments (static or dynamic lists based on filter criteria) are translated to Mailchimp Tags. We document each ConvergeHub segment's filter logic during scoping and recreate equivalent Mailchimp Tagging rules or Segments using the same criteria. Tags enable the customer to re-run segments in Mailchimp as new contacts are added.

ConvergeHub's email opt-in and opt-out flags on Contact and Lead records map to Mailchimp's GDPR and marketing consent fields. We preserve consent language, opt-in date, and consent source in merge fields for compliance. Unsubscribed and bounced contacts from ConvergeHub are imported as suppressed contacts in Mailchimp to prevent accidental re-sending.

ConvergeHub custom fields on Contacts and Leads (such as custom picklists, text fields, date fields, and numeric fields) are created as Mailchimp Merge Fields during setup. Picklist values from ConvergeHub become merge field option labels. Date fields are stored as text in YYYY-MM-DD format. Multi-select fields are concatenated with a delimiter. The customer chooses merge field names during scoping to match Mailchimp naming conventions.

ConvergeHub Deals (pipeline opportunities with stage, value, probability, and owner) have no equivalent object in Mailchimp. Mailchimp tracks customer interactions but does not maintain a sales pipeline. We export Deal records as a CSV for the customer's reference and note that pipeline data does not migrate. If the customer needs pipeline tracking post-migration, they should retain ConvergeHub for Deal management or adopt a separate CRM.

ConvergeHub Cases (support tickets with priority, status, subject, and linked Contact or Account) have no equivalent in Mailchimp. Case history, support interactions, and case-related notes do not migrate. If the customer maintains a customer service operation, they need a dedicated helpdesk platform post-migration.

ConvergeHub Activities (logged calls, tasks, events, and meeting records) do not map to Mailchimp. Mailchimp tracks opens, clicks, and unsubscribes for email campaigns, but not the historical activity timeline from a CRM. We do not migrate activity records. The customer should preserve activity history in an exported CSV if needed for compliance or audit purposes.

ConvergeHub Invoices and Products have no Mailchimp equivalent. Invoice records, line items, payment status, and product catalog data do not migrate. If the customer uses ConvergeHub for billing and needs to retain this history, they should export to CSV before migration and consider a dedicated accounting platform post-migration.