Migrate from Pure Chart to Mailchimp

Pure Chart contacts map directly to Mailchimp subscribers. Every contact property becomes either a native Mailchimp field or a merge field. The email address is the primary key — Mailchimp deduplicates by email on import, keeping the most recently updated record.

Mailchimp has no standalone company object. Pure Chart company data (name, industry, website, employee count) maps to merge fields on the subscriber record. Multiple contacts from the same company each carry the company data as individual merge field values. If you need to query company-level aggregates, you can use external reporting tools that join on the company name stored in the merge field.

Every Pure Chart custom contact property becomes a Mailchimp merge field. We match Pure Chart property types to Mailchimp field types: text to text, number to number, date to date, phone to phone. Array or nested JSON values are flattened to pipe-delimited text with a warning note in the migration plan.

Pure Chart tags map 1:1 to Mailchimp tags. Tags are applied directly during the contact import. Mailchimp tags are additive — if a contact has five tags in Pure Chart, all five are applied in Mailchimp. No tag limit applies on Mailchimp's side.

Pure Chart segments (saved filter combinations) are translated into Mailchimp segment conditions. Each segment's filter logic — property conditions combined with tag logic — is recreated as a Mailchimp Saved Segment. You review and approve the segment mapping before the migration run.

Pure Chart campaign names, subjects, and send dates are mapped to Mailchimp campaign records for reference. Aggregate open and click rates from Pure Chart are stored as merge fields (LAST_OPEN_DATE, HISTORICAL_CLICK_RATE) so the data is visible on each subscriber record even though Mailchimp's own reporting starts post-migration.

Pure Chart engagement scores (open count, click count, last activity date) are stored as custom merge fields on each subscriber. Mailchimp tracks opens and clicks natively from migration day forward; pre-migration engagement history is preserved in merge fields so your team can reference it in filters or conditional content.

Pure Chart workflow definitions (triggers, conditions, time delays, actions) have no Mailchimp equivalent. We export the full workflow definition as a JSON reference file before migration. Your Mailchimp admin rebuilds triggers using Customer Journeys or a third-party automation tool (Zapier, Make).

Pure Chart email templates migrate as Mailchimp templates. HTML-based templates copy directly; drag-and-drop templates are recreated as Mailchimp Builder templates using the layout and content as a guide. Images are re-hosted to Mailchimp's content delivery network. You will receive a template mapping document listing each original Pure Chart template alongside its Mailchimp counterpart so your design team can verify layout fidelity and update links if needed.

Pure Chart unsubscribes and bounces are imported into Mailchimp as suppressed (unsubscribed) contacts before any campaign sends. This is mandatory — failing to suppress before the first send damages sender reputation and deliverability. We run this import as Step 1 of the migration.