Migrate from Adaptix to Mailchimp

Adaptix Contacts migrate 1:1 to Mailchimp Audience Members. The primary email address becomes the subscriber_id dedupe key. All standard fields (first name, last name, phone) map to Mailchimp merge fields FNAME, LNAME, PHONE. Custom properties on the Contact map to additional merge fields that we create in the destination Audience before import.

Adaptix Companies do not have a direct Mailchimp equivalent because Mailchimp has no native Account or Company object. We extract the primary Company associated with each Contact and populate Mailchimp merge fields (COMPANY, INDUSTRY, WEBSITE) on the Audience Member record. Multi-company contacts require customer guidance on which company record to prioritize.

Adaptix Tags migrate to Mailchimp Tags on a per-Audience basis. We export the full tag assignment table (Contact ID to Tag name) and apply tags during the Audience Member import using Mailchimp's batch tag API endpoint. Tags used for segmentation are preserved as a mapping table to assist with static segment reconstruction.

Adaptix Segments are built from filter rules; Mailchimp Segments can be either dynamic (rule-based, rebuilt) or static (membership list). We export segment membership as a list of contact email addresses for each Adaptix Segment. In Mailchimp we create static segments with the original contact lists, giving the team a reference point while they rebuild dynamic rules in Mailchimp's segment builder.

Adaptix Automations are not executable in Mailchimp due to architectural differences in trigger models and action types. We deliver a written Customer Journey Map for each Adaptix Automation documenting the trigger, every step, condition branches, delays, and exit actions. The customer or their Mailchimp partner uses this to rebuild journeys in Mailchimp's Customer Journey Builder.

Adaptix Landing Pages export as static HTML with embedded form markup. Dynamic connections to Adaptix's form handler, tag assignments, and automation triggers are severed on export. We package page HTML and form definitions separately. The customer rebuilds the page in Mailchimp Landing Pages or their CMS using the exported HTML as a visual reference; we flag which pages had automation connections during discovery.

Adaptix Form field definitions and consent settings export as JSON. Mailchimp Signup Forms use a different field schema and cannot import the JSON directly. We deliver a field-by-field mapping table showing each Adaptix form field, its type, and the recommended Mailchimp field equivalent. The customer's marketing team rebuilds forms in Mailchimp's form builder using the mapping as a guide.

Adaptix Custom Properties on Contacts vary per account and are not standardized. We flag every custom property during discovery, identify the Mailchimp equivalent field type (text, number, date, phone, address, or dropdown), create the merge field in the destination Audience before import, and map the source values. Any Adaptix custom property without a clear Mailchimp field type is flagged for the customer to decide whether to include or drop.

SMS opt-in status and consent records on Adaptix Contacts flag explicitly for Mailchimp SMS compliance. Mailchimp requires double opt-in for SMS-eligible contacts. We identify all contacts with SMS consent in Adaptix, flag them separately, and recommend a re-confirmation campaign approach rather than bulk import of SMS-eligible status to avoid Mailchimp's consent policy violation.