Migrate from Access CRM to Mailchimp

Access CRM Contacts map to Mailchimp Audience members. Each contact's email address is the primary key and dedupe handle. We preserve first name, last name, phone, address, and owner assignment. Email opt-in status from Access CRM maps to Mailchimp's subscribed/unsubscribed/global unsubscribe status, with the original Access CRM status preserved in a custom contact field for compliance audit.

Access CRM Companies have no direct Mailchimp equivalent. We offer two strategies: (a) add the company name as an audience tag (e.g., tag: Company=Acme Corp) for segmentation, or (b) append company name, domain, industry, and address as a contact note. The customer selects the strategy during scoping. Parent/child company hierarchies flatten to a single tag value unless the customer requests a hierarchical note structure.

Access CRM Opportunities carry Worst/Likely/Best deal values, stage probabilities, and close dates that have no Mailchimp counterpart. We do not migrate Opportunities as records. Instead, we export a structured Opportunities inventory CSV with deal name, amount range, stage, and owner, and we deliver it alongside the migration package so the customer's admin can reference historical pipeline data in a spreadsheet or a supplemental CRM if needed.

Access CRM Cases with lifecycle status, priority, and routing assignments have no Mailchimp equivalent. Cases do not migrate. We export a Cases inventory CSV with subject, status, priority, owner, and related contact email so the customer can reference case history for support handoff or import into a dedicated helpdesk platform.

Access CRM Activities (calls, emails, meetings, notes) associated with Contacts map to Mailchimp campaign engagement history if the contact's email appears in a historical Mailchimp campaign. We export the full activity history as a structured JSON timeline per contact, delivered as a separate export package. Mailchimp's own open/click engagement data is the primary record post-migration; historical Access CRM activities are reference-only unless re-imported to a third-party timeline tool.

Access CRM tenant-defined pipeline stages (e.g., Proposal, Negotiation, WON) do not map to Mailchimp objects. We capture the full stage list during scoping and offer to create Mailchimp segments that mirror the stage vocabulary as tag filters (e.g., tag: PipelineStage=Proposal). This is a segmentation strategy, not a pipeline migration, and requires the customer to define the segment logic post-migration.

Access CRM web-enquiry form fields that capture leads are treated as a custom object set. We export the form field schema (field name, type, required flag) and any associated contact records. The customer rebuilds the signup form in Mailchimp's form builder and maps the form fields to the corresponding Mailchimp contact fields. Form submissions are not replayed; only the field schema and historical captured contacts migrate.

Access CRM tenant-specific custom fields migrate to Mailchimp audience merge fields. We extract the full field manifest during scoping, map field types (text, number, date, dropdown) to Mailchimp merge field types (TEXT, NUMBER, DATE, ADDRESS, PHONE), and create the merge fields in the Mailchimp audience before contact import. Fields without a Mailchimp equivalent (e.g., multi-select picklists with more than 30 values) are exported as a separate custom field export package.