Migrate from Ontraport to Twenty CRM

Ontraport Contact records map directly to Twenty People. All standard fields (First Name, Last Name, Email, Phone, Address) migrate 1:1. Custom contact properties map to Twenty custom fields which must be pre-created in Settings → Data Model before CSV import. Lifecycle stages from Ontraport migrate as a custom text or select field since Twenty does not have a native lifecycle stage object. Owner resolution is by email match against Twenty Members.

Ontraport Company records map to Twenty Company. The Company name is the dedupe key. Ontraport does not enforce unique Company names, so we recommend deduping by domain or name normalization before import to avoid duplicate Company records in Twenty. Company records must import before People so that the People-to-Company relationship (Work Intelligence in Twenty) is satisfied at insert time.

Ontraport Deal records map to Twenty Opportunity. Pipeline ID and stage from Ontraport map to Twenty's Opportunity pipeline and stage. We create Twenty pipeline stages matching Ontraport stage names and probabilities before importing Deals. Deal amount, close date, owner, and Contact or Company association migrate directly. Closed-won and Closed-lost status maps to the equivalent Twenty stage.

Ontraport Tags are flat plain-text values applied to Contacts. We export tag assignments per Contact and apply them as a custom Tags field in Twenty People (stored as comma-separated text or as a tag-relation table depending on the customer's preference). Tags do not carry automation trigger logic to Twenty since Ontraport Automation Rules are not exportable; tags migrate as data labels only.

Ontraport Notes linked to Contacts must be deduplicated before import because Ontraport's CSV export repeats the full Contact row for each Note attached to it. We deduplicate these rows post-export, extracting each Note body and associating it with the single correct Contact record. Notes then migrate to Twenty Note records linked via the standard note-relation to the correct People record.

Ontraport Automation Rules cannot be exported as structured automation code. We extract the trigger definitions, enrolled Contact counts, and rule names as a written inventory document for the customer's admin to reference when rebuilding in Twenty Workflows. This is an inventory handoff, not a data migration — the automation logic itself must be redesigned from scratch in Twenty.

Ontraport Sequences (legacy timed step sequences) export as step definitions and enrollment data but the cadence logic cannot be imported. We document the sequence steps, enrollment dates, and Contact assignments in a written inventory for rebuild in Twenty Workflows. Email templates used within sequences migrate as text content only; HTML template structure requires rebuild.

Ontraport Campaign assignments and engagement metrics (opens, clicks, unsubscribes per Contact) migrate as structured data attached to the Contact record. Campaign configuration and email content do not migrate. If the customer has multiple active campaigns, we recommend creating a Campaign custom object in Twenty and linking People to it via a relationship table, preserving the campaign assignment history.

Ontraport Invoice records with line items, payment status, and product associations migrate as a custom Invoice object in Twenty. Payment status, total amount, and Contact linkage transfer. We create the Invoice custom object with fields for amount, status, date, and related Contact lookup before import. Invoice PDF attachments migrate as file links if stored externally; Ontraport-hosted PDFs require separate export.

Ontraport custom objects (Pets, Courses, Memberships, etc.) with custom fields and Contact or Company relationships migrate to identically named Twenty custom objects. We pre-create the destination custom object schema in Twenty Settings → Data Model, including all custom fields and lookup relationships, before any records load. Relationship IDs in Ontraport must be resolved to Twenty People or Company IDs during the transform phase.

Ontraport Membership and Course content objects with subscriber enrollment lists migrate as custom objects in Twenty. We export content titles, descriptions, and subscriber lists with enrollment dates. Actual course content (video, HTML pages, files) requires separate export from Ontraport since page structures are not exportable in structured form. Enrollment dates and subscription status transfer as structured data.

Ontraport Tasks assigned to Contacts or Deals with due dates and completion status migrate to Twenty Task records. Task title, body, due date, completion status, and owner migrate directly. Owner resolution is by email match against Twenty Members. Tasks must import after People and Opportunities so that the related record lookups are satisfied at insert time.