Migrate from Regal.io to Mailchimp

Regal Contacts with a valid email address migrate to Mailchimp Members within a target Audience. The Regal contact's primary email field maps to the Member email address, first_name and last_name map to Mailchimp's FNAME and LNAME merge fields, and phone maps to PHONE if present. Contacts without an email address cannot become Mailchimp Members and are flagged in the reconciliation report as email-scope exclusions. We deduplicate by email address during import to prevent duplicate Members from forming if the same email appears on multiple Regal Contacts.

Regal's custom contact attribute schema migrates to Mailchimp merge fields. We extract the full attribute list from Regal's API during discovery, map each attribute to the appropriate Mailchimp field type (text, number, date, phone, address, or dropdown), and create the merge fields in the target Audience before the Member import begins. Merge fields that reference Regal-specific concepts (call_disposition, answer_status, journey_trigger) have no meaningful Mailchimp equivalent and are documented as custom fields to be evaluated for retention or retirement.

Regal Campaign membership (which contacts are enrolled in which outbound programs) migrates as Mailchimp Tags. We export the Campaign-to-Contact association from Regal, create a Tag in Mailchimp for each Campaign name, and apply tags to the corresponding Members during import. Mailchimp Segments are not directly populated from Regal data but can be built post-migration using the imported merge fields and tags as segment conditions.

Regal Events that represent email interactions (opens, clicks, bounces) can be preserved as Mailchimp Tags on the Member record (e.g., tag: email_opened_2025_06_15) or as a structured note in a custom text merge field. Mailchimp does not support a native event-stream model, so we document the event types and timestamps in a JSON artifact that the customer's team can use to re-trigger email automations if needed. Voice and SMS events from Regal have no Mailchimp equivalent and are excluded.

SMS conversational history stored in Regal Contacts has no Mailchimp equivalent. Mailchimp supports SMS marketing sends but does not maintain a threaded SMS inbox. We export SMS thread data as a structured JSON file and flag it for evaluation against SMS-native platforms (Klaviyo, Attentive, Postscript) if the customer intends to continue SMS marketing. SMS data is not loaded into Mailchimp.

Call transcripts and recording metadata in Regal are excluded from the Mailchimp migration. Mailchimp has no mechanism to store or display telephony data. We export available transcripts as structured text files and call recording metadata (duration, disposition, agent ID) as a JSON artifact. The customer evaluates whether this data is needed for compliance retention or can be archived.

Regal Journeys are event-triggered conditional sequences across voice, SMS, and email. Mailchimp Automations are time-delay and trigger-based email sequences that do not support voice or SMS steps. We document each active Regal Journey as a step-by-step conditional rule table specifying trigger conditions, step sequence, channel per step, delay logic, and exit criteria. The customer uses this documentation to rebuild the email-only portion of each Journey in Mailchimp Automations. Voice and SMS steps are flagged as out-of-scope for Mailchimp and noted for a telephony replacement evaluation.

Regal AI Agent configurations — voice scripts, decision trees, persona settings, and handoff logic — are tied to Regal's proprietary agent runtime and are not exportable via API or UI. AI Agents are explicitly excluded from the migration scope. We deliver a written inventory of the AI Agent configurations in use (agent name, primary use case, trigger conditions, key decision points) so the customer can evaluate whether a replacement platform (e.g., Five9, Genesys Cloud, or a conversational AI tool) is needed. The customer rebuilds agent logic in the replacement platform post-migration.