Migrate from ActiveDEMAND to Mailchimp

ActiveDEMAND Contacts map directly to Mailchimp Members within a target Audience. The contact email is the primary key used for upsert operations. First name, last name, phone, and all mapped Brand Custom Fields migrate as Mailchimp standard fields or Merge Fields. We deduplicate by email on import. Unsubscribed or bounced contacts in ActiveDEMAND are set to the corresponding status in Mailchimp to preserve GDPR and CAN-SPAM compliance at the point of migration.

ActiveDEMAND Brand Custom Field schemas (which vary per brand/tenant) map to Mailchimp Merge Fields. We export the full schema definition first before exporting data, then create each Merge Field in Mailchimp with the correct type: text fields get MERGEX text type, phone numbers get MERGEX phone, dates get MERGEX date, and so on. Mailchimp imposes a ten-character merge tag limit and a per-Audience 40-merge-field cap. Fields exceeding these limits are noted in the mapping document for the customer to resolve in Mailchimp settings before import.

ActiveDEMAND Contact Lists (static and dynamic) are exported as a list of contact IDs per list. We reconstruct each list in Mailchimp as a Tag assignment on every Member in the original list. Dynamic lists are exported as a static snapshot; Mailchimp's segment-builder replaces dynamic list behavior. The customer chooses whether to create individual Tags per list or consolidate into Groups during scoping.

ActiveDEMAND Campaigns (email type) are exported with their name, status, and send date. We create a corresponding Mailchimp Campaign record per ActiveDEMAND campaign for inventory purposes, and link the Members who were sent or opened each campaign as Tag notes on their Member record. Campaign body content (HTML, images, templates) is exported as a structured asset file; the customer rebuilds the email template in Mailchimp's editor using the exported assets as reference.

ActiveDEMAND Automated Workflows are exported as metadata: workflow name, trigger type, step count, and step descriptions. Mailchimp Customer Journey automations are different in structure (event-triggered email sequences with delay steps). We do not migrate workflows as code. We deliver a written inventory of every ActiveDEMAND workflow with its trigger conditions, steps, and a recommended Mailchimp Customer Journey equivalent, and the customer's admin rebuilds them post-migration.

ActiveDEMAND Funnels represent multi-stage customer journeys. We export funnel names, stage definitions, and the contact IDs assigned to each stage as a Tag per stage. Mailchimp's Customer Journey builder and segment-based email sends replace funnel behavior. We map funnel stage labels to Tag names and assign the tag to the relevant contacts. Stage-level conversion data does not migrate as aggregate records; the customer plans to rebuild funnel analytics in Mailchimp's built-in reporting.

ActiveDEMAND Forms and their field definitions are exported as metadata (form name, field list, field types). Mailchimp's embedded signup forms and landing page integrations replace this. The HTML/CSS form body does not migrate directly; we provide the field inventory and recommend Mailchimp's form builder or a third-party form tool (Typeform, JotForm) as the replacement. The form field mapping document tells the admin which Mailchimp merge fields correspond to each ActiveDEMAND field.

ActiveDEMAND Call Tracking records (source number, destination number, duration, recording URL, linked Contact) have no Mailchimp equivalent. Mailchimp does not support call logging, phone number storage as a call record, or recording URL attachments. We export call tracking records as a structured CSV for the customer to load into a separate CRM or phone system, and we link the Contact's email to the export row so the record remains referentially linked. If the customer uses a separate CRM post-migration, the call CSV maps by email to that CRM's contact records.

ActiveDEMAND Chat Conversation records (timestamps, message threads, visitor contact info) have no Mailchimp equivalent. We export conversation metadata and text content as a structured archive CSV linked to the contact email. Mailchimp's platform does not store chat history. The customer may use this CSV for reference in a separate helpdesk tool or CRM.

ActiveDEMAND Appointments and Tour booking records (date, time, status, linked Contact, community reference) have no Mailchimp equivalent. We export appointment records as a structured CSV linked by contact email, with community assignment preserved as a custom tag on the contact record if needed. The customer reconciles appointment data with a separate scheduling or property management tool post-migration.

ActiveDEMAND Companies exist as a related object to Contacts. Mailchimp has no native Company or Account object; Members are flat audience records without a parent-company relationship. We extract Company name, domain, city, and state and write them to Mailchimp Merge Fields (COMPANY, WEBSITE, CITY, STATE) so the data is preserved on the Member record, even without a formal relationship structure. If the customer needs a CRM post-migration, the Company-to-Contact relationship requires re-establishment there.

ActiveDEMAND Custom Dashboards, aggregate analytics, funnel conversion rates, and attribution summaries are configuration-bound and not portable. We export report definitions as a metadata document listing each ActiveDEMAND report, its metrics, and the ActiveDEMAND fields powering it. Mailchimp's own reporting (open rate, click rate, audience growth, revenue tracking if e-commerce connected) replaces this. The customer screenshots key ActiveDEMAND dashboards pre-migration and plans Mailchimp equivalents using migrated contact and tag data.