Migrate from FIVE CRM to Mailchimp

FIVE CRM Contact records map to Mailchimp Audience members. The email address field serves as the primary key and dedupe mechanism. We run email validation against Mailchimp's bulk verification requirements before import to prevent bounces that damage sender reputation. First name, last name, phone number, and owner-assigned user map to Mailchimp FNAME, LNAME, PHONE merge fields and the contact's assigned owner is documented as a tag for post-migration reassignment since Mailchimp has no user assignment model.

FIVE CRM Company records have no structural equivalent in Mailchimp. Mailchimp Audience members are flat contact records without a parent Account or Company object. We flag every FIVE CRM Company with associated Contacts and document which Contacts belong to which Company in a supplementary CSV so the customer's admin can recreate Company context using Mailchimp Tags or Groups. Companies with no associated Contacts are documented in the no-destination inventory.

FIVE CRM Lead records (separate from Contacts) merge into Mailchimp Audience members. The original Lead_Source property migrates as a Mailchimp Tag (e.g., tag: lead_source_web, tag: lead_source_referral) so the admin can segment by origin without a dedicated Lead object. Unqualified Leads with no email address are documented in the no-destination inventory since Mailchimp requires a valid email address for Audience membership.

FIVE CRM Campaigns track email marketing sequences and membership. Mailchimp has a native Campaign object that manages the sending of emails to Audience segments. We migrate campaign membership as Mailchimp Audience segments (using tag-based or group-based segment definitions) and preserve the FIVE CRM campaign name and status. Granular per-contact engagement history (opens, clicks, replies) does not transfer because FIVE CRM does not expose a bulk export endpoint for event-level logs and Mailchimp stores campaign-level engagement differently.

FIVE CRM custom fields require explicit mapping to Mailchimp merge fields. Mailchimp supports text, number, date, phone, address, and dropdown merge field types. We enumerate every active custom field during scoping, confirm the data type, and map to the nearest Mailchimp equivalent. Boolean fields become dropdown merge fields with Yes/No options. Multi-select picklist values in FIVE CRM may require multiple Tags rather than a single merge field if the value count exceeds Mailchimp's dropdown limit. Phone number merge fields require formatting to E.164 for international compatibility.

FIVE CRM Tags map directly to Mailchimp Tags. Tags serve as the primary segmentation mechanism in Mailchimp and replace FIVE CRM's tag-based filtering. Multi-select tag fields on FIVE CRM records split into individual Tags during import. Tags with more than 50 characters are truncated to Mailchimp's tag length limit and documented in the field mapping summary.

FIVE CRM Pipelines and their custom stage names do not have an equivalent in Mailchimp. Mailchimp does not track deal progress, opportunity stages, or sales pipeline data. We document the complete pipeline structure including stage names, stage order, and which Deals are associated with each stage in the written no-destination inventory. The customer's admin can recreate pipeline context in a spreadsheet or a dedicated CRM if deal tracking is required post-migration.

FIVE CRM Task records (with due dates, assignees, and completion status) have no structural equivalent in Mailchimp. Mailchimp has no task management or activity timeline beyond per-campaign email engagement reports. We document all open Tasks in the written no-destination inventory with assignee, due date, and description so the admin can recreate task context in a project management tool or a dedicated CRM if task tracking is required.

File attachments associated with FIVE CRM Contacts or Companies do not have a storage equivalent in Mailchimp. Mailchimp does not support file attachments on contact records or a document management layer. We document attachment file names, associated records, and storage locations in the no-destination inventory. The customer's admin can re-upload files to a cloud storage platform and link to them via a URL field in Mailchimp if needed.