Migrate from Ontraport to HubSpot

Ontraport contacts map directly to HubSpot contacts. Every standard contact property (name, email, phone, address, job title) has a HubSpot equivalent. Custom contact properties migrate as HubSpot custom properties. The Ontraport contact-to-company association links to HubSpot's primary company via company_id.

Ontraport companies map directly to HubSpot companies. Standard fields (name, domain, address, industry, employee count) map to HubSpot's company properties. Ontraport parent-child company hierarchies map to HubSpot's parent company field using ID-based references. Multi-company contact associations surface as HubSpot Account Contact Relationships, preserving the N:N association flexibility from Ontraport's data model.

Ontraport deals map to HubSpot deals (internally called Opportunities). Deal name, amount, close date, and stage map to HubSpot deal properties. Ontraport pipeline stages map to HubSpot deal pipeline stages via value mapping — each Ontraport stage name gets mapped to the corresponding HubSpot stage in the configured pipeline.

Ontraport deal pipelines map directly to HubSpot deal pipelines. Each Ontraport pipeline becomes a named HubSpot deal pipeline with its own stage definitions. If Ontraport has multiple pipelines (e.g., one for product sales, one for services), HubSpot creates corresponding pipelines so deal records land in the correct workflow context.

Ontraport products map to HubSpot products with a nuance: Ontraport product pricing includes per-unit price, setup fee, and recurring amounts. HubSpot products store price and have Line Items that attach quantity and discounts to deal records. We map Ontraport product price to HubSpot product price and create Line Items per deal-product association.

HubSpot has no native order or invoice object. Ontraport order records (with status, total, payment method, fulfillment info) migrate as a HubSpot custom object named 'Order.' The custom object links to the contact who placed the order and includes all order line items as JSON or as separate custom object records.

Ontraport tags are flat label strings applied to contacts. In HubSpot, tags migrate as a multi-select custom property on the contact record, preserving the original tag names. For segmentation, HubSpot Lists (static or dynamic) can be created post-migration based on tag values — this requires manual list-building in HubSpot's UI or via workflow.

Ontraport email logs, call records, and notes attach to contacts with timestamps and owner information. These map to HubSpot's engagement timeline (email, call, meeting, note). Original timestamps and owners are preserved. Ontraport bulk email campaign sends do not map to HubSpot marketing emails — those are a separate system.

Ontraport membership and course enrollment records have no HubSpot native equivalent. These migrate as HubSpot custom objects that link to the contact record, storing enrollment date, product name, access level, and expiration. Enterprise-tier HubSpot with Operations Hub is required for custom objects.

Ontraport user-defined custom objects map 1:1 to HubSpot custom objects. The custom object name and all custom fields migrate with type-aware mapping (text, number, date, pick-list). Custom object associations in Ontraport that use N:N relationships need HubSpot junction objects — this is surfaced in the pre-migration plan.

Ontraport form submission records containing field values and submission timestamps attach to contacts and can be mapped to HubSpot contact properties. We capture the form name, submission date, and field responses as custom text properties or consolidated JSON on the contact record, ensuring historical form data remains accessible for reporting and follow-up workflows.

Ontraport owners (users assigned to contacts, companies, and deals) are resolved in HubSpot by email match. If an Ontraport owner email matches a HubSpot user email, records assign to that user. Unmatched owners are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback owner.