Migrate from Wired Plus to Mailchimp

Wired Plus contacts map 1:1 to Mailchimp audience subscribers. We query email, first name, last name, and all custom field values explicitly during extraction. The opt_in and source consent flags are preserved in a dedicated merge field (CONSENT_STATUS) and mapped to Mailchimp's subscriber status (subscribed, unsubscribed, pending, cleaned) to avoid importing unconfirmed contacts as active subscribers, which creates GDPR risk.

Wired Plus flat tag labels map directly to Mailchimp tags. We export all tag assignments per contact, then batch-apply them during import using the Mailchimp Tags API endpoint. Contacts with multiple tags receive all tags in a single API call per contact. We flag and deduplicate any tag names that differ only by case.

Wired Plus company records exist as a related object to contacts. We extract Company_Name and domain fields and map them to Mailchimp merge fields (COMPANY_NAME, COMPANY_DOMAIN) attached to the contact record. If the destination Mailchimp account uses multiple audiences, we use a consistent company naming convention to enable cross-audience segmentation by company later.

Wired Plus campaigns contain email send history, open rates, click rates, and bounce data. We export campaign name, status, send date, and performance metrics as a structured data file alongside the contact import. This is informational history only: campaign records do not become active Mailchimp campaigns. The customer may choose to recreate high-performing campaigns as Mailchimp campaigns using historical metrics as a reference.

Wired Plus automation workflows define trigger-action sequences with conditional branches and time delays. We export workflow definitions as structured JSON metadata including trigger types, delay values, condition logic, and action sequences. The JSON does not import into Mailchimp Customer Journeys because the trigger event IDs and condition semantics differ. We deliver a written workflow audit log documenting each automation's trigger, conditions, and actions with recommended Mailchimp Customer Journey equivalents for the customer's admin to rebuild.

Wired Plus landing pages store HTML content and form configurations. We export page HTML and asset URLs as a packaged folder. Any embedded forms require a new form handler; we flag forms that collected data now needed at Mailchimp so the admin can set up Mailchimp forms or a replacement form handler before launch.

Wired Plus forms capture subscriber data and are linked to campaigns or landing pages. We export field names, field types, and submission logs. Form-to-field mappings must be rebuilt in Mailchimp Forms because form handler IDs do not transfer. Submission logs migrate as a contact history note or custom property so that submission context is not lost.

Wired Plus custom fields are account-specific and export with field labels rather than internal field IDs. We resolve labels to internal identifiers via the API during scoping, then map each to a Mailchimp merge field. Field types are translated: text fields become Mailchimp text merge fields, date fields become date merge fields, numeric fields become number merge fields, and picklist or dropdown fields become dropdown merge fields. Picklist values migrate as merge field options.