Migrate from ActiveCampaign to Twenty CRM

ActiveCampaign Contacts map to Twenty CRM People. Email is the dedupe key and required field on both platforms. All standard contact fields (name, phone, job title, address) map directly. Custom contact fields require pre-creation in Twenty's People object schema before import; we create the equivalent custom fields during the schema design phase and preserve the ActiveCampaign field labels in Twenty's field description for admin reference.

ActiveCampaign Accounts map to Twenty CRM Companies. The Account-Contact association graph migrates as a Person-Company relationship in Twenty. Account custom fields map to Company custom fields. If ActiveCampaign Accounts have no associated domain (some are person-named accounts), we create a stub Company record to satisfy the relationship before importing Contacts.

ActiveCampaign Deals map to Twenty CRM Opportunities. The pipeline and stage assignments migrate as Opportunity pipeline and stage values. Deal custom fields map to Opportunity custom fields. Note: deal notes are not accessible via ActiveCampaign's API and will not transfer to Twenty — we flag this gap during scoping and extract any manually accessible notes via a workaround, but advise the customer that note content is at risk and may need manual re-entry.

ActiveCampaign pipelines (including multiple pipelines on Plus/Pro/Enterprise tiers) map to Twenty CRM pipeline definitions. We extract pipeline names, stage order, and stage probability values and configure the equivalent pipeline in Twenty before importing any Opportunities. Stage probability percentages normalize to Twenty's expected format.

ActiveCampaign tags are a flat label system with no hierarchical structure. We export the full tag taxonomy and either map high-frequency tags to a Twenty CRM custom multi-select field on Person, or deliver the tag list as a CSV for the customer to create a corresponding custom field post-migration. The customer chooses the tagging strategy during scoping based on their most-used tag categories.

ActiveCampaign Custom Objects (Enterprise or Pipelines/Sales Engagement add-on required) map to Twenty CRM custom objects. Custom Object schemas, field definitions, and all associated records migrate. We pre-create the destination custom object schema in Twenty via API or UI before importing data. If the customer does not have Enterprise or the add-on, Custom Objects are not present and this mapping step is skipped.

ActiveCampaign automations are not accessible via the public API and cannot be exported or migrated programmatically. We do not attempt to import automation JSON as it is not available. We deliver a written inventory of every active automation including its trigger, conditions, actions, and recommended replacement in Twenty (or an external automation tool). The customer or a developer rebuilds automations post-migration.

ActiveCampaign campaign sends and engagement data (opens, clicks, unsubscribes) are available via campaign report exports as CSVs. We extract these reports and map campaign-level metrics to custom Task records on the associated Person in Twenty CRM, storing campaign name, send date, and engagement status. Individual email content does not migrate to Twenty as Twenty does not have a native email marketing object.

Contact-level email engagement history (opens, clicks, replies) migrates as Activity Tasks linked to the Person record. We extract engagement timelines via the ActiveCampaign API and map the activity type, timestamp, and summary to a Twenty Task. Email content is not preserved unless specifically scoped; the activity record carries the fact of the engagement rather than the full email body.

ActiveCampaign notes on Contacts and Deals migrate as Comments linked to the Person or Opportunity record in Twenty. We extract note content and creation timestamp and map to the Twenty Comment object. Deal notes are excluded due to the ActiveCampaign API limitation described above.

ActiveCampaign call engagements map to Twenty CRM Tasks with a call subtype identifier. Call duration, disposition, and outcome migrate as custom fields on the Task. The call recording URL does not migrate as Twenty does not have a native call recording attachment model.

ActiveCampaign meeting engagements map to Twenty CRM Tasks with a meeting subtype. Start time, end time, location, and attendee list migrate as Task fields. Attendee emails resolve against the Person records in Twenty to create linked attendees.