Migrate from Aurea CRM to Mailchimp

Aurea CRM Contact records map 1:1 to Mailchimp Members within a configured Audience. We extract all standard contact fields (firstname, lastname, email, phone, address components) via Aurea's Import/Export module and map them to Mailchimp's required FNAME, LNAME, EMAIL merge fields plus the optional address merge fields using Mailchimp's structured address field format (street, city, state, zip, country split across the field). Subscriber status (active, unsubscribed, bounced) migrates as Mailchimp Member status. The Aurea contact's email address serves as the primary dedupe key during import.

Aurea CRM Account (Company) records have no direct Mailchimp equivalent because Mailchimp has no native Account or Company object. We handle this in two ways: (1) the company name from Aurea Account maps to a custom merge field COMPANY or BUSINESSNAME on each Member, and (2) Aurea Account IDs and names are written as Tags on each Member so that the customer can segment by company in Mailchimp using Tag-based segments. We document the full Account-ID-to-Tag mapping during scoping so that this relationship is queryable post-migration.

Aurea Campaign Manager records (bundled at the Enterprise tier) map to Mailchimp Campaigns. We migrate campaign metadata: campaign name, campaign type, campaign status, send date, subject line, open rate, click rate, bounce rate, and unsubscribe count from Aurea's campaign response metrics. These are recorded as a Campaign Migration Log in a shared spreadsheet or documented in Mailchimp's campaign notes field. Actual email content (HTML bodies, templates, images) migrates as Mailchimp content blocks or is flagged for manual rebuild using Mailchimp's template builder since content encoding varies by Aurea installation.

Aurea CRM Activity records of type email capture the send, open, and click history tied to campaigns. Mailchimp does not store a full structured activity log per contact; instead, engagement is represented as timestamped events (last open, last click, total opens, total clicks) on the Member record plus campaign-level reporting. We map Aurea's activity timestamps to Mailchimp's Member activity fields and note in the migration log that the granular activity record structure is flattened. Plain call and meeting activities from Aurea do not have a Mailchimp equivalent and are documented in the handoff as requiring manual note-taking or a linked CRM.

Aurea CRM administrator-defined custom fields across Contact and Account map to Mailchimp Merge Fields. We pre-create merge fields in Mailchimp before import using the Mailchimp Marketing API (POST /lists/{list_id}/merge-fields) with the appropriate field type: text for free-text fields, date for date fields, phone for telephone fields, address for structured address components. Multi-select and dropdown fields from Aurea CRM cannot map directly because Mailchimp merge fields are single-value; we flatten these to pipe-delimited text (e.g., 'Interest A | Interest B') in a text merge field and document the original picklist options for the customer.

Aurea CRM Owner records map as Tags on migrated Members to preserve the record ownership attribution. Each Aurea user email is written as a tag (e.g., 'Owner: [email protected]') on the Members that user owned in Aurea CRM. This is a lookup mapping because Mailchimp has no User object; the Tag serves as a reference marker that the customer's admin can use to query or segment by original owner. We deliver the Owner-ID-to-email mapping as a reference document alongside the migration.

Aurea CRM Partner records from the Partner Relationship Management module represent channel partner leads and partner-owned accounts. These migrate as Mailchimp Members with a 'Partner: [partner_name]' Tag and relevant merge fields (partner_id, partner_tier, partner_territory) from the Aurea Partner record. Partner-specific quota and territory assignments are documented in the partner mapping log and flagged for manual rebuild if the customer needs partner performance tracking beyond Mailchimp segmentation.

Aurea CRM document management stores files linked to Contact and Account records. Mailchimp Members have no native attachment or document storage. We flag records with high attachment volume (more than three files per record) during scoping and deliver a document inventory list with file URLs, record association, and file store location. The customer decides whether to migrate files to a separate cloud storage solution (Google Drive, SharePoint) or leave them in Aurea CRM as a read-only archive. No file data moves into Mailchimp.