Migrate from GleanView to HighLevel

GatherView Contact records map directly to GoHighLevel Contact records via the bulk CSV import endpoint. Standard fields (First Name, Last Name, Email, Phone, Address, Owner) map 1:1. Custom fields on the Contact record in GatherView map to GoHighLevel Contact Custom Fields, which we pre-create in the destination sub-account before import. We deduplicate against the destination using email as the primary key. Rich-text notes attached to Contacts export as plain text in CSV and migrate as Contact notes in GoHighLevel.

GatherView Company records map to GoHighLevel Locations (Company object). The Company Name, Industry, Website, and Address fields map directly. Custom fields on the Company record become Location Custom Fields in GoHighLevel. We create all Locations before Contacts so that Contact-to-Location lookups are resolved at import time rather than in a second pass.

GatherView Lead records — which carry source, status, and owner but no separate qualification model — map to GoHighLevel Contacts. The Lead Status value from GatherView becomes a GoHighLevel Tag (e.g., tag:lead_status_new, tag:lead_status_qualified) so that sales reps can filter contacts by original lead origin without requiring a separate Lead object. If the customer uses a separate qualification model in GatherView, we discuss splitting Leads into Contacts and Opportunities during scoping.

GatherView Deals map to GoHighLevel Opportunities. The Deal Stage maps to the closest GoHighLevel Pipeline Stage by name and order; if GatherView uses custom stage names with no direct GoHighLevel equivalent, we flag the gap for the customer to configure in GoHighLevel before migration. Deal Amount, Close Date, Owner, and associated Contact and Company links migrate. Historical stage transitions in GatherView do not transfer as an audit trail in GoHighLevel unless GoHighLevel's native Pipeline Audit Log feature is enabled by the customer.

Each GatherView deal pipeline and its stages are documented and then recreated in GoHighLevel under Opportunities > Pipelines. The stage order, probability percentages, and stage-specific actions from GatherView are noted in the handoff document. GoHighLevel's Pipeline stage builder allows custom probabilities per stage; we map GatherView's probability assumptions to the closest GoHighLevel defaults and flag any custom probabilities for the customer to set.

GatherQuote Products (base prices, cost, margin, attributes, bundle components) export from CSV as flat rows. We extract Product Name, SKU, Description, and Base Price. For bundled products, we document the bundle structure in the handoff document since GoHighLevel does not have a native bundle concept; the customer rebuilds bundles as grouped Products or as a Custom Object with line items. Formula-derived pricing fields (cost-plus-markup, conditional pricing) are flagged as described in the gotchas section.

GatherView Quotes reference Products, Customers (Contacts/Companies), and pricing rules. We extract Quote headers (quote number, date, expiration, terms) and line items (product reference, quantity, unit price, discount) from CSV. These map to GoHighLevel Opportunities with line item records attached. Quote PDF attachments and proposal templates do not export from CSV; we document every linked quote template URL in the attachment manifest for manual re-upload or re-creation in GoHighLevel's document builder.

GatherView activities attached to Contacts or Deals export as rows in the activity CSV. We import these into GoHighLevel's Contact timeline as notes, calls, or meeting records. Multi-select or rich-text activity notes may require reformatting; we strip unsupported HTML tags during transform and flag any rich-text formatting anomalies. Large activity batches are chunked to avoid import timeouts.

Every GatherView custom field on Contacts, Companies, Deals, and Leads requires per-field mapping to GoHighLevel. GoHighLevel permanently assigns custom fields to either Contact or Opportunity objects — a field created on Contact cannot later be moved to Opportunity. We read the GatherView field schema from the CSV headers, map each field to the appropriate GoHighLevel custom field object, and present a field-mapping worksheet before migration begins. Any GatherView custom field with no GoHighLevel equivalent is flagged for manual recreation post-migration.