Migrate from Ortto to HubSpot

Ortto people map 1:1 to HubSpot contacts. All standard fields (name, email, phone, job title, address) transfer directly. Owner resolution happens by email match against HubSpot users — any Ortto owner without a HubSpot counterpart is flagged before migration commits so your team can invite them or reassign.

Ortto organizations map to HubSpot companies. Parent-child organization hierarchies in Ortto transfer to HubSpot via the Parent Company field. HubSpot caps linked people per company at 3,000 — setups exceeding this limit require a secondary association strategy that we surface in the pre-migration plan.

Ortto supports up to 100 custom fields per person record. These map to HubSpot contact properties. Starter-tier HubSpot accounts cap at 50 custom properties — if your Ortto setup exceeds this, we identify the lowest-value fields for culling or map them to custom objects on higher tiers. Field type mapping covers text, number, date, boolean, single-select, and multi-select.

Ortto organizations support up to 25 custom fields. These map to HubSpot company properties. HubSpot company properties share a separate pool from contact properties, so the Starter-tier 50-property cap applies independently. Multi-select and single-select fields from Ortto map to HubSpot option-set properties with values preserved exactly as stored.

Ortto stores activities as structured records with type, timestamp, metadata, and source. These transfer to HubSpot's engagement timeline. HubSpot classifies activities by type (email, call, meeting, note) and surfaces them on the contact record. The original activity timestamp is preserved; HubSpot sets its own engagement metadata at import time. Activity-type metadata from Ortto (e.g., link-clicked URL, email subject) transfers to HubSpot's engagement notes field for reference.

Ortto tags are a flat key-value label system that can apply to people. HubSpot has no native equivalent to Ortto's tag model. We map flat tags to a multi-select HubSpot contact property. Ortto supports nested tag hierarchies (parent/child tag groups) — nested hierarchies are flattened during migration, with parent and child segments joined into a single label string. If your Ortto setup relies heavily on nested hierarchies, we surface this in the pre-migration plan for your admin to decide on consolidation strategy.

Ortto static lists of people map to HubSpot lists directly. HubSpot list membership is static by default, matching Ortto's behavior. Dynamic lists in Ortto (membership based on filter conditions) have no direct HubSpot equivalent — they are not migrated as live lists. We instead export the dynamic-list filter definitions as a reference document so your HubSpot admin can recreate the logic as HubSpot lists or smart lists.

Ortto campaigns (email, SMS, in-app) with audience and status metadata map to HubSpot campaigns. The campaign-type field in Ortto (e.g., email vs. SMS) does not have a HubSpot equivalent and is stored as a custom text field on the HubSpot campaign record. Campaign performance metrics (open rate, click rate) stored in Ortto are not transferred — HubSpot tracks its own campaign analytics independently after go-live.

Ortto has no native deal object, but deal-like data stored in custom fields on the person or organization record migrates to HubSpot deal properties. If your Ortto setup uses a custom object for deals, that maps to a HubSpot custom object or deal properties depending on your HubSpot tier. HubSpot's standard deal fields (name, amount, stage, close date, owner) are mapped first, then any deal-specific custom properties from Ortto are added as HubSpot deal custom properties.

Ortto Journeys and Playbooks are automation constructs (step-by-step logic, triggers, conditions, actions) that have no import path into HubSpot. They must be rebuilt. We export your Ortto journey definitions as JSON configuration files and produce a feature-parity comparison document mapping each Ortto trigger and action to its HubSpot Workflow or Sequence equivalent. Your HubSpot admin uses these documents to rebuild Journeys in HubSpot's automation layer after data migration completes.