Migrate from Amwork to Mailchimp

Discovery and data audit

We audit the source Amwork workspace: contact count, company count, lead volume, custom field definitions (API names and types), lifecycle stage values, owner assignments, and any prior import history. We compare the exported contact count against Amwork's reported contact count to detect silent import failures from prior migrations. We also identify any Amwork contacts with missing email addresses, which cannot migrate to Mailchimp as subscribers. The discovery output is a written Data Audit Report with record counts, field inventory, and a data-quality issue list that must be resolved before migration.

Mailchimp audience setup and merge field creation

We create the Mailchimp Audience with the correct field structure before any data imports. This includes creating custom merge fields that map to Amwork custom field definitions, configuring the double opt-in setting based on the customer's preference, and setting up the initial Tags structure for owner-based segmentation. We also configure the default subscriber status (subscribed by default unless opt-in verification shows otherwise). The audience is created in a staging state until domain authentication is confirmed.

Domain authentication configuration

We coordinate with the customer's DNS provider to add DKIM and SPF TXT records to the sending domain before the Mailchimp audience is activated. This step requires DNS access and typically takes 24-48 hours for propagation. Without confirmed authentication, the Mailchimp account is placed in a restricted sending state. We verify DKIM and SPF records post-propagation using an external DNS lookup tool before enabling campaign sending.

Contact hygiene and opt-in verification

We segment Amwork contacts into four groups: verified opt-in (migrate immediately), unverified but likely consented (require re-permissioning campaign), purchased or imported list contacts with no engagement record (recommend exclusion), and contacts with invalid or missing email addresses (export as non-migratable). We provide a re-permissioning email template and a separate Mailchimp audience for the quarantine list. Migration proceeds with verified contacts first.

Production migration and reconciliation

We import Amwork Contacts as Mailchimp Subscribers in batches using Mailchimp's bulk import endpoint, applying merge field mappings, owner tags, lifecycle stage values, and company data per record. Each batch is reconciled against the source export row count. After import, we run a random sample validation (10% of records or minimum 50) comparing email, name, and merge field values between Amwork and the Mailchimp subscriber profile. The customer approves the sample before we mark the migration complete.

Deal, Project, and Automation handoff documentation

We deliver three written documents: a Deal Inventory CSV (all Amwork Deals with name, value, stage, close date, owner, and linked contact email), a Project-Task Inventory CSV (project hierarchy with task names, assignees, and due dates), and an Automation Inventory (all active Amwork workflow rules with trigger, conditions, and actions mapped to Mailchimp Customer Journey equivalents). These documents are the customer's guide for recreating deal pipeline tracking and automation sequences in Mailchimp or a separate CRM tool.