Migrate from BenchmarkONE to HighLevel

BenchmarkONE Contact records map directly to GoHighLevel Contact records. Standard fields — First Name, Last Name, Email, Phone, Address, Title, Company — map 1:1. The BenchmarkONE Temperature field (Cold/Warm/Hot lead scoring) has no native GHL equivalent; we create a custom picklist field temperature__c on the Contact object during migration setup and map each Temperature value accordingly. Contact Status, Lead Source, and Opt-in Status map to GHL built-in or custom fields.

BenchmarkONE Companies are stored as a separate entity linked to Contacts via Account Company ID. GoHighLevel does not have a standalone Company object — company information lives as fields on the Contact record (Company Name, Website, Address). We extract Company Name and Website from the BenchmarkONE Company export and populate the corresponding fields on the primary Contact record. The Company-to-Contact relationship does not require a separate import in GHL.

BenchmarkONE Deals map to GoHighLevel Opportunities. The HubSpot Sales Hub migration reference maps Deals to Opportunities, and the same 1:1 logic applies here. We configure the GHL pipeline and stage structure before migration so that dealstage values resolve to valid GHL Opportunity stage values. Closed-Won and Closed-Lost reasons from BenchmarkONE custom fields map to custom Opportunity fields.

BenchmarkONE pipelines and their associated stages migrate as GHL Pipelines and Stage definitions. We create the destination pipeline structure in GHL before any Opportunity import so that stage values are valid at insert time. Stage probability percentages from BenchmarkONE transfer to GHL stage configuration.

BenchmarkONE Tasks linked to Contacts, Companies, or Deals map to GHL Tasks. Due date, status, priority, and assignee fields transfer directly. Task associations resolve to the migrated Contact or Opportunity ID. Note that GHL Tasks appear on the contact timeline and in the Tasks view; there is no separate Tasks object as a top-level record type in GHL's data model.

BenchmarkONE tags (stored as comma-separated values in the CSV export) map directly to GoHighLevel Tags. Multiple tags per contact are supported in both systems. Tags used for segmentation in BenchmarkONE become GHL Tags that can be used in SmartLists, Workflow triggers, and contact filtering. We preserve tag names verbatim and deduplicate if the same tag name appears under different capitalizations.

BenchmarkONE custom fields on Contacts and Companies (text, number, date, dropdown, checkbox types) map to GoHighLevel Contact custom fields. We audit field types during scoping — GHL custom fields support text, number, date, dropdown, multi-select, phone, and URL types. Custom field schemas must be pre-created in GHL before import. Multi-select or checkbox fields in BenchmarkONE require conversion to GHL multi-select or checkbox fields.

BenchmarkONE stores social profile URLs (LinkedIn, Twitter, Facebook, etc.) on Contact records. These map to GHL built-in social profile URL fields if available, or to custom URL fields on the Contact object. We extract each social profile URL from the BenchmarkONE export and populate the corresponding field.

BenchmarkONE stores campaign metadata (name, send date, audience, template) and aggregate performance stats (opens, clicks). Individual email event logs may require a separate export. Campaign metadata migrates as GHL Campaigns or as a custom object depending on the customer's reporting needs. Aggregate open rates and click rates transfer as custom fields on the campaign record. BenchmarkONE email templates are HTML and require manual upload to GHL's email template builder; we do not migrate template code directly.

BenchmarkONE Users (assigned as owners to Contacts, Companies, Deals, and Tasks) map to GoHighLevel Users. We resolve owners by email match against the GHL User table. Users without a matching GHL User account go to a reconciliation queue for the customer to provision before record import continues. BenchmarkONE's unlimited user seats mean the owner count is typically low, simplifying the reconciliation step.