Migrate from Ontraport to Mailchimp

Ontraport Contact records map 1:1 to Mailchimp Members within an Audience. All standard fields (First Name, Last Name, Email) map directly. Custom fields on Contact map to Mailchimp Merge Fields per audience, with field types converted to Mailchimp-supported types (text, number, date, phone, address, dropdown). Lifecycle stage data from Ontraport migrates as a text merge field for segmentation in Mailchimp Customer Journey Builder.

Ontraport Companies have a one-to-many relationship with Contacts. Mailchimp has no Company or Account object. We export all Company records and their linked Contact IDs, then decide with the customer whether to map the Company name to a Company merge field on each Contact, apply it as a tag on each Contact, or discard it if the data is not needed for ongoing campaigns. Company deduping is recommended before export since Ontraport does not enforce unique Company names.

Ontraport Tags applied to Contacts map directly to Mailchimp Tags on each Member. Tags serve as the primary segmentation mechanism in Mailchimp since there is no criteria-based auto-update segment equivalent to Ontraport's database segments. We export the full tag list per Contact and reapply as flat tag assignments during import. Tag-based automation triggers in Mailchimp Customer Journey Builder require manual rebuild.

Ontraport Notes are linked to Contact records but Mailchimp has no native Note object. We export Notes per Contact and offer two strategies: concatenate Note content into a long-text merge field on the Member record, or apply a Has Notes tag to Contacts that had Note records so the admin can review them post-migration. The Ontraport Notes export quirk (each Note generates a duplicate Contact row) is deduplicated before import.

Ontraport Deals have pipeline, stage, amount, owner, and Contact or Company associations. Mailchimp has no Deal or pipeline object. We export all Deal records and their associations, and present two options: map Deal stage to a Deal_Status merge field on the Member for reference, or apply a deal_stage tag to Contacts with open Deals. Deal amounts and owner assignments cannot be represented natively in Mailchimp and require a paired CRM or manual tracking for sales pipeline management.

Ontraport invoice and transaction records include line items, payment status, and product associations linked to Contacts. Mailchimp has no invoice, payment, or transaction record object. We export full invoice and transaction history for the customer's financial records reconciliation and flag that payment tracking requires a dedicated payment processor, accounting tool, or e-commerce integration post-migration.

Ontraport Automation Rules define triggers, conditions, and multi-step actions that govern contact journeys. Mailchimp Customer Journey Builder uses a different automation model with entry triggers, conditions, and action blocks. We export a written inventory of every active Automation Rule including trigger definitions, enrolled Contact counts, and step summaries so the customer's team can rebuild equivalent Customer Journeys in Mailchimp. The automation logic itself cannot be imported.

Ontraport Campaigns hold email and multi-channel marketing campaign configurations with engagement metrics per Contact. We export campaign assignments and per-contact engagement data (opens, clicks, unsubscribes) as Merge Field values or tags on Members. The campaign-level configuration (templates, send schedules, audience filters) cannot be imported into Mailchimp and requires rebuild. Historical engagement data migrates as reference data, not as active campaign records.