Migrate from Streak to HighLevel

Streak's Box is the primary CRM record wrapping an email thread with custom fields, stage, owner, and tasks. We map Box to GoHighLevel Opportunity. The Box name becomes Opportunity name, stage becomes pipeline stage, owner resolves by email to a GoHighLevel User, and all custom Box properties map to Opportunity custom fields. The original Gmail thread ID is preserved in a custom field streak_thread_id__c for audit reference. Archive status and Box notes migrate as Opportunity notes.

Streak Contacts pulled from Gmail map to GoHighLevel Contacts by email. Name, email address, phone, company affiliation, and custom contact properties transfer directly. Gmail contact associations are preserved as metadata but do not re-create the email thread in GoHighLevel. We deduplicate by email address on import.

Streak Pipelines define the workflow stages a Box moves through. Each Streak Pipeline maps to a GoHighLevel Pipeline. Stage names, ordering, and any stage-level metadata transfer. If the destination GoHighLevel account has fewer pre-configured pipeline stages than the Streak source, we map by position — the first Streak stage maps to the first GoHighLevel stage, and so on. We flag any stage-level fields that require a custom Opportunity field in GoHighLevel.

Streak Stages within a Pipeline are ordered steps. We map stage names and order to GoHighLevel pipeline stage names. Stage probabilities from Streak (where available on Pro+) transfer to GoHighLevel stage probability settings. Closed-Lost and Closed-Won stage flags map to the corresponding GoHighLevel stage status.

Streak Tags are flat labels applied to Boxes for filtering. We preserve all tag names and associations as GoHighLevel Tags on the Contact or Opportunity record. Tags with no attached Boxes are included as empty tag lists for reconstruction in GoHighLevel. GoHighLevel applies tags across contacts, opportunities, and other records, matching Streak's flat tagging model.

Streak Tasks are Box-level action items with assignees and due dates. They are flat — no subtasks or dependencies. We map them to GoHighLevel Tasks linked to the parent Opportunity. Due date, assignee (resolved by email to GoHighLevel User), task body, and completion status transfer. Open tasks are imported as pending; completed tasks retain their completed status with the original completion timestamp.

Streak Mail Merge Campaigns store recipient lists, email templates, send history, and open/reply tracking. We export campaign metadata and send logs including send date, open rate, and reply tracking. GoHighLevel has no direct equivalent of Streak's Gmail-bound mail merge model; the closest GoHighLevel feature is a Workflow with email action steps. We deliver a written inventory of every Streak Mail Merge Campaign with its recipient filter, send cadence, template content, and recommended GoHighLevel Workflow equivalent for your team to rebuild.

Streak Snippets are templated email text blocks with merge variables. We export snippet content and merge variable syntax. Variable naming conventions differ between Streak and GoHighLevel, so we document each snippet's fields, variable names, and body content for reconstruction as GoHighLevel Email Templates or within Workflow email actions. Snippet merge variable mapping is included in the handoff document.

Streak custom properties added to Boxes (dropdowns, text fields, dates, numbers, checkboxes) vary per pipeline and per Box. We discover the full property schema per pipeline during the schema audit. Each custom property maps to a GoHighLevel Opportunity custom field of equivalent type. Contact-level custom properties map to GoHighLevel Contact custom fields. We handle type conversion — Streak dropdowns become GoHighLevel dropdowns, Streak checkboxes become GoHighLevel checkboxes, and so on.

Streak User records include email, name, role, and permissions level. We map users to GoHighLevel Users by email. Shared pipeline access depends on Streak Pro tier or above. Enterprise-tier custom roles and data validation rules have no direct GoHighLevel equivalent; we extract the role definitions and map them to GoHighLevel's team roles and access model, flagging any granular permission rules that cannot be represented in GoHighLevel.

File attachments stored inside Box threads are referenced by Gmail file ID. We export the file URL, filename, size, and attachment date. File content download requires the source Gmail account to remain active and accessible. We flag any Box records with attachments and document the file inventory separately for manual upload or Dropbox/Google Drive re-link in GoHighLevel.