Migrate from EspoCRM to Mailchimp

EspoCRM Contact records map to Mailchimp Audience members. We extract firstName, lastName, email, phone, and address fields and map them to Mailchimp's standard address and phone merge fields. Custom fields on Contact created via Entity Manager map to Mailchimp merge fields (maximum 40 per audience); if the source has more than 40 custom fields, we prioritize by usage frequency and flag the remainder for manual audience enrichment in Mailchimp. Multi-email fields on EspoCRM Contact are mapped to the primary EMAIL merge field; additional email addresses are stored as custom merge fields or tags.

EspoCRM Lead records map to Mailchimp Audience members with their original lead status preserved as a tag or custom merge field. Leads that have been converted to Contacts (tracked via the converted flag and linked Contact/Account IDs in EspoCRM) are deduplicated against existing Contacts before import to avoid duplicate audience members. We import converted Leads as contacts and unconverted Leads as subscribers at their current EspoCRM email opt-in status.

EspoCRM Campaign records with associated target lists (linked Leads and Contacts) are migrated as Mailchimp segments or as tag-applied contacts within a single primary audience. If the customer uses multiple EspoCRM Campaigns as distinct targeting lists, each can become a separate Mailchimp segment or the customer can consolidate into one audience with tags per campaign source. We apply tags matching the EspoCRM Campaign name to all members of that target list.

EspoCRM Account records (companies) do not have a direct Mailchimp equivalent because Mailchimp is a contact-centric platform, not a company-centric one. We extract the company name from each Contact's Account link and map it to a COMPANY merge field on the Mailchimp audience member. If the customer uses Accounts as a segmentation dimension, we also apply a company-based tag to each audience member.

EspoCRM Opportunities have no Mailchimp equivalent. Mailchimp does not support deal pipeline, stage, probability, or revenue tracking. We flag Opportunities during discovery, export them as a CSV for the customer's reference, and advise rebuilding the pipeline view in a dedicated CRM or spreadsheet. This is a manual reconstruction step outside the automated migration scope.

EspoCRM Cases (support tickets) do not migrate to Mailchimp. Mailchimp does not have a ticket or case management object. We export Case records as a CSV with status, priority, and resolution fields, and advise the customer to evaluate dedicated helpdesk platforms (Zendesk, HubSpot Service Hub, Freshdesk) if case management is needed post-migration.

Custom entity types created via EspoCRM's Entity Manager are evaluated for Mailchimp compatibility. If a custom entity links to Contacts (e.g., a Subscription, Property, or Vehicle linked via link-multiple), we extract the related entity name or ID as a tag or custom merge field on the parent Contact audience member. Custom entities that are standalone with no Contact relationship are exported as CSV reference data and not imported into Mailchimp.

EspoCRM Activity history (Meeting, Call, Task, Email records linked to Contacts) does not migrate. Mailchimp tracks its own send engagement data (opens, clicks, bounces, unsubscribes) and does not accept external activity history as a native object. We export Activities as a CSV timeline for the customer's records. The Mailchimp engagement timeline begins on the date of the first campaign send post-migration.

EspoCRM Document records and their associated file attachments (stored on the filesystem on self-hosted instances under data/files/) do not migrate to Mailchimp. Mailchimp does not have a document management object. We identify Document records linked to Contacts during discovery, extract referenced files from the EspoCRM filesystem archive if self-hosted, and deliver them as a zip archive for manual attachment to relevant audience members or for use in future campaigns.