Migrate from Reach to HighLevel

Reach Contacts map to GoHighLevel Contacts as the primary record. Because Reach does not publish its field schema, we capture all visible columns from the CSV export at extraction time and map each to either a GoHighLevel standard Contact field (First Name, Last Name, Email, Phone, Address) or a GoHighLevel Custom Field created to receive the Reach-specific property. We validate the full column set against the baseline Reach export and treat any column not matching a known standard as custom. Reach contact records may contain company data stored as a property; we split this into a separate GoHighLevel Company record and resolve the Contact-to-Company lookup at import time.

Reach's custom property model is not publicly documented. We discover custom fields at export time by comparing the full column set of the Reach CSV export against a baseline Contact export baseline. Each discovered custom property becomes a GoHighLevel Custom Field on the Contact object (or on a Custom Object if the data is entity-level rather than person-level). Field type mapping is inferred from Reach data patterns: text values become GoHighLevel text fields, numeric values become number fields, and date-like values become date fields. The customer confirms the intended field type during scoping validation.

Reach label or tagging data is extracted from any tag-equivalent column in the CSV export and applied as GoHighLevel Tags on the Contact record. GoHighLevel supports multiple tags per Contact with no tag limit documented at the standard tier. We handle comma-separated or multi-value tag cells in the Reach export by splitting and creating individual Tag records. Tags used for content classification in Reach's media workflows are preserved as-is for the customer to reassign in GoHighLevel's Tag Manager.

Reach stores playlist and screen management data tied to contacts or accounts, but the storage model is not documented. We extract any media-asset references visible in the Reach export (URLs, file names, playlist identifiers) as Note records or file Attachments in GoHighLevel linked via ContentDocumentLink to the nearest Contact. We do not migrate the actual media files programmatically because Reach provides no documented media export endpoint; the customer must export media assets manually from Reach and re-upload them to GoHighLevel or a linked storage service.

If Reach contact records contain company name or company-level properties, we split these into a GoHighLevel Company record. Multiple Reach contacts sharing the same company name are de-duplicated into a single Company record with the Contact-to-Company lookup resolved at import time. This applies only if confirmed company data is present in the Reach export; if Reach stores company data only as a flat contact property without separate entity tracking, we flag it during scoping so the customer can decide whether to create Company records or leave company data as a Contact custom field.

Reach Enterprise seat-license records (name, email, role status) map to GoHighLevel User records. We resolve by email match against the GoHighLevel destination account. Any Reach user without a matching GoHighLevel User is flagged in a reconciliation queue for the customer to provision before Contact import resumes, because GoHighLevel requires OwnerId references on records assigned to active Users.

No Deal or Opportunity object was identified in available Reach documentation or reviews. If the customer's Reach account contains deal-like records stored as contact properties or in a separate export category not discovered during initial research, we flag this during the discovery call and add it to the object mapping scope. In the standard Reach migration scenario, we do not provision Opportunities in GoHighLevel unless confirmed deal data exists.

Reach's export documentation makes no mention of activity history, call logs, or engagement timestamps. We do not migrate activity data unless a full column export confirms its presence in the Reach dataset. If the customer confirms activity records exist in Reach, we add Task, Event, and EmailMessage migration using GoHighLevel's API with standard field mapping (TaskSubtype for calls, ActivityDate for timestamp preservation).