Migrate your ActiveCampaign data

The primary billing and data unit in ActiveCampaign. All standard contact fields, custom fields, and tags migrate cleanly. Note: ActiveCampaign counts unsubscribes, bounces, and unconfirmed contacts toward the contact limit as of November 2025 — we flag this during scoping so the customer understands their actual billable contact count post-migration.

Deals have a rich schema including pipeline, stage, value, owner, contacts, notes, and custom fields. Pipeline structures must be recreated in the destination; we map Deal fields 1:1 and flag stage names that need manual alignment. Deal notes cannot be exported via API and must be captured separately before migration.

Accounts associate with Contacts and Deals. We map the Account object including custom fields and the association graph to Contacts. Account-level data migrates cleanly when the destination has a matching concept.

Pipelines are container objects defining deal stages. ActiveCampaign supports multiple pipelines with custom stages. We extract pipeline definitions including stage names, order, and probability values, then recreate them in the destination system.

Automations are JSON-based workflow definitions with triggers, conditions, and actions. There is no documented export endpoint for automation JSON. Automations must be manually rebuilt in the destination platform, or recreated using equivalent logic in the destination's workflow builder.

We export template HTML and associated metadata. Template content migrates; inline CSS and media embedding may require cleanup in the destination editor depending on the target platform's template rendering engine.

Forms and their field configurations export from ActiveCampaign. We map field types to the destination equivalent. Complex conditional logic in forms may need manual recreation.

Landing pages export as HTML with metadata. The structural fidelity of the export depends on how the destination platform handles imported HTML assets.

Tags are a flat label system applied to Contacts. We export the full tag taxonomy and reassign tags during import. Tags migrate 1:1 with no value mapping required.

Custom objects are a schema-level feature available only on Enterprise or with the Pipelines/Sales Engagement add-on. They define custom field schemas associated with standard objects. We export custom object definitions and their data, then map field types to the destination equivalent.

Historical campaign sends, open/click/geo data, and social shares are available via campaign report exports as CSVs. We extract these reports and map them to the destination campaign object, though the structure varies significantly between platforms.

Contact-level activity history (email opens, link clicks, form submissions, automation entries) is logged per contact. We extract engagement timelines and map them to the destination's activity/engagement object.