Migrate from Ontraport to Pipedrive

Ontraport Contact records map directly to Pipedrive Person. All standard fields (FirstName, LastName, Email, Phone, Address) migrate 1:1. Custom Contact properties migrate as custom fields in Pipedrive. We flag lifecycle stage and source data for preservation as custom Person fields even though Pipedrive does not have a native Lifecycle Stage equivalent. The Ontraport contact_id is stored as a reference field for audit and cross-system reconciliation.

Ontraport Company records map to Pipedrive Organization. Ontraport does not enforce company deduping during import, so we deduplicate Organization names before Pipedrive import to prevent duplicate Organization records. The Organization is created before Person import so that the Org ID lookup is satisfied at the moment of Person insert. If a Contact in Ontraport has no associated Company, we create a placeholder Organization or attach the Person without an Organization depending on the customer's preference during scoping.

Ontraport Deal records map to Pipedrive Deal. Pipeline and stage assignments migrate from Ontraport to Pipedrive Pipeline and Stage values, which we configure before migration. Deal amount, owner, expected close date, and stage status migrate directly. Ontraport Deal associations (Contact or Company) map to Pipedrive Deal person_id or org_id respectively. Pipeline IDs are destination-specific and are created during the schema configuration phase before any Deal data moves.

Each Ontraport Deal pipeline becomes a Pipedrive Pipeline. Ontraport stages map to Pipedrive Stage values within each Pipeline. We configure Pipeline and Stage in Pipedrive before Deal import, mapping stage order and probability percentages from Ontraport to Pipedrive stage characteristics. Deals without a pipeline assignment in Ontraport are mapped to a default Pipeline that we create during schema setup.

Ontraport Tags are plain-text values applied to Contacts. We export all Tag assignments per Contact and reapply them as Pipedrive Labels on the migrated Person record. Tags used for automation triggers are noted in the deliverables but cannot be reactivated in Pipedrive without rebuilding the triggering logic as a Pipedrive Workflow. Label migration is straightforward since both platforms use a flat label/tag namespace per record.

Ontraport Notes are linked to Contact records. When exported as a CSV with the 'include notes' option, each Note generates a separate row that duplicates the Contact's full data. A Contact with three Notes produces three identical rows with one Note text in each. We deduplicate these rows post-export and re-link each Note to its single Contact before import into Pipedrive. Notes migrate as Pipedrive Notes attached to the corresponding Person or Organization.

Ontraport Tasks assigned to Contacts or Deals migrate to Pipedrive Activities (Tasks and Calls) with due dates, completion status, and owner assignments preserved. Completed status maps to Pipedrive's done flag. Task subject and body text migrate as Activity subject and note fields. Owner resolution is by email match against Pipedrive User records.

Ontraport Automation Rules are stored in a proprietary format and cannot be exported as structured data. We extract trigger definitions and enrolled Contact lists for documentation purposes only. Pipedrive Workflows must be redesigned from scratch using Pipedrive's trigger-action model. We deliver a written inventory of every active Ontraport Automation Rule with its trigger conditions, steps, and enrolled Contact count so that the customer's admin can rebuild equivalent Pipedrive Workflows post-migration.

Ontraport Campaigns (email and multi-channel marketing campaigns tied to Contacts) have limited structure that maps to Pipedrive. We export campaign assignments and engagement metrics (opens, clicks, unsubscribes) per Contact as custom Person fields or as a separate campaign membership table. Campaign-level configuration (email templates, send schedules, A/B tests) does not migrate. If the customer uses Pipedrive Campaigns, we map campaign names and assign Contacts with engagement history to the corresponding Pipedrive Campaign.

Ontraport invoice and transaction records include line items, payment status, and product associations. Pipedrive does not have native invoicing. We export invoice data as line-item records attached to the corresponding Deal or Person via custom fields, with payment status and product details preserved. Customers requiring native invoicing connect Pipedrive to Freshbooks or QuickBooks post-migration.

Ontraport Custom Objects (Pets, Courses, Subscriptions, and similar) export with their custom field definitions and relationship tables linking to Contacts or Companies. We map each Custom Object to Pipedrive Custom Fields on Person, Organization, or Deal depending on the relationship type. Relationship IDs must be resolved to Pipedrive IDs at migration time. For one-to-many relationships (a Course with many enrolled Contacts), we provide a relationship table CSV for manual linking or use Pipedrive's custom field workaround.

Ontraport Membership and Course content with Contact enrollment records export as content titles, descriptions, and subscriber lists with enrollment dates. Actual course page structures and membership site HTML are not exportable in structured form and must be rebuilt. We export subscriber lists as custom Person fields (e.g., enrolled_course_names, membership_status, enrollment_date) and provide a written content inventory for the customer's admin to reprovision in their chosen course platform.