Migrate from HubSpot to Mailchimp

HubSpot Contact records map 1:1 to Mailchimp subscribers in the target audience. We map every HubSpot standard contact property (firstname, lastname, email, phone, address, lifecycle stage, lead status, hs_lead_source) and all custom contact properties to Mailchimp merge fields. Merge fields are created in Mailchimp before import on Standard plan or higher. Free and Starter plans on HubSpot cannot use custom field mappings with the Mailchimp integration — we handle this via the Mailchimp API directly, bypassing the native integration limitation. The HubSpot marketing-contact billing flag is stored as a custom merge field (hs_marketing_contact__c) for future segmentation.

HubSpot Company records have no direct Mailchimp equivalent because Mailchimp has no Company or Account object. We map company data by extracting the HubSpot company domain and name and applying them as subscriber tags on the associated contacts (tag format: company:acme-corp). Multiple contacts sharing the same company receive the same tag, enabling the customer to segment by company in Mailchimp. Company properties other than name and domain are preserved as custom merge fields on the primary contact record or documented in the handoff inventory for manual entry.

HubSpot Deals have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not include deal tracking, pipeline stages, deal amounts, or close dates. We flag the total deal count and pipeline value during scoping and deliver a written inventory of all active and historical Deals grouped by pipeline and stage so the customer's admin can document them externally or choose a CRM alternative (Pipedrive, Streak) if deal tracking is essential.

HubSpot Pipeline configurations (stages, probabilities, automation triggers per stage) have no Mailchimp equivalent. Mailchimp automations are email-centric and do not model a sales pipeline. We deliver a written inventory of all HubSpot pipeline names, stage names, and stage probabilities for the customer's admin to use as reference documentation if a pipeline tracking tool is adopted in the future.

HubSpot Lead records (Enterprise tier only, introduced 2023) map to Mailchimp subscribers with the HubSpot lead_status and lifecyclestage properties preserved as custom merge fields. Lead scoring values migrate as a numeric merge field. Because Mailchimp does not have a separate Lead and Contact model, all HubSpot contacts and leads land in the same Mailchimp audience and are distinguished by their lifecycle stage and status merge fields.

HubSpot Products map to Mailchimp Products if the customer is on a Mailchimp plan that includes e-commerce integration (Standard or Premium). Product name, SKU (hs_sku), description, and price migrate to Mailchimp Product records. Products are required for Mailchimp Automation Abandoned Cart and Product Follow-Up journeys. If the customer does not have e-commerce enabled, we document the product catalog for manual entry.

HubSpot email engagement history (sent, opened, clicked, bounced records) does not migrate to Mailchimp because Mailchimp's subscriber activity records are email-platform-specific and begin recording only when the subscriber engages with a Mailchimp campaign. We deliver a summary count of total emails sent, open rate, and click rate per HubSpot contact as a merge field (hs_email_stats__c) for reference but do not recreate the engagement timeline.

HubSpot call, meeting, and task engagements have no Mailchimp equivalent. Mailchimp does not store call logs, meeting records, or task items. We flag the total activity count per contact during scoping and deliver a written inventory of engagement types and volumes so the customer understands the scope of what will not transfer.

HubSpot Tickets have no Mailchimp equivalent. Mailchimp is not a support or service management platform. We deliver a written inventory of open and closed tickets grouped by ticket pipeline and status for the customer's admin to reference if a dedicated support tool is adopted.

HubSpot custom objects (Enterprise-only) have no Mailchimp equivalent. Mailchimp's data model is subscriber-centric and does not support custom record types. If the customer has custom object data that must be preserved, we recommend migrating those records to a CRM platform (Pipedrive, Salesforce, or HubSpot CRM) in parallel and syncing the subscriber audience to that CRM via Mailchimp's native CRM integrations.