Migrate from Sales Journey to HighLevel

Sales Journey Contact records map directly to GoHighLevel Contact. We use email as the primary dedupe key during import. Standard fields (First Name, Last Name, Email, Phone, Address) migrate directly. Custom fields on the Contact record migrate to GoHighLevel Contact custom fields, which must be pre-created in the destination account before import. Tags on Sales Journey contacts migrate to GoHighLevel tags, preserved as a flat list per contact. The HubSpot source platform integrates with GoHighLevel; Sales Journey's export uses CSV or API depending on discovery findings.

Sales Journey Company records map to GoHighLevel Location. Location name, address, industry, and size fields migrate directly. We preserve the relationship between Companies and associated Contacts by resolving the Location ID at import time and assigning it to each Contact. Domain from the Company record maps to the Location's website field and can be used as a secondary dedupe key alongside contact email.

Sales Journey Deal records map to GoHighLevel Opportunities. Deal stage, deal value, owner assignment, close date, and associated company and contact links all migrate. Pipeline stage names in Sales Journey must map to GoHighLevel pipeline stages; we create a stage mapping table during scoping and submit it for customer review before migration begins. Closed-Won and Closed-Lost reasons map to GoHighLevel Opportunity custom fields if the destination account has them configured.

Sales Journey Lead records map to GoHighLevel Contact with lifecycle status preserved in a custom field or tag. GoHighLevel does not use a separate Lead object like Salesforce; unqualified prospects live as Contacts with a lifecycle status field or tag that the customer's admin configures. We preserve the original Sales Journey Lead status in a dedicated tag (e.g., lead_status_original) for segmentation and audit purposes.

Each Sales Journey pipeline stage maps to a GoHighLevel Pipeline Stage by name and order. We extract the complete stage list from Sales Journey during discovery, propose the GoHighLevel pipeline stage names (which the customer renames to match their current taxonomy), and configure stage probabilities in GoHighLevel before any Deal or Opportunity records load. Stage mapping is reviewed and approved before the migration phase begins.

Sales Journey call logs map to GoHighLevel Activity records with task type set to Call. Call duration, disposition, timestamp, and owner assignment migrate directly. We resolve the owner by email against GoHighLevel Users. Call notes migrate to the activity body field. If Sales Journey stores call recordings as file URLs, we migrate the URL as a custom field rather than re-uploading the file.

Sales Journey email engagement records map to GoHighLevel Activity entries with email metadata (subject, body, timestamp, direction) preserved. We place emails on the correct Contact record by resolving the contact email against the migrated Contact list. Engagement scoring or behavioral signals (open rates, link clicks) may not export cleanly from Sales Journey; we audit this during discovery and flag any missing engagement history in the scoping report.

Sales Journey meeting records map to GoHighLevel Calendar Events with start time, end time, location, and attendee list preserved. Attendees resolve to GoHighLevel Contacts by email. Meeting notes migrate to the event description or an associated activity note. We preserve the original timestamp for activity timeline ordering.

Sales Journey notes attached to Contacts, Companies, or Deals map to GoHighLevel Activity Notes on the appropriate record. Note content, author, and timestamp migrate directly. We resolve the author by email against GoHighLevel Users to maintain attribution.

Sales Journey owner assignments on Deals and Contacts export as user references (typically by email or internal ID). We resolve each source owner by email against GoHighLevel Users in the destination account. Owners without a matching GoHighLevel User go into a reconciliation queue for the customer's admin to provision before record import resumes. This step gates the Deal and Opportunity migration phase because owner assignment is required on those records in GoHighLevel.

Sales Journey custom fields on standard objects (Contacts, Companies, Deals) migrate to GoHighLevel custom fields of the equivalent type. We pre-create the destination custom fields during the schema phase, including field type matching (text, number, date, picklist, checkbox, multi-select), before any record import. Any custom field validation rules in Sales Journey must be communicated during scoping so we can apply equivalent logic or flags in GoHighLevel.

Sales Journey tags stored on Contacts, Companies, or Deals export as a flat tag list per record. Tags migrate directly to GoHighLevel tags without transformation. If Sales Journey uses a hierarchical tag taxonomy, we flatten it into a flat tag list and document the original hierarchy in the scoping report so the customer's admin can recreate groupings in GoHighLevel if needed.