Migrate from Simply CRM to Mailchimp

Mailchimp has no company object — company data flattens per contact

Simply CRM stores companies as a first-class object with industry, employee count, annual revenue, and parent-child hierarchies. Mailchimp has no company object — company data must be written as merge fields on individual contacts. If a contact in Simply CRM links to multiple companies, only the primary company maps cleanly to the COMPANY merge field; secondary affiliations become tags (format: company:AcmeCorp) so Mailchimp segments can still filter by affiliation. Hierarchical company structures collapse into a single company name. Revenue and industry fields require new custom merge fields — Mailchimp has no standard MERGE field for these by default.

Mailchimp's contact-based pricing means migrated contacts immediately affect your plan tier

Simply CRM charges per seat or flat-rate regardless of contact count. Mailchimp charges per total audience size — adding contacts from Simply CRM will increase your Mailchimp subscriber count and may push you into a higher pricing tier. We surface the contact volume before migration and show which Mailchimp plan tier the total audience will land in so there are no billing surprises. Audiences with over 500 contacts require a paid Mailchimp plan; we flag this before migration commits.

Activity history (calls, meetings, notes) does not migrate — only email engagement is tracked post-migration

Simply CRM logs calls, meetings, internal emails, and notes with timestamps and owner attribution. Mailchimp tracks only email engagement (opens, clicks, unsubscribes, bounces) per member. Historical activity context from Simply CRM cannot be written to Mailchimp — there is no activity log model in Mailchimp's API. If your team relies on Simply CRM's activity timeline for follow-up context, that history is lost in Mailchimp. We can extract the most recent activity date as a merge field for segmentation purposes, but the full timeline has no destination.

Unsubscribe and GDPR consent flags must be honored precisely or deliverability suffers

Simply CRM contacts marked 'Do Not Email' or with revoked GDPR consent must map to Mailchimp 'Unsubscribed' status — not just a tag. Using a tag instead of the native status field means Mailchimp will still attempt to email those contacts if segments are not carefully scoped, causing spam complaints that damage sender reputation. We validate unsubscribe and consent mappings against Mailchimp's list washing rules before writing any member record. If Simply CRM stores consent as a date field rather than a boolean, we map it to Mailchimp's marketing permission merge fields.

Mailchimp's 50 merge field limit may require flattening or prioritization

Mailchimp allows a maximum of 50 merge fields per audience. Simply CRM setups with many custom fields on contacts (30+) may exceed this limit. We audit the custom field count during scoping and group lower-priority fields into comma-separated text merge fields or consolidate related fields into tags. We present a prioritization list before migration so you decide which custom fields get dedicated merge fields versus tag-based storage. This is handled in the pre-migration plan, not discovered during the run.