Migrate from Alpine IQ to Mailchimp

Discovery and export planning

We audit the Alpine IQ account scope: contact volume (Personas), order volume, active audience definitions, loyalty program settings (points, tiers, discount groups), opt-in record counts, and custom field inventory. We extract the full store mapping configuration for multi-location accounts and identify any Flow Event definitions requiring documentation. We assess blocklist volume and determine whether blocklist completeness export is required for compliance. The discovery output is a written migration scope with record counts per object, a custom field inventory for Mailchimp merge field creation, and a decision on whether Flow Event inventory is needed for rebuild documentation.

Destination schema setup in Mailchimp

We create the Mailchimp Audience with all required standard merge fields (FNAME, LNAME, EMAIL, PHONE, BIRTHDAY, ADDRESS and its subfields) and all custom merge fields identified during discovery (AIQ_POINTS, AIQ_TIER, AIQ_SMS_OPT, AIQ_CREATE, AIQ_LAST_OD, AIQ_TOTAL_$, AIQ_ORD_CNT, AIQ_SRC_ID, GENDER, MED_ID, AIQ_STORE_LOC). Groupings and interest categories are created to mirror Alpine IQ audience definitions where tags are the chosen segmentation medium. The Mailchimp API credentials are validated and rate limits confirmed before export begins.

Contact extraction with blocklist audit

We export Personas from Alpine IQ using the /api/v2/personas endpoint with pagination and chunking. We run a supplementary blocklist audit query against alternative endpoints to identify suppressed contacts not returned by the standard export. Suppressed contacts are flagged with their reason (unsubscribed, bounced, complained) and merged into the contact export with the appropriate Mailchimp status. Opt-in records are fetched from /api/v2/optin endpoints and joined to the Persona export. We validate record counts against the Alpine IQ dashboard totals before pushing data to Mailchimp.

Order history extraction and tagging

We export Order records from Alpine IQ, linking each order to the corresponding Persona by customer_id. For each contact, we compute aggregate fields (total_spend, order_count, last_order_date) and generate per-order tags (e.g., CATEGORY_FLOWER, BRAND_BRETT, ORDER_AMT_HIGH). Attribution parameters from order.attr fields generate additional tags (ATTR_source, ATTR_campaign) for campaign tracking rebuild. The tagged contact payload is prepared in Mailchimp batch-compatible format.

Batch import to Mailchimp with reconciliation

We push contact records to Mailchimp via the Members API in batches of 500, applying exponential backoff on rate limit responses (Mailchimp caps at 10 calls per second on most tiers). Each contact is assigned the appropriate status (subscribed, unsubscribed, cleaned) based on the opt-in and blocklist audit. Tags are applied in the same batch payload. After import, we reconcile record counts: contacts in Alpine IQ minus suppressed contacts should equal members in the Mailchimp audience. We spot-check 25-50 records against the Alpine IQ source data for field-level accuracy.

Cutover and rebuild handoff

We freeze Alpine IQ contact writes during the cutover window, run a final delta export for any contacts modified during migration, and apply updates to Mailchimp. The Mailchimp audience is validated as the system of record. We deliver the migration handoff document containing: loyalty program settings snapshot (points, tiers, expiration rules) extracted from Alpine IQ for manual Mailchimp rebuild, Flow Event inventory with trigger conditions and action sequences for Customer Journey rebuild, store mapping configuration for location-based segmentation, and segment rebuild recommendations based on behavioral criteria from each Alpine IQ audience definition. We provide a one-week post-cutover reconciliation window for the customer's team to report any data gaps.