Migrate from ASPEC to Mailchimp

ASPEC Contact records map directly to Mailchimp Audience Members. We map first name, last name, email address, phone number, and physical address to the corresponding Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Email address serves as the dedupe key during import. Any Contact without a valid email address is held in a reconciliation queue for the customer to correct before import; Mailchimp requires a valid email for every Audience Member.

ASPEC Company records do not have a direct Mailchimp equivalent because Mailchimp has no Company or Account object. We encode company data into Mailchimp merge fields: the company name maps to a custom COMPANY merge field, and any company size or industry data maps to custom merge fields on the Audience. This means the 1:1 association between Contact and Company in ASPEC is preserved only as metadata on the individual Audience Member, not as a separate related record.

ASPEC tags on Contacts and Companies map directly to Mailchimp Tags on the corresponding Audience Members. We preserve the tag taxonomy during import, writing tags as comma-separated values in the Mailchimp Tags field. Tags used for segmentation in ASPEC (for example, industry verticals or account tiers) become Mailchimp Tags that can be used in Audience segmentation rules for campaign targeting.

ASPEC Opportunities (deal records with pipeline stages, values, and close dates) have no Mailchimp equivalent. Mailchimp does not have a deal, opportunity, or pipeline object. We do not migrate Opportunity records. If the customer requires pipeline tracking, they must implement it in a separate CRM or spreadsheet outside of Mailchimp. We flag every Opportunity during scoping so the customer can export it manually if needed for reporting.

ASPEC Activity records (calls, emails, meetings, tasks) linked to Contacts do not migrate to Mailchimp. Mailchimp tracks engagement at the campaign level (opens, clicks, unsubscribes) but has no native activity timeline for individual contacts. The historical activity data from ASPEC cannot be reconstructed in Mailchimp. We flag this gap during scoping and recommend the customer export activity history as a CSV for their own records if required for compliance or audit.

ASPEC custom fields (stored in a separate metadata layer from record data) map to Mailchimp Merge Fields on the Audience. We run a mandatory schema discovery step to enumerate all active ASPEC custom fields and their data types before migration. Text fields map to Mailchimp text merge fields; date fields map to date merge fields; number fields map to number merge fields; checkbox or multi-select fields map to Mailchimp text merge fields with comma-separated values. Merge field names in Mailchimp are uppercase and limited to 30 characters, so we truncate and sanitize ASPEC field names during mapping.

ASPEC Users and Owners assigned to Contacts and Companies map to Mailchimp Admin roles. However, Mailchimp Admin roles do not attach to individual contact records the way ASPEC ownership does. We document which ASPEC users correspond to which Mailchimp admin accounts during scoping so that the customer can assign appropriate Mailchimp permission sets post-migration. Individual record-level ownership does not migrate.

ASPEC Pipeline Stages define deal progress and are configured per pipeline. Mailchimp has no pipeline or stage concept. Pipeline stage definitions are flagged as non-migratable during scoping. If the customer has used pipeline stages to categorize customers or prospects (for example, for customer lifecycle stages), we recommend rebuilding this segmentation logic using Mailchimp Tags and Segments post-migration.