Migrate your Ontraport data

The primary object in Ontraport. All standard fields, custom fields, lifecycle stages, source data, and engagement history are available via API. We map all Contact fields 1:1 and flag custom properties that may need schema adjustment at the destination.

Prebuilt object with a one-to-many relationship to Contacts. We export Company records and the associated Contact links, but recommend deduping Company names before import since Ontraport does not enforce Company uniqueness.

Prebuilt custom object for pipeline management. Deals have pipeline, stage, amount, and owner fields. We map Deal fields and preserve the Contact or Company association, but pipeline IDs are destination-specific and must be remapped.

Applied to Contacts to categorize and trigger automations. Tag names are plain-text values. We export all Tag assignments per Contact and reapply them as flat tag lists at the destination, noting that destination tag logic may differ.

Linked to Contact records. When exported as a CSV, each Note generates a separate row duplicating the Contact's data, so we deduplicate and re-link Notes to Contacts after import.

Legacy automation feature replaced by Automation Rules. A Sequence is a series of timed steps tied to Contacts. We export step definitions and enrollment data, but automation logic cannot be imported into non-Ontraport systems and must be rebuilt.

Ontraport's primary automation engine. Automations define triggers, conditions, and multi-step actions across the account. We export trigger definitions and enrolled Contact lists, but automation logic must be reconstructed at the destination.

Email and multi-channel marketing campaigns tied to Contacts. We export campaign assignments and engagement metrics (opens, clicks, unsubscribes) per Contact, but campaign-level configuration requires manual re-creation.

Ontraport's payment records include line items, payment status, and product associations. We export transaction history and invoice data, preserving the Contact linkage and payment status for reconciliation in the destination system.

Custom objects (Pets, Courses, etc.) can be created with custom fields and relationships to Contacts or Companies. We export all Custom Object records and relationship tables, but relationship IDs must be remapped since they are internal to the account.

Content objects tied to Contact enrollment records. We export content titles, descriptions, and subscriber lists with enrollment dates. Actual course content and page structures require separate export and manual re-provisioning.

Ontraport hosts forms and pages with submission data linked to Contacts. We export form submissions and field data, but HTML-based page templates are not exportable in structured form and must be rebuilt at the destination.

Assigned to Contacts or Deals with due dates and completion status. We export task records with owner assignments and link them back to the target object at the destination.

Prebuilt custom object types for data collection and event management. Survey responses and event registration records are exported as Custom Object data, with field mapping handled case-by-case based on survey structure.