Migrate from Mailchimp to Freshsales

Mailchimp Audiences are separate contact containers each with their own settings, opt-in workflow, and GDPR consent fields. We export all Audiences and merge them into Freshsales Contacts. Each contact's subscription status (subscribed, unsubscribed, non-subscribed, cleaned) maps to Freshsales Contact lifecycle status fields, and GDPR consent flags (if configured) map to custom contact properties. If a contact appears in multiple Audiences with conflicting statuses, we apply the most permissive status (subscribed takes precedence over unsubscribed only if the contact re-subscribed after the unsubscribe event). Audience-level opt-in defaults are noted in the migration summary for the customer's admin to configure in Freshsales.

Mailchimp Contact records map directly to Freshsales Contacts. Standard fields (email, first name, last name, phone, address) map to Freshsales standard contact fields. Merge field values map to Freshsales custom contact properties, creating the field in Freshsales if it does not exist. The contact's unique Mailchimp contact ID is preserved in a custom property for audit and cross-reference. Contact status (subscribed, unsubscribed, non-subscribed, cleaned) maps to Freshsales lifecycle stage or a custom subscription_status field so the customer can filter on deliverability eligibility after migration.

Mailchimp Tags are freeform labels attached to individual contacts. We export all tag names and their contact associations and import them into Freshsales Tags, which attach to Contacts the same way. Tags used for segmentation classification migrate as structured tags; if the customer used a tagging convention for campaign attribution (e.g., campaign_name), we recommend mapping those to Freshsales custom contact fields for reporting rather than leaving them as freeform tags.

Mailchimp Segments are dynamic filters built on contact properties, merge field values, and engagement behavior. Freshsales Smart Lists provide equivalent dynamic filtering on contact and deal properties. We export the segment rules as structured data (field name, operator, value) and provide a mapping document that tells the customer's admin which Freshsales Smart List fields and operators replicate each Mailchimp segment rule. Segments requiring behavioral triggers (e.g., opened any campaign in last 30 days) may require Freshsales Workflows to replicate the enrollment logic.

Mailchimp Groups are category-value pairs where contacts can belong to multiple values within a Category (e.g., Interests: Sports, Music, Technology). We export both the Category and the Group. Each Category becomes a Freshsales custom dropdown or multi-select picklist field on Contact, with the Group values as picklist options. The contact's group membership migrates as the selected picklist value. Multi-value group memberships (contacts in multiple groups within one Category) map to Freshsales multi-select picklist fields.

Mailchimp campaign metadata (campaign name, subject line, send date, recipient count, open rate, click rate, bounce rate, unsubscribes) migrates as records in a Freshsales custom Campaign History object or as Deal records with campaign attribution fields. We export campaign content as HTML blobs attached to the record. Freshsales does not have a native campaign analytics dashboard equivalent to Mailchimp Reports, so the customer reviews campaign history in the custom object list view or exports to a spreadsheet. This is a known limitation that the migration handoff document acknowledges.

Mailchimp email engagement events (opens, clicks, bounces, unsubscribes) per contact migrate to Freshsales activity records on the Contact timeline. Each event type maps to a corresponding Freshsales activity type: opens and clicks become Note records with the engagement detail; bounces become Task records with a bounced flag; unsubscribes become Task records with the unsubscribe reason captured. We export the last 90 days of activity by default. Full campaign history may require pagination across multiple Mailchimp API pages and is available at an extended scope if the customer requests it.

Mailchimp Automations store workflow logic (triggers, delays, conditions, actions) in a proprietary format with no export mechanism. We do not migrate automation workflows as code. We run a full automation audit and deliver a written inventory document listing every active automation with its trigger type (welcome, abandoned cart, birthday, date-based, API-triggered), step count, enrollment size, and action sequence. The customer's admin rebuilds each workflow in Freshsales Workflows (Growth tier and above) or in a dedicated automation tool. The automation inventory document is the primary deliverable for this object.

Mailchimp email templates export as raw HTML files. Freshsales has a built-in email template system, but it does not render Mailchimp-specific content block syntax. We export the HTML but note that visually complex templates with nested Mailchimp blocks, dynamic content sections, or Mailchimp-specific merge tag syntax will not render correctly without manual rebuild. Simple templates with standard HTML structure (headers, body text, images, footers) are more likely to transfer without adjustment. The customer should plan for a template rebuild effort as part of post-migration setup.