Migrate from Freshsales to Mailchimp

Freshsales Contacts map directly to Mailchimp Audience members using email address as the dedupe key. Standard contact fields (first_name, last_name, email, phone, address fields) map to Mailchimp merge fields. We create any missing merge fields in the Mailchimp audience schema before importing. Contacts without an email address are flagged in a reconciliation report because Mailchimp requires an email for member records.

Freshsales Leads map to Mailchimp Audience members using the same email dedupe logic as Contacts. The Lead's lifecycle stage migrates as a Mailchimp tag (e.g., 'Lead: New', 'Lead: Contacted') so that lead quality can be used for segmentation in Mailchimp automations. If the customer used the Freshsales Classic-to-Suite migration where Leads auto-convert to Contacts, we detect this during scoping and skip duplicate record creation.

Freshsales Accounts have no Mailchimp equivalent because Mailchimp does not have a company object. Account name and industry can be stored as merge fields on the contact record, or we create a tag pattern (e.g., 'Account: Acme Corp') to preserve company grouping. We discuss the preferred strategy with the customer during scoping because the choice affects how audience segmentation works in Mailchimp.

Freshsales contact tags map directly to Mailchimp tags on the contact record. Tags are preserved as-is because Mailchimp tags are a first-class object. If the same tag appears on multiple contacts, it becomes a Mailchimp segment filter criterion post-migration. We capture the full tag taxonomy during scoping so that the customer can plan their Mailchimp segment strategy.

Freshsales custom fields on Contacts map to Mailchimp merge fields. We translate Freshsales field types (text, number, date, dropdown, checkbox, multi-select) to Mailchimp merge field types (text, number, date, radio, checkbox, multi-select where supported). Mailchimp has a merge field limit per audience; we verify the count during scoping and flag if the destination audience approaches the limit.

Freshsales lifecycle stages (New, Active, Stale, Cold, etc.) are a contact property with no direct Mailchimp equivalent. We migrate lifecycle stage as a Mailchimp tag (e.g., 'Lifecycle: New', 'Lifecycle: Active') so that the customer can rebuild Freshsales-style lead quality segmentation in Mailchimp using tag-based filters. The original Freshsales lifecycle stage value is preserved in the tag label.

Freshsales Deals have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not support pipeline, opportunity, or deal records. We document every Deal in a written inventory (record count, stage distribution, owner, amount, probability) for the customer's admin to handle outside the migration scope. Deals are not imported into Mailchimp.

Freshsales Tasks, Events, and Calls have no Mailchimp equivalent as native activity records. Mailchimp tracks campaign engagement (opens, clicks, unsubscribes) per contact, but this is email-specific and does not reflect Freshsales sales activities. We can write Freshsales engagement timestamps into Mailchimp contact notes or a custom merge field as a historical reference, but this is a best-effort preservation and does not replicate the activity timeline. Activity history is documented in the scope inventory.

Freshsales Products with SKUs and pricing have no Mailchimp equivalent. Mailchimp does not have a product catalog. If the customer uses Freshsales products in CPQ workflows, those records are documented in the scope inventory for the customer to handle separately. Mailchimp product recommendations are a campaign-send feature, not a catalog feature, and are rebuilt in Mailchimp's campaign builder post-migration.

Freshsales Custom Objects (created via Freshworks developer platform) have no Mailchimp equivalent. Custom object records cannot migrate to Mailchimp. We document the custom object schema, record count, and any lookup relationships to standard objects (Contact, Account, Deal) in the scope inventory. If the customer needs this data, it requires a separate storage solution or a custom Mailchimp integration built post-migration.