Migrate from Levitate to Mailchimp

Levitate Contacts map directly to Mailchimp Subscribers within an Audience. We extract contact records via Levitate's UI-based CSV export, then import using Mailchimp's API with upsert logic keyed on email address to resolve duplicates. Standard properties (first name, last name, email, phone, company) map to Mailchimp's corresponding subscriber fields. Any contact records with duplicate email addresses are flagged for the customer's admin to resolve before the final import batch runs.

Levitate's tag taxonomy maps to Mailchimp Tags on a 1:1 basis with the original tag names preserved. We extract the complete tag list from Levitate contact records, deduplicate it, and apply it as Tags during the Mailchimp Subscriber import. Tags used for automation triggers in Levitate are flagged as a priority segment for rebuilding in Mailchimp's Customer Journey Builder using tag-addition as a trigger condition. Mailchimp Tags are scoped per audience, which means the customer should decide whether to consolidate all contacts into a single audience or maintain separate audiences per tag-based segment.

Levitate Key Dates (birthday, renewal date, policy expiration, and custom age milestones) are a Levitate-specific field type that drives date-triggered automations. Mailchimp has no equivalent date-triggered automation model. We map Key Dates to Mailchimp custom merge fields of date type within each Audience. These fields must be created in Mailchimp before the contact import runs. We flag every Key Date field found during discovery and confirm with the customer that the destination audience has equivalent merge fields created, or that they are comfortable with dates landing as plain date fields with no automation trigger behavior.

Levitate campaign metadata (campaign name, send date, subject line, total sends) and aggregate engagement stats (opens, clicks, replies per campaign) are exported from Levitate's reporting UI and mapped to Mailchimp campaign records. Because Levitate does not expose a bulk export API for engagement events, individual email open and click timestamps per subscriber are not directly migratable. We import aggregate open and click counts as contact-level custom properties on each subscriber so that sales and marketing teams can see last-engagement data at the contact level without rebuilding the full event timeline.

Levitate automations are server-side workflow sequences with email steps, delays, conditional branches, and tag-action triggers. Mailchimp's Customer Journey Builder uses a completely different event-triggered model with entry triggers, time delays, condition-split branches, and action blocks. There is no export capability from Levitate and no direct migration path to Mailchimp. We extract the full list of active automations from Levitate's UI, document each automation's trigger, conditions, steps, and tag actions in a written handoff inventory, and the customer's admin uses that inventory to rebuild Customer Journeys in Mailchimp using the migrated tag taxonomy as the segmentation foundation.

Levitate SMS logs are stored per contact in the thread view but are not available via bulk export. We extract available SMS thread data from Levitate's contact profile UI where accessible and import it as contact-level note entries in Mailchimp or as a custom contact property storing the last SMS interaction date. Long-term SMS history cannot be fully reconstructed without manual per-contact export from Levitate, which we flag during discovery scoping.

Attachments referenced in Levitate automations or campaign content are stored as URLs or references to Levitate's content library. We export the attachment reference URLs and flag any files that must be re-uploaded to Mailchimp's Content Studio before automations or campaigns can reference them. Actual file binaries are not migratable from Levitate's hosted content library.

Levitate user accounts with owner, admin, and member roles are mapped to Mailchimp Users by email match. Role-level permission scopes from Levitate are documented as a written reference but cannot be directly transferred because Mailchimp's permission model uses a different role hierarchy (Admin, Manager, Author, Viewer). We flag the role mapping discrepancy and recommend the customer review Mailchimp's user permission settings post-migration.