Migrate from crmConnect to Mailchimp

Source export scoping and tier verification

We confirm the crmConnect subscription tier (Standard or Professional) because Standard caps contact storage and limits pipeline access. We identify all data objects in scope for migration: Contacts, Tags, Segments, Email Campaigns, Custom Properties, and any available Pipelines, Opportunities, Memberships, and Calendars. We verify that the UI-based CSV export is the only available export path and estimate the number of export files required based on total contact volume. We request access to crmConnect as an admin user with full contact, pipeline, and automation visibility.

Suppression list extraction and consent audit

Before exporting any contacts, we extract the full suppression list from crmConnect: all unsubscribed, bounced, and do-not-contact records. These are imported into Mailchimp as a suppression list before any active subscriber import so they are never emailed. We audit the opt-in source for each contact to identify those with unclear consent history (imported from a third-party list, single-check consent form, or historical record without timestamp) and flag them for re-confirmation rather than active import. This step prevents deliverability damage from mailing to unconsented contacts post-migration.

Multi-file export sequencing and deduplication

We sequence the crmConnect CSV exports across the estimated file count, maintaining consistent field headers across all files. After export completes, we run email-address-based deduplication across all files, merging any duplicate contact records and retaining the most recent field values for any conflicting properties. We cross-check the deduplicated total against crmConnect's reported contact count to confirm nothing was missed. Any discrepancies trigger a re-export of the affected batch before moving forward.

Mailchimp audience schema setup and merge field creation

We create the target Mailchimp Audience and configure the merge field schema based on the crmConnect contact properties discovered during export. Standard fields (First Name, Last Name, Email, Phone, Address) map to Mailchimp's built-in merge fields. Custom crmConnect properties (custom fields, pipeline stage tags, membership status, enrollment dates) map to Mailchimp custom merge fields of the appropriate type. Tags from crmConnect are pre-created as Mailchimp Tags so they are available for assignment during import. We configure any required GDPR fields (HasOptedOutOfEmail, GDPR_Consent) during this step.

Subscriber import with tag assignment and suppression hygiene

We import contacts into the Mailchimp Audience in batches using Mailchimp's bulk import endpoint, with rate-limit handling and batch chunking to avoid API throttling. Each batch assigns the corresponding crmConnect Tags to each Subscriber during import. Suppressed contacts are excluded from the active import batch and remain in the suppression list. After each batch import, we reconcile the row count against the source export and check Mailchimp's import report for any email addresses rejected due to formatting, duplicates, or permission flags.

Template reconstruction and campaign content migration

We export crmConnect email campaign templates as HTML content and extract subject lines, from-name configurations, and image asset URLs. Images hosted in crmConnect are re-uploaded to Mailchimp's asset library or kept at their original hosted URLs. Template body content is populated into Mailchimp's template format (coded or drag-and-drop depending on complexity). Plain-text versions are auto-generated from HTML. We deliver the reconstructed templates as drafts in the customer's Mailchimp account ready for review and sending.

Automation inventory delivery and cutover handoff

We deliver the written automation inventory documenting every crmConnect Automation with its trigger, conditions, delays, and actions and a recommended Mailchimp Customer Journey equivalent. We also deliver the pipeline stage tag map, the merge field schema reference, and the suppression list confirmation. After final delta import (any contacts modified during the migration window), we enable Mailchimp as the active sending platform and recommend the customer send a re-engagement or confirmation email to the audience. We do not rebuild automations in Mailchimp as part of the migration scope.