Mailchimp to HubSpot migration
Moving from Mailchimp to HubSpot puts your contact records inside a full CRM context instead of an audience-centric email platform. FlitStack AI maps every subscriber, tag, group membership, and campaign engagement history to HubSpot contacts, companies, and custom properties — preserving original timestamps and source audience IDs so your HubSpot instance reflects the full picture from day one.
FlitStack AI migrates contacts, list membership + custom properties, custom property on contacts, contact property or list memberships and contact properties from Mailchimp to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 24–72 hours for under 25,000 subscribers.

What moves from Mailchimp to HubSpot?
Mailchimp organizes data around Audiences and Subscribers — a flat contact model with tagging, grouping, and campaign engagement tracking per subscriber.
Read the full summary
HubSpot uses a relational CRM model with Contacts, Companies, Deals, and lifecycle stages, where engagement history lives in a native timeline tied to HubSpot-sent emails and forms. The migration carries subscriber records, all custom merge-field data, tag assignments, and group memberships into HubSpot contacts and custom properties. The most substantive gaps are automations (Mailchimp automation workflows have no native HubSpot equivalent and must be rebuilt), campaign engagement history (Mailchimp open/click rates per subscriber migrate as static custom properties on contacts since HubSpot's timeline tracks HubSpot-sent emails), and audience membership flags (which require HubSpot list membership or a custom property to replicate Mailchimp's audience-level subscriber status). FlitStack AI sequences the migration using Mailchimp's API export — validated, deduplicated by email, and enriched with campaign engagement history before writing into HubSpot via the Contacts API.
Subscriber (Contact Record) → Contact
Mailchimp subscribers map directly to HubSpot contacts by email address as the primary deduplication key.
How it maps
All subscriber records are matched against existing HubSpot contacts using email; duplicates are merged rather than created. Subscribers without a valid email address are flagged in a quarantine list for manual review before migration to prevent data integrity issues.
Audience → List Membership + Custom Property
Mailchimp audiences have no direct HubSpot equivalent since HubSpot maintains one unified contact database.
How it maps
We create a HubSpot list for each Mailchimp audience and add a custom boolean property (Audience_Name__c) set to true for members. Subscribers appearing in multiple Mailchimp audiences receive all corresponding audience properties, preserving the complete membership history.
Merge Field → Custom Property on Contact
Standard Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS) map to HubSpot native contact properties using the standard field names.
How it maps
Custom merge fields created per audience are migrated as HubSpot custom properties, preserving the original data type — text fields become single-line text properties, number merges become number properties, and date fields become date properties in HubSpot.
Tag → Contact Property or List Membership
Mailchimp tags are cross-audience labels attached to subscribers without hierarchical structure.
How it maps
We map tags to HubSpot contact properties by default, using a multi-select property or multiple single-select boolean properties depending on tag count. Alternatively, tags can map to HubSpot lists if the tag functions as a segment equivalent for dynamic list membership. The strategy is chosen during the planning phase.
Group → Contact Property
Mailchimp groups are interest-based categories within an audience that allow subscribers to self-select preferences such as product interest, subscription tier, or communication frequency.
How it maps
Each group maps to a dedicated HubSpot contact property named by group category, with the group name preserved exactly as the option label. Group categories define the property API name while group names become the selectable options.
Campaign (Send History) → Custom Properties on Contact
Mailchimp maintains detailed engagement records per subscriber including opens, clicks, and sends for each campaign in the send history.
How it maps
HubSpot's native timeline only tracks engagement with emails sent from HubSpot itself. Historical Mailchimp campaign metrics are migrated as static custom properties on each contact, including Last_Mailchimp_Campaign_Date__c, Mailchimp_Open_Count__c, and Mailchimp_Click_Count__c for reporting continuity.
- SubscriberContact1:1
- AudienceList Membershipmerged
- Merge FieldCustom Property on Contacttransformed
- TagContact Property or List Membershiptransformed
- GroupContact Propertytransformed
- CampaignCustom Properties on Contacttransformed
+ 6 more in the mapping below
How Mailchimp and HubSpot differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Mailchimp | HubSpot |
|---|---|---|
| Core object model | Mailchimp: Audience → Subscriber (flat contact list with tags and groups). One subscriber can belong to multiple audiences. | HubSpot: Contact → Company → Deal (relational CRM with lifecycle stages, primary company association, and multi-object associations). |
| Contact property extensibility | Mailchimp: Merge fields (FNAME, LNAME, custom merges) per audience; tags are cross-audience labels. | HubSpot: Standard + custom properties on Contact; tags are global; lifecycle_stage is a built-in property with defined transitions. |
| Campaign engagement tracking | Mailchimp: Tracks opens, clicks, and sends per subscriber across all campaigns; stored in subscriber profile. | HubSpot: Native timeline tracks engagement with HubSpot-sent emails and forms; historical Mailchimp data requires custom properties. |
| Automation / sequences | Mailchimp: Automation workflows (Customer Journeys) with triggers, conditions, and email sends. | HubSpot: Workflows (enrollment-based, separate from Deals and Tickets). No direct automation transfer. |
| Audience model | Mailchimp: Multiple audiences; subscribers can appear in one or more. Email address uniqueness not enforced across audiences. | HubSpot: One contact database; deduplication by email is default. Multiple audiences require consolidation strategy. |
| Pricing basis | Mailchimp: Free up to 500 subscribers; $13/mo for 500; $59/mo for 5,000; $99/mo for 10,000 subscribers. | HubSpot Starter: $20/mo includes 1,000 contacts; Professional starts at $890/mo with full CRM features and marketing tools. |
| List vs. segment model | Mailchimp: Lists (audiences) and Segments (dynamic filters on list members). | HubSpot: Lists (static or dynamic) and Smart Lists based on contact properties and lifecycle stage. |
Mailchimp to HubSpot field mapping
The 30 most-used fields of 32 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.
-
email_addressSubscriberemailContact -
first_nameSubscriberfirstnameContact -
last_nameSubscriberlastnameContact -
phone_numberSubscriberphoneContact -
address_line_1SubscriberaddressContact
| Mailchimp field | HubSpot field | Mapping | Note |
|---|---|---|---|
Subscriber.email_address | Contact.email | direct | |
Subscriber.first_name | Contact.firstname | direct | |
Subscriber.last_name | Contact.lastname | direct | |
Subscriber.phone_number | Contact.phone | direct | |
Subscriber.address_line_1 | Contact.address | direct | |
Subscriber.city | Contact.city | direct | |
Subscriber.state_region | Contact.state | direct | |
Subscriber.postal_code | Contact.zip | direct | |
Subscriber.country | Contact.country | direct | |
Subscriber.opt_in_status | Contact.emailoptout | value_mapping | Mailchimp opt-in flags map to HubSpot's email opt-out property. Double opt-in status preserved as a custom boolean field. |
Subscriber.stats.rating | Contact.hs_analytics_num_page_views | transformed | Mailchimp subscriber rating (engagement score 1–5) has no direct HubSpot equivalent. Mapped to a custom number field for reporting parity. |
Subscriber.stats.avg_open_rate | Contact.Mailchimp_Avg_Open_Rate__c | custom_field_required | Aggregate open rate per subscriber stored as a custom number field. |
Subscriber.stats.avg_click_rate | Contact.Mailchimp_Avg_Click_Rate__c | custom_field_required | Aggregate click rate per subscriber stored as a custom number field. |
Subscriber.timestamp_opt | Contact.hs_analytics_num_visits | transformed | Mailchimp opt-in timestamp mapped to a custom datetime field (Mailchimp_Opt_In_Date__c) since HubSpot's native timestamp fields track HubSpot-native activity. |
Subscriber.last_changed | Contact.lastmodifieddate | direct | |
Subscriber.subscribe_time | Contact.createdate | direct | |
Subscriber.unique_email_id | Contact.Source_System_ID__c | custom_field_required | Mailchimp's unique email ID stored as Source_System_ID__c for traceability and delta-run deduplication. |
Subscriber.tags | Contact.Mailchimp_Tags__c | custom_field_required | All Mailchimp tags consolidated into a multi-select custom property on HubSpot contact. Tag names preserved exactly; multi-select delimiter is semicolon. |
Subscriber.tags | Contact.Mailchimp_Tag_List__c | custom_field_required | As an alternative to multi-select, tags can be split into separate single-select boolean properties per distinct tag if tag count is under 20. |
Audience Member.audience_name | Contact.Mailchimp_Audience__c | value_mapping | For multi-audience subscribers, each audience name becomes a custom property set to true. Created dynamically based on source audience membership. |
Campaign Activity.campaign_title | Contact.Mailchimp_Last_Campaign__c | custom_field_required | Name of the most recent Mailchimp campaign the subscriber engaged with stored as a custom text field. |
Campaign Activity.opens_total | Contact.Mailchimp_Open_Count__c | custom_field_required | Total opens across all Mailchimp campaigns stored as a custom number field on the contact record. |
Campaign Activity.clicks_total | Contact.Mailchimp_Click_Count__c | custom_field_required | Total clicks across all Mailchimp campaigns stored as a custom number field on the contact record. |
Campaign Activity.last_open | Contact.Mailchimp_Last_Open_Date__c | custom_field_required | Most recent email open date from Mailchimp stored as a custom datetime field for engagement recency reporting. |
Campaign Activity.last_click | Contact.Mailchimp_Last_Click_Date__c | custom_field_required | Most recent email click date from Mailchimp stored as a custom datetime field for engagement recency reporting. |
Campaign Activity.last_sent | Contact.Mailchimp_Last_Sent_Date__c | custom_field_required | Most recent campaign send date for this subscriber stored as a custom datetime field. |
Group.group_name | Contact.Mailchimp_Group_{Category}__c | custom_field_required | Each Mailchimp group category becomes a HubSpot custom property. Property type is single-select with group name as options. Category name embedded in property API name. |
Merge Field (Custom).merge_field_value | Contact.Custom_Property__c | custom_field_required | Custom merge fields from Mailchimp inherit their data type in HubSpot. Text merges map to single-line text, number merges to number properties, dates to date properties. |
Subscriber.email_client | Contact.Mailchimp_Email_Client__c | custom_field_required | Mailchimp stores the subscriber's primary email client (Gmail, Outlook, etc.). Preserved as a custom single-select field for segmentation. |
Subscriber.language | Contact.language | direct |
What to watch for in a Mailchimp to HubSpot migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Multiple Mailchimp audiences create duplicate contacts unless deduplication is pre-planned
Mailchimp does not enforce email uniqueness across audiences — the same address can exist in Audience A and Audience B as separate subscriber records.
How we handle it
When both are imported into HubSpot's single contact database, a deduplication conflict arises. We apply email-based deduplication during migration, merging audience membership flags into a single contact record with multiple Mailchimp_Audience__c properties set. Your team must decide before migration whether to prioritize the most recent subscriber record or a specific audience's data when merge-field values conflict across audiences.
Mailchimp automations and customer journeys do not transfer to HubSpot workflows
Mailchimp automation workflows (welcome series, abandoned-cart sequences, birthday emails, post-purchase follow-ups) are built on Mailchimp's own trigger-and-delay engine.
How we handle it
HubSpot workflows operate on a different enrollment model tied to HubSpot's lifecycle stages, contact properties, and form submissions. There is no programmatic mapping between the two. We export your Mailchimp automation definitions as JSON with step-by-step descriptions so your HubSpot admin can reference them when rebuilding in HubSpot Workflows. This is manual work — budget 1–3 weeks depending on automation complexity.
Mailchimp campaign engagement history does not appear in HubSpot's activity timeline
HubSpot's contact timeline natively shows emails sent from HubSpot, form submissions, page views tracked by the HubSpot tracking code, and meeting activity.
How we handle it
Historical Mailchimp campaign sends, opens, and clicks are not ingested into HubSpot's native activity log — they land as static custom properties on each contact record. Your HubSpot reports will show HubSpot-sent email performance going forward, but Mailchimp historical engagement is queryable as a custom property report only. If executive dashboards require historical open/click rates, they must be built as custom report types in HubSpot referencing the custom fields.
Mailchimp tags require a mapping strategy before migration — count and structure matter
Mailchimp tags are cross-audience and can be applied arbitrarily per subscriber, with no formal taxonomy enforced.
How we handle it
HubSpot contact properties have a defined schema. Tags with fewer than 20 unique values can map cleanly to a HubSpot multi-select property. Tags with hundreds of unique values or nested tag hierarchies (e.g., Product Line > Feature > Use Case) require flattening before mapping. We analyze your Mailchimp tag inventory during the planning phase and propose either a multi-select mapping, a tag-to-list conversion, or a custom property per tag group before migration runs.
HubSpot lists do not automatically update when Mailchimp segments are imported
Mailchimp segments are dynamic filters (opens > 3, clicked any link, tag equals 'enterprise') that update automatically as subscriber data changes.
How we handle it
When imported into HubSpot, static segments become static lists — they reflect subscriber membership at migration time only. Dynamic segments need to be rebuilt as HubSpot Smart Lists using HubSpot's filter criteria, which differ from Mailchimp's syntax. We provide a Smart List rebuild reference mapping each Mailchimp segment condition to the equivalent HubSpot filter and property name.
How the migration runs
Audit Mailchimp audiences, tags, groups, and merge fields
We connect to Mailchimp via API and pull a full inventory of all audiences, subscriber counts, tag names and usage frequency, group categories, custom merge fields with data types, and campaign history.
What this step covers
This inventory drives the mapping plan and surfaces the tag-structure and audience-count variables that determine migration scope and pricing. We share the inventory with your team for confirmation before any data movement begins.
Design HubSpot schema: custom properties, lists, and lifecycle configuration
Based on the Mailchimp audit findings, we design the HubSpot custom properties required to receive all Mailchimp data — per-subscriber engagement fields, audience membership boolean flags, tag multi-select properties, and group properties for interest categories.
What this step covers
We also create HubSpot lists that mirror each Mailchimp audience for list-based segmentation. If Mailchimp contains multiple audiences with overlapping subscribers, we design the deduplication strategy (email-first merge, most-recent-wins, or audience-priority ranking) in collaboration with your team before migration execution begins.
Export and deduplicate Mailchimp subscriber data
We export all subscriber records across all Mailchimp audiences via the Mailchimp API, including merge-field values, tag assignments, group memberships, and engagement stats per subscriber.
What this step covers
Deduplication runs by email address — for subscribers appearing in multiple audiences, we apply the agreed strategy and flag any merge-field conflicts for resolution before write. Tags are aggregated per subscriber for the multi-select property mapping.
Run sample migration with field-level diff
A representative sample — typically 200–500 contacts spanning all audiences, tag groups, and engagement levels — migrates first in an isolated test environment.
What this step covers
We generate a comprehensive field-level diff comparing source Mailchimp field values against the resulting HubSpot contact properties for each sampled record. Your team verifies tag mapping accuracy, audience flag settings, engagement property values, merge-field translation, and deduplication outcomes. Sample validation gates the full migration run; no bulk data moves until the sample passes your approval.
Execute full migration with delta-pickup window
The full subscriber dataset writes to HubSpot via the Contacts API.
What this step covers
A delta-pickup window (typically 24–48 hours) captures any new subscribers, unsubscribes, or tag changes made in Mailchimp during the cutover period. We export Mailchimp automation definitions as JSON for your rebuild reference. An audit log captures every record operation, and one-click rollback is available if reconciliation identifies data integrity issues.
Deliver Smart List rebuild reference for dynamic segments
For each Mailchimp dynamic segment, we produce a written mapping document that translates the original Mailchimp filter conditions into HubSpot Smart List criteria.
What this step covers
Each mapping specifies the equivalent HubSpot property name, operator (equals, contains, greater than, etc.), and value for every condition in the original segment. This step-by-step rebuild guide enables your HubSpot admin to recreate all dynamic segments accurately, ensuring your marketing lists update automatically based on current contact data rather than remaining frozen at migration-time snapshots.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record count, the number of Mailchimp audiences to consolidate, custom merge-field count, and tag structure complexity. A single-audience migration with under 10 merge fields and straightforward tags lands in the lower range. Multiple audiences requiring deduplication, extensive historical campaign engagement properties, or nested tag hierarchies that need multi-select property mapping push toward the upper end. HubSpot lifecycle stage configuration and list-building rules also add planning scope. All FlitStack migrations include a sample run with field-level diff before the full commit. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Mailchimp to HubSpot →Why teams move from Mailchimp to HubSpot
- Mailchimp's audience-centric model caps out when B2B teams need full pipeline visibility — contacts stored in an email platform with no deal or company context create blind spots that a CRM eliminates. Reddit threads on r/marketing and r/CRM consistently flag this as the breaking point for scaling teams.
- Running Mailchimp alongside a separate CRM creates duplicate contact databases, sync gaps, and reporting disconnects. Community posts on r/CRM describe the operational pain of managing two systems and the cost of a second platform when a unified CRM would consolidate spend.
- HubSpot's free CRM tier and Starter plan offer contact management, deal pipelines, and email tracking without a per-seat markup at entry level — teams paying $800+/month for combined Mailchimp plus a CRM find HubSpot's pricing structure more predictable at the same scale.
- Marketing-automation complexity grows beyond Mailchimp's automation builder for teams running multi-step nurture sequences tied to sales signals. HubSpot's workflow engine provides deeper CRM context (lifecycle stage, deal stage, company properties) for enrollment triggers, enabling more sophisticated automation logic that aligns marketing and sales activities.
- B2B companies acquiring contacts through events, forms, and sales touchpoints need a CRM that tracks the full customer journey — from first touch to closed deal — rather than a platform optimized for broadcast email campaigns. HubSpot's lifecycle tracking captures every interaction across channels, creating a complete history that informs sales outreach and marketing personalization.
Questions, answered
Mailchimp to HubSpot migration questions
How long does a Mailchimp to HubSpot migration take?
Most Mailchimp-to-HubSpot migrations complete in 24–72 hours of clock time for under 25,000 subscribers across one or two audiences with straightforward tag structures and merge fields. Larger migrations with 250,000+ subscribers, multiple audiences requiring deduplication, or extensive nested tag hierarchies and custom merge-field counts extend to 3–7 calendar days. The initial planning and HubSpot schema setup phase (Steps 1–2) runs concurrently with preparation activities and typically takes 1–3 business days before migration execution begins, so total project duration includes this planning window.
Will my Mailchimp automations and customer journeys migrate to HubSpot?
No. Mailchimp automation workflows — welcome series, abandoned-cart sequences, post-purchase emails, birthday automations — do not migrate to HubSpot. They run on fundamentally different engines with different trigger models. FlitStack AI exports your Mailchimp automation definitions as a JSON reference document so your HubSpot admin can rebuild them step by step in HubSpot Workflows. Plan 1–3 weeks for rebuild depending on automation complexity.
What happens to my Mailchimp subscriber tags and groups in HubSpot?
Mailchimp tags migrate as a custom multi-select property (Mailchimp_Tags__c) on each HubSpot contact, with all tag names preserved. Group memberships map to individual custom properties named by group category. If you have fewer than 20 distinct tags, we can alternatively create one boolean property per tag. Dynamic segments from Mailchimp require rebuild as HubSpot Smart Lists — we provide the written filter-to-criteria mapping for each segment after migration.
Can I migrate Mailchimp campaign engagement history (opens, clicks, sends) to HubSpot?
Partially. Aggregate engagement stats per subscriber — total opens, total clicks, last open date, last click date, and last campaign sent — migrate as custom properties on each HubSpot contact (Mailchimp_Open_Count__c, Mailchimp_Click_Count__c, Mailchimp_Last_Open_Date__c, etc.). These are static reference values. They do not appear in HubSpot's native activity timeline, which tracks HubSpot-sent emails. We also create a Mailchimp_Campaign_Report__c custom object for aggregate campaign-level stats.
What happens if the same email address appears in multiple Mailchimp audiences?
Mailchimp does not enforce email uniqueness across audiences, so the same address can exist in multiple audiences as separate subscriber records. During migration, we deduplicate by email — the contacts merge into a single HubSpot contact record. We set a custom property (Mailchimp_Audience__c) for each source audience the email belonged to. If merge-field values conflict between audience records (e.g., different last_name values), we apply your chosen priority rule (most recent, audience-specific, or manual review) before writing.
Does the migration affect my Mailchimp account during the cutover?
No. FlitStack AI connects to Mailchimp via read-only API access during migration — your team continues working in Mailchimp throughout. A delta-pickup window (24–48 hours) after the full migration captures any new subscribers, unsubscribes, tag changes, or contact updates made in Mailchimp during the cutover period, so your HubSpot database reflects Mailchimp's final state at go-live. After go-live, Mailchimp is put in read-only or decommissioned per your decision.
What Mailchimp data does FlitStack AI NOT migrate?
We do not migrate Mailchimp automation workflows, email templates, campaign send history (aggregate reports are preserved; individual send events are not), integrations or third-party connections, billing information, or domain authentication records. Email templates must be recreated in HubSpot's drag-and-drop editor. Automation definitions are exported as JSON for manual rebuild. Integration endpoints must be reconfigured in HubSpot's app marketplace after migration.
How do I handle unsubscribes and cleaned (bounced) contacts from Mailchimp in HubSpot?
Mailchimp subscriber statuses map to HubSpot contact email subscription statuses: 'Subscribed' becomes 'subscribed', 'Unsubscribed' becomes 'unsubscribed', and 'Cleaned' (hard bounce) becomes 'bounced' in HubSpot. For cleaned contacts, we also set a custom boolean field (Mailchimp_Cleaned__c) to distinguish hard bounces from manual unsubscribes — useful if you want to suppress those contacts from future HubSpot email sends without formally unsubscribing them from a marketing perspective.
Related migrations
HubSpot implementation
Set up HubSpot and migrate into it as one engagement.
See the service → Zoho CRM to HubSpotMapping · history · rollbackZendesk Sell to HubSpotMapping · history · rollbackClose to HubSpotMapping · history · rollbackPipedrive to HubSpotMapping · history · rollbackSalesforce to HubSpotMapping · history · rollbackEspoCRM to HubSpotMapping · history · rollback Mailchimp to SalesforceMapping · history · rollbackMailchimp to Zoho CRMMapping · history · rollbackMailchimp to Dynamics 365Mapping · history · rollbackSources: official documentation
- Format import files — HubSpot Knowledge Base
- Create and edit custom objects — HubSpot Knowledge Base
- Import objects programmatically — HubSpot Knowledge Base
- Understand property field types in HubSpot
- Merge Fields Documentation — Mailchimp Developer
- Format Guidelines for Your Import File — Mailchimp
- Manage Audience and Signup Form Fields — Mailchimp
Get a quote
Moving from Mailchimp to HubSpot?
Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.
Get a quote