Migrate from OnePageCRM to HighLevel

OnePageCRM contact persons map to GoHighLevel contacts with full field parity on name, email (primary phone for deduplication), phone, address, and social URLs. Custom contact fields from OnePageCRM require pre-creation in GoHighLevel before import. We preserve the Next Action date as a custom field next_action_date__c and the Next Action text as a custom field next_action_text__c, then create a corresponding task with that due date during migration. The OnePageCRM contact-to-organization linkage resolves to a Company lookup in GoHighLevel using the Organization name as the matching key.

OnePageCRM organization records map to GoHighLevel Company objects. Fields including company name, phone, address, and custom company fields migrate with full parity. Custom company fields must be pre-created in GoHighLevel before the organization batch loads. We resolve the Organization ID as a reference field org_id__c for traceability back to the source record.

OnePageCRM's flat model links contacts to organizations via a simple association. In GoHighLevel, each Contact has a required Company lookup field. We resolve this relationship by matching the OnePageCRM contact's Organization name to a GoHighLevel Company record created during the organization import phase. Records where the Organization name is blank are loaded as contacts without a Company association and flagged for manual linking.

OnePageCRM deals map to GoHighLevel opportunities with name, amount, stage, close date, margin, commission, and cost preserved. Multi-month deal flags migrate as custom opportunity fields. Closed-won and closed-lost status from OnePageCRM maps to GoHighLevel pipeline stage values, with the original close reason preserved in a custom field. Deal ID is retained as deal_id__c for audit.

OnePageCRM predefined items (products and services used in deal creation) map to GoHighLevel products. We preserve item name, price, quantity, grouping (category), and description. Products are imported before deals so that line items can reference the product lookup at migration time. SKU and grouping information from OnePageCRM become custom product fields in GoHighLevel.

OnePageCRM tags assigned to contacts and deals migrate as GoHighLevel tags. The flat tag namespace is preserved without flattening. Tags used for deal-level categorization map to opportunity tags in GoHighLevel. We handle tag name normalization (lowercasing, removing special characters) to avoid GoHighLevel tag creation conflicts.

OnePageCRM lead source values (website inquiry, phone call, referral, etc.) classify how contacts entered the CRM. We map these to GoHighLevel custom contact fields (lead_source__c) or tags, depending on whether the customer wants to filter and segment by source in dashboards. We create the picklist or tag set based on the distinct values found in the source export.

OnePageCRM contact statuses (Prospect, Qualified, Customer, etc.) define where a contact sits in the sales pipeline. We capture the full status taxonomy and map each value to a corresponding GoHighLevel pipeline stage. The customer chooses the target pipeline during scoping. Status ordering and probability percentages migrate as pipeline configuration.

Notes and call logs attached to contacts in OnePageCRM export as plain text in the contact dataset. We migrate these as GoHighLevel contact notes or activity log entries on the contact timeline. Call duration and disposition from OnePageCRM call logs migrate as custom activity fields. Email body content and attachments cannot be exported from OnePageCRM natively and are flagged as a data gap; we attempt API-based extraction for individual contact records but note that conversation threads may be incomplete.

All OnePageCRM custom fields must be pre-created in GoHighLevel before data import. We provide a custom field checklist during scoping that maps each source field name, type, and options to the equivalent GoHighLevel field. Multi-select picklists, date fields, and numeric fields map with type parity. Fields that use unsupported GoHighLevel types (e.g., multi-relational lookups) are flagged for customer decision on field splitting or acceptance of data loss.