Migrate from AllClients to Mailchimp

AllClients Contact records map directly to Mailchimp Audience Members. Email address is the primary key and dedupe field. We run the contact export from AllClients' Data Migration menu as the foundation and merge in Notes and Tags during the mapping phase. AllClients Select tier at 1,500 contacts maps to Mailchimp's free tier at 500 contacts with a gap that we flag before migration; customers typically upgrade to Mailchimp Essentials or Standard to match their full contact volume.

AllClients exports Notes as a separate Notes.csv file that is not joined to the main Contact CSV. We run the join explicitly using the contact's email address as the key. If a contact's email changed between the two exports, we flag the orphaned notes for manual review. Member notes in Mailchimp are per-member text fields that attach to the member profile visible in the member detail view. We append multiple notes as separate timestamped entries if the contact has more than one.

AllClients custom fields are account-level definitions that we discover during scoping. We create corresponding Merge Fields in the Mailchimp Audience before any contact import, mapping AllClients field types to Mailchimp merge field types: text to text, number to number, date to date, dropdown to radio or dropdown, multi-select to checkboxes. Address fields in AllClients require splitting into Mailchimp's separate ADDRESS merge field format with street, city, state, zip, and country components.

Tags are the most direct migration between the two platforms. AllClients exports tags as comma-separated values within the contact record. We extract all unique tag values, create corresponding Tags in the Mailchimp Audience during scoping, then apply tag membership during the member import. Tags are additive and do not overwrite existing member data, making them safe for re-runs if the initial import has issues.

AllClients Groups are logical collections of contacts filtered by shared properties (tag, field value, group membership). AllClients does not export group definitions independently; contacts are filtered by group at export time. We reconstruct Groups as Mailchimp Segments by capturing the filter conditions and translating them to Mailchimp segment rules using merge field conditions and tag combinations. We deliver a written Segment Rebuild Specification listing each original Group, its filter logic, and the equivalent Mailchimp segment rule for the customer to create post-migration.

AllClients stores email templates as HTML blobs under the Email Marketing section. We export each template as an HTML file and import it into Mailchimp's template library. We preserve inline images as external URLs and replace them with Mailchimp-hosted images where possible. Template layout and styling migrate but AllClients-specific merge tags are replaced with Mailchimp merge tag syntax during import. Basic templates typically map cleanly; templates with heavy AllClients-specific branding require visual review and manual adjustment.

AllClients Campaign records (campaign names, linked segments, send dates, send counts) do not have a structural equivalent in Mailchimp as historical campaign objects. We migrate campaign names and the contact segments they were sent to as a written campaign history document. Email performance data (open rates, click rates) is AllClients metadata that does not export cleanly; we recommend capturing screenshots of campaign reports before account cancellation. Mailchimp campaign history is retained in the platform going forward.

AllClients User records (Name, Email, role) do not map to any Mailchimp object because Mailchimp is not a multi-user CRM in the traditional sense. Owner assignment on AllClients contacts does not transfer. We flag this gap and recommend that the customer assigns a primary Mailchimp admin account or, if multiple senders are needed, uses Mailchimp's Teams and Permissions feature to provision sub-accounts post-migration.