Migrate from Highrise to HighLevel

Highrise People map directly to GoHighLevel Contacts. We export People via the parties.xml API endpoint and map standard fields (name, email, phone, address, social links) to GoHighLevel's Contact fields. Custom fields on People are detected via the Highrise custom_field_subjects API and created as GoHighLevel Contact custom fields before import. The Highrise owner (sales rep) resolves to a GoHighLevel User by email match and populates the Contact owner field.

Highrise Companies are a distinct Party type alongside People and export via the same parties.xml API endpoint. We map Company name, domain, address, and phone to GoHighLevel Company fields. The Company-Contact association uses Highrise's party_id on People to link to the corresponding GoHighLevel Company record. If a Highrise Contact has no associated Company, it imports as a standalone GoHighLevel Contact without a Company link.

Highrise Deals map to GoHighLevel Opportunities. This is the most complex mapping because Highrise exports Deals as plain text (.txt) rather than CSV, and GoHighLevel Opportunities require a Pipeline assignment. We parse the TXT output to extract deal name, stage name, value, responsible user, and linked party. We create a GoHighLevel Pipeline (or multiple Pipelines if the customer uses multiple Highrise deal categories) before migration and map Highrise deal stages to GoHighLevel pipeline stages with probability percentages.

Highrise Cases (customer support or task tracking) do not have a direct GoHighLevel object equivalent. We map Cases to a dedicated GoHighLevel Pipeline with a separate stage set (Open, In Progress, Resolved, Closed) and create Opportunities for each Case with the Case title, status, and linked contact parsed from the Highrise TXT export. Any Case attachments or embedded content in TXT require manual review post-migration.

Highrise Tasks export cleanly via the tasks API and map to GoHighLevel Tasks. We preserve task title, due date, status (completed/open), priority, and the linked party reference. The assignee resolves to a GoHighLevel User by email match. Tasks without a due date import with no due date in GoHighLevel.

Highrise stores all Notes, Emails, and Comments as Recordings linked to People or Companies. Highrise exports these only as TXT, stripping HTML formatting from emails and losing inline image references. We parse the TXT output to extract the full text content, timestamp, author, and linked party, then create GoHighLevel Activity records. Email body content arrives as plain text in GoHighLevel rather than rich HTML. The author resolves to a GoHighLevel User by email where possible.

Highrise custom fields on People, Companies, and Deals are detected via the custom_field_subjects API endpoints. We create equivalent custom fields in GoHighLevel before migration, preserving the field label and data type (text, number, date, checkbox, dropdown). Highrise multi-checkbox custom fields map to GoHighLevel multi-select custom fields. GoHighLevel's custom field naming follows its own conventions, so we document the mapping in the handoff spreadsheet.

Highrise Tags are a flat label system applied to People, Companies, Deals, and Cases. We export all tag names and their associations (which records have which tags). In GoHighLevel, we create Tag records and link them to Contacts, Companies, and Opportunities using GoHighLevel's tag associations. The many-to-many relationship between records and tags is preserved.

Highrise Users are the internal team members who own records and are assigned to Deals. We export the full user roster including name and email. We match each Highrise user by email to an existing GoHighLevel User and populate the owner field on Contacts, Companies, and Opportunities. Any Highrise user without a matching GoHighLevel User goes to a reconciliation queue for the customer to provision before record import resumes.

Highrise stores SMS conversations linked to contacts via the API as part of a contact's recording history. We capture message text, timestamp, and direction (sent/received) and create GoHighLevel Activity records of type SMS. GoHighLevel's SMS requires its own LC Phone or Twilio integration to be active for delivery, but the content transfers. Threading context (which messages belong to which conversation) may not map cleanly and requires spot-check validation post-migration.