Migrate from CentraHub CRM to Mailchimp

CentraHub Contact records map directly to Mailchimp Subscribers within a designated Audience. We use the Contact email address as the subscriber identifier and merge key. First name, last name, phone, and address fields map to Mailchimp's standard address and FNAME/LNAME merge fields. Subscribers are imported in batches using Mailchimp's POST lists/{list_id}/members endpoint with status set to subscribed or pending based on the contact's email opt-in value in CentraHub.

CentraHub Accounts represent company-level records. Mailchimp has no native Account or Company object, so we carry the Account name as a merge field (COMPANY) on each Subscriber. If the customer wants company-level segmentation, we create a Tag named after each unique Account and apply it to all Subscribers from that Account. The customer chooses between merge field and tagging strategy during scoping.

CentraHub Lead records map to Mailchimp Subscribers with status set to subscribed or pending based on the lead's email opt-in status. We preserve the original lead source value (from CentraHub's leadsource field) as a merge field and apply a LEAD tag to distinguish new prospects from converted Contacts in the Audience.

CentraHub Deals track opportunities in a pipeline with stage, amount, and close date. Mailchimp has no deal or opportunity object. We export Deal records as a structured JSON report for the customer's admin to import into a deal-tracking tool (Pipedrive, Zoho CRM, or a spreadsheet) or to reference during manual follow-up. The deal-to-contact relationship is not preserved as a native link in Mailchimp.

CentraHub Tags are applied across objects for segmentation and map directly to Mailchimp Tags. We extract the full tag vocabulary from each CentraHub module, deduplicate across objects, and import them as Mailchimp Tags using the POST lists/{list_id}/tagging endpoint. Tag membership is preserved per Subscriber. Tags that do not have an exact match are flagged in the migration report for the customer to review.

CentraHub custom fields per module (text, number, picklist, date, phone, email, website) map to Mailchimp Merge Fields within the destination Audience. We extract the custom field schema per module from CentraHub and create matching Mailchimp merge field definitions (type-mapped: text to text, number to number, date to date, phone to phone) before importing subscriber data. Picklist values from CentraHub become merge field options in Mailchimp.

CentraHub email Campaign records with open and click data migrate as read-only reference records in a migration inventory document. Active campaign state (scheduled sends, automation triggers) cannot migrate because Mailchimp must re-trigger sends. We export campaign name, send date, open rate, click rate, and audience size as a structured CSV that the customer can use to configure equivalent Mailchimp campaigns and set baseline performance expectations.

CentraHub Workflows automate email sends, field updates, and task creation based on trigger conditions. Mailchimp Customer Journeys are trigger-based email automations with a different action model. We do not migrate Workflows as code. We export all active CentraHub Workflow definitions as structured JSON with trigger conditions, actions, and delay rules, and deliver a written mapping to Mailchimp Customer Journey triggers and actions for the customer's marketing team to rebuild.