Migrate from InStream to HighLevel

InStream Contacts map to GoHighLevel Contacts with all standard fields transferred directly: first name, last name, email, phone, address, and social profile URLs. The live social profile enrichment data (profile photos, job titles, company sizes pulled from LinkedIn or Twitter at import time) does not migrate because it is linked to InStream's external API rather than stored as independent fields. We extract and map the social profile URLs as static text fields on the GoHighLevel Contact so that the social links remain accessible even without the enriched snapshot.

InStream Company records map to GoHighLevel Company records. The Company name, domain, address, phone, and industry fields transfer 1:1. Each GoHighLevel Contact that was linked to an InStream Company is re-linked via the Contact-Company relationship in GoHighLevel after both objects are loaded. We resolve parent-company relationships at migration time using the InStream company hierarchy if present.

InStream Deals map to GoHighLevel Opportunities. The deal name, value, currency, expected close date, and associated Contact and Company links transfer directly. Pipeline stages from InStream are free-text and not normalized, so we capture each stage's name and order position during discovery and map them to GoHighLevel Opportunity pipeline stages, creating the equivalent stages in GoHighLevel's pipeline configuration before migration. Loss reasons and win reasons stored as InStream custom deal properties migrate to GoHighLevel custom Opportunity fields.

InStream's single Kanban pipeline maps to a GoHighLevel Pipeline with the same stage names in the same order. We create the pipeline in GoHighLevel during the discovery phase before data migration begins. Each InStream stage name becomes a GoHighLevel stage, and probability values are assigned per stage to match the original deal flow. If the InStream account uses multiple named pipelines, each becomes a separate GoHighLevel Pipeline.

InStream Lists are static groupings of Contacts used for segmentation. These map to GoHighLevel Tags applied to Contact records. A Contact that belonged to three InStream Lists receives three corresponding Tags in GoHighLevel. The tag naming convention preserves the original List name. If a Contact was added to a List after a certain date, we can optionally apply a tag with a date suffix if the customer wants to preserve recency information.

InStream email history attached to Contacts migrates to GoHighLevel Contact activity timeline entries. Each email record carries the subject, body, direction (sent or received), timestamp, and associated Contact link. Emails stored as rich HTML are preserved as formatted content in GoHighLevel's activity feed. The sender or recipient email address is linked to the Contact record where a match exists.

InStream call logs migrate to GoHighLevel Contact activity timeline entries with call type. Call duration, disposition notes, timestamp, and whether the call was inbound or outbound transfer to GoHighLevel's activity record for the associated Contact. If a call recording URL is stored in InStream, we preserve it as a text link on the GoHighLevel activity entry.

InStream meeting records attached to Contacts migrate to GoHighLevel Contact activity entries with appointment type. Meeting title, date and time, attendees, location, and any notes transfer. If the meeting was linked to a Deal in InStream, we link the GoHighLevel activity entry to the corresponding Opportunity if the customer requests cross-object activity linking.

InStream task records (completed tasks, follow-ups, internal to-dos) attached to Contacts migrate to GoHighLevel Contact activity timeline entries. Task subject, status, due date, and outcome notes transfer. Open tasks from InStream are migrated as open tasks in GoHighLevel and can be reassigned to GoHighLevel users if the owner mapping is resolved.

InStream tags on Contacts map directly to GoHighLevel tags on Contact records. Each distinct InStream tag becomes a GoHighLevel tag. Tags are applied at the Contact level, and a single Contact can carry multiple tags. The tag vocabulary is preserved exactly as named in InStream. If InStream tags include compound names (e.g., priority-high, source-linkedin), we split and apply both the prefix and suffix as separate tags per the customer's preference.

InStream custom fields on Contacts, Companies, and Deals have no publicly documented API schema, so we extract field definitions from the InStream UI export during discovery. Each custom field is matched to an equivalent GoHighLevel custom field by data type and name. GoHighLevel custom fields are created in the UI before migration begins. Any InStream custom field that cannot be mapped to a GoHighLevel field type is flagged in the discovery report for the customer's admin to review and resolve.