Migrate from Ortto to HighLevel

Ortto People migrate as GoHighLevel Contacts. Standard fields (first name, last name, email, phone, location) map directly. Custom fields up to 100 per Person transfer to GoHighLevel Contact custom fields, with aggregate field types flagged during discovery (these are not creatable via Ortto API and must be recreated manually). Lifecycle stage and source attribution migrate as custom fields on the Contact since GoHighLevel uses pipeline stages rather than lifecycle properties.

Ortto Accounts (formerly Organizations) map directly to GoHighLevel Companies. Up to 3,000 people can link per Account in Ortto; GoHighLevel Companies support equivalent linking. Custom fields up to 25 per Account transfer to GoHighLevel Company custom fields. Fields exceeding GoHighLevel's type restrictions (multi-select picklist options, date format constraints) are converted to text fields during migration with a notation for the customer's admin to reconfigure post-migration.

Tags are first-class API objects in Ortto and migrate as flat string tags attached to the corresponding GoHighLevel Contact. Hierarchical or nested tag structures in Ortto are flattened into a dot-separated string format (e.g., segment.premium.vip) so that the full taxonomy is preserved in the tag label even when the nested structure itself cannot map natively. Tag assignments per person are resolved before Contact insert.

Ortto Audiences (dynamic or static segments of People) are converted into GoHighLevel filter rules and applied as Smart List criteria or tag-based segments. We export the audience definition (rule logic, conditions, and time-based triggers) as written documentation alongside the migration so the customer's admin can configure equivalent filters in GoHighLevel. Active audience memberships are applied as tags at migration time.

Ortto Activities (email opens, clicks, form submissions, custom events, and all behavioral events) migrate into GoHighLevel's activity history attached to each Contact. The Ortto Activity API returns up to 100 records per feed view, requiring pagination through all activity pages. We preserve the original activity timestamp, event type, and metadata (e.g., email subject, link clicked, form name) in GoHighLevel activity entries. Large activity histories require batched import with rate-limit handling on both platforms.

Ortto Campaigns (email, SMS, push) migrate as campaign structures in GoHighLevel: subject lines, recipient segments (applied as tags or Smart Lists), content body, and campaign metadata transfer. Campaign template styling and visual layout require manual reconstruction in GoHighLevel's template builder. Any active scheduled campaigns must be paused in Ortto before migration and rescheduled in GoHighLevel post-import. Campaign performance history (open rates, click rates) does not migrate as historical analytics but is available as a reporting baseline.

Ortto People custom fields up to 100 per Person transfer to GoHighLevel Contact custom fields with equivalent field types (text, number, date, dropdown). Ortto aggregate field types (which cannot be created via API) are flagged during discovery for manual recreation in GoHighLevel after migration. We scan the full custom field schema before any data import and create all destination fields in GoHighLevel first to ensure the import runs cleanly.

Ortto capture widgets support up to 50 fields. We export field mappings and widget field configurations from Ortto's UI. Visual styling, layout, and behavioral settings (popup triggers, timing, animation) do not migrate because these are UI-layer configurations not accessible via Ortto's API. We deliver a field inventory with the widget name, field labels, field types, and submission action so the customer's team can reconstruct the visual form in GoHighLevel's form builder.