Migrate from Ontraport to Salesforce Sales Cloud

Ontraport Contacts map to Salesforce Lead or Contact based on the customer's lifecycle stage matrix. We define the split rule during scoping: contacts with lifecycle stage of Subscriber or lead map to Salesforce Lead; contacts with lifecycle stage of Customer, Evangelist, or other post-sale stages map to Salesforce Contact attached to an Account. We preserve the original Ontraport lifecycle stage in a custom field on both Lead and Contact for audit. Tags assigned to the Contact migrate as a multi-select picklist field.

Ontraport Company records map to Salesforce Account. Ontraport does not enforce Company name dedupe, so we run a dedupe pass on Company names before import to prevent duplicate Accounts. The Company address maps to the Account billing address. The Company-Contact relationship is preserved by linking migrated Contacts to their parent Account via AccountId lookup after Account insert.

Ontraport Deals map to Salesforce Opportunity. The Deal pipeline maps to a Salesforce Record Type and Sales Process. Deal stage maps to StageName, and the stage probability migrates to Salesforce StageProbability rounded to the nearest integer. Deal amount, close date, owner, and associated Contact or Company links all transfer. Closed-Lost and Closed-Won custom fields become Salesforce Loss Reason and Win Reason fields.

Ontraport pipeline stages map to Salesforce Opportunity stages. Each Ontraport pipeline becomes a Salesforce Record Type with a corresponding Sales Process that limits the visible stages per pipeline. Stage probability percentages migrate to Salesforce StageProbability values. We configure the stage order to match Ontraport's visual pipeline ordering.

Ontraport tags are plain-text values applied to Contacts. We export all tag assignments per Contact and reapply them as a Salesforce multi-select picklist field. The customer chooses the field label and API name during scoping. If the customer uses tags for content classification, we offer an optional migration to Salesforce Topics with TopicAssignment records.

Ontraport Notes are linked to Contact records. When exported as CSV, each Note generates a separate row duplicating the full Contact record. We deduplicate these rows after export and re-link each Note to its single Contact record before import. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Lead, Contact, Account, or Opportunity. Note body transfers as rich text.

Ontraport Tasks assigned to Contacts or Deals map to Salesforce Task records. Due date, completion status, priority, and task body transfer directly. Owner assignment resolves by matching the Ontraport owner email to the Salesforce User record. Tasks linked to Deals resolve the WhatId to the migrated Opportunity.

Ontraport Automation Rules define triggers, conditions, and multi-step actions across the account. We export trigger definitions, condition logic, and enrolled Contact lists. The automation workflows themselves cannot be exported and must be redesigned in Salesforce Flow. We deliver a written inventory of every active Ontraport Automation with its trigger type, conditions, actions, and a recommended Salesforce Flow equivalent for the customer's admin to rebuild.

Ontraport Campaigns are email and multi-channel marketing programs tied to Contacts. We export campaign assignments and engagement metrics (opens, clicks, unsubscribes) per Contact. Campaign-level configuration requires manual recreation in Salesforce. Campaign Members migrate as CampaignMember records linking the Contact or Lead to the Campaign.

Ontraport payment records include line items, payment status, and product associations. We export transaction history with Contact linkage and payment status for reconciliation. Invoices and transaction history do not map to standard Salesforce objects; we recommend either migrating them as a custom Invoice__c object with InvoiceLineItem__c or linking completed payments to the related Opportunity. The customer chooses during scoping.

Ontraport Custom Objects store non-standard records with custom fields and relationships to Contacts or Companies. We export all Custom Object records and relationship tables. At the destination, we pre-create Salesforce custom objects with matching field types, lookup relationships to Contact or Account, and validation rules before any data import. Relationship IDs must be resolved to Salesforce IDs during migration because Ontraport relationship IDs are not valid in Salesforce.

Ontraport Membership and Course content objects store titles, descriptions, and subscriber enrollment lists with enrollment dates. We export the content metadata and the subscriber-to-contact mapping. Course content and page structures are not portable in structured form. The subscriber enrollment list migrates as a custom enrollment object with a lookup to Contact and a reference to the related Course or Membership record.

Ontraport hosts forms and pages with submission data linked to Contacts. We export form submission field data as custom Contact fields or as a custom FormSubmission__c object. HTML-based page templates are not exportable in structured form and must be rebuilt. We document every form field and its Ontraport data type for the customer's admin to configure in Salesforce Web-to-Lead, Experience Cloud forms, or a third-party form tool.

Ontraport owners on Contact, Company, Deal, and Task records map to Salesforce User records by email match. Owners without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes. We extract all distinct owner emails across all migrated objects to generate the full owner list upfront.