Migrate from bxp software to Mailchimp

BXP Contact records map to Mailchimp contacts within an audience. The contact email address is the primary key. We use the bxp API v6 to export contacts and map standard fields (first name, last name, phone) to Mailchimp's corresponding contact fields. Custom fields on each BXP contact are enumerated during scoping and mapped to Mailchimp merge tags with appropriate field types (text, number, date, dropdown). Subscribers without an email address are flagged for manual review before import because Mailchimp requires a valid email for each contact.

BXP Forms are the primary data containers and each form can have a unique field set. If the BXP deployment uses multiple Forms with distinct field structures, we create separate Mailchimp audiences and map each form to its corresponding audience. This preserves the data separation that BXP's form-based model enforces. If all contacts share a common field set across forms, we consolidate into a single audience and tag contacts by their source form.

Every BXP custom field becomes a Mailchimp merge tag. During scoping we enumerate all custom field names and data types from the BXP instance. Text fields map to Mailchimp text merge tags, date fields to date merge tags, and dropdown or multi-select fields to either text or dropdown merge tags depending on Mailchimp's supported types. Mailchimp limits merge tags to 40 characters and alphanumeric characters only; we sanitise BXP field names during the mapping phase. Merge tags are configured in Mailchimp before contact import begins.

BXP contact tags map directly to Mailchimp tags. Tags are preserved on import to maintain segmentation logic that existed in BXP. Tags used for contact classification migrate as Mailchimp tags attached to the contact record. Note that Mailchimp tags are purely organisational and do not carry behavioural data; any tag-based automation logic from BXP must be rebuilt as Mailchimp Customer Journey automations.

BXP call activity logs (call duration, disposition, agent assignment) do not have a native Mailchimp equivalent. Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes) but not individual call records. We export call activity data as a structured JSON file with contact email as the lookup key. The customer stores this externally or imports it into a separate system. Call data is not loaded into Mailchimp because Mailchimp has no contact-centre data model.

BXP QA evaluations tied to contacts and calls are bespoke to each deployment and have no Mailchimp equivalent. Mailchimp is an email marketing platform, not a contact-centre quality assurance system. We export QA records as structured JSON with contact email as the primary key, preserving evaluation scores, auditor notes, and associated call identifiers. The customer stores this file for audit purposes or imports it into a dedicated QA platform.

BXP elearning completion records, training scores, and module assignments do not map to Mailchimp. Mailchimp has no learning management system or training completion tracking. We export elearning data as structured JSON with the contact email as the lookup key. This file serves as the training history record for compliance or audit purposes and is not loaded into Mailchimp's audience data model.

BXP custom archives in CDA and CCL proprietary formats require parsing before migration. We convert these archives into standard CSV or JSON using the format specification we obtain from BXP during scoping. Parsed records then follow the standard Contact and Custom Field mapping path into Mailchimp. CDA/CCL parsing adds scope to the migration and is scoped separately during discovery.