Migrate from Soffront to HighLevel

Soffront Contacts map directly to GoHighLevel Contacts. We map standard fields (name, email, phone, address) and preserve lifecycle stage, group assignments, and tags as GoHighLevel Contact Tags or custom fields. The dedupe key is email address. Group membership from Soffront maps to GoHighLevel Contact Tags or a custom multi-select field depending on the customer's segmentation preferences established during scoping.

Soffront Accounts (companies) map to GoHighLevel Companies. The Account name becomes the Company name, and industry, size, and custom properties map to GoHighLevel Company custom fields. The Company-Contact relationship is preserved; we create the Company first so that the Contact import can reference it via the primaryCompanyId field.

Soffront Deals map to GoHighLevel Opportunities with pipeline stages mapped to GoHighLevel pipeline stages. Stage names and probabilities are value-mapped during scoping because Soffront pipeline stages vary by instance. Deal amount, close date, owner, and custom properties migrate to GoHighLevel Opportunity fields and custom fields. The pipeline assignment resolves to a GoHighLevel pipeline created during schema design.

Soffront Activities (calls, emails, meetings, tasks) map to GoHighLevel Tasks and Calendar Events. Activity type labels require mapping to GoHighLevel's activity type taxonomy. We set the activity timestamp to preserve the timeline ordering. Owner resolution uses email match against GoHighLevel Users. Activity notes migrate to the Task body field. GoHighLevel does not have a native engagement timeline like some CRM platforms; activities appear as Tasks in the Contact or Opportunity record.

Soffront Projects include status, milestones, assigned managers, resources, and due dates. GoHighLevel does not have a native Project object. We map Projects to a GoHighLevel Custom Object called Projects with custom fields for status, milestone tracking, manager assignment, and due date. If the customer uses Projects extensively, we pre-create the Custom Object schema during the schema design phase before data migration.

Soffront Tickets flow through capture, assignment, escalation, and resolution with conversation history. GoHighLevel handles support tickets via Opportunities in a dedicated support pipeline or via a Custom Object (Support Ticket) depending on the customer's volume and workflow needs. We establish the ticket pipeline or Custom Object during scoping. Conversation history migrates as notes or custom text fields on the ticket record. Ticket status and priority map to GoHighLevel pipeline stage and a priority custom field.

Soffront Knowledge Base articles with category assignments and ticket-type links do not migrate as structured content. We export the article list, categories, and ticket-type associations during discovery and deliver a written Knowledge Base inventory document. GoHighLevel has a separate Knowledge Base product that must be configured manually or by a GoHighLevel-certified agency. We do not recreate articles in GoHighLevel as part of standard migration scope; the customer's admin uses the inventory to recreate articles in the GoHighLevel Knowledge Base.

Soffront Custom Objects (beyond the standard data model) map to GoHighLevel Custom Objects of matching API names. GoHighLevel requires Custom Objects to be pre-created in the UI before any data can be imported via API. We inspect the Soffront custom object schema during discovery, define the GoHighLevel Custom Object schema (fields, types, lookups) during schema design, and create the Custom Object in GoHighLevel before migrating any records. Lookup relationships to standard objects (Contact, Company, Opportunity) are resolved at migration time.

Soffront's customization-first design means custom field names and picklist values vary between Soffront instances. We perform a field inventory during discovery that pairs each Soffront custom field to a GoHighLevel custom field of the equivalent type (text, number, date, picklist, checkbox). GoHighLevel uses an object selector at the top of the Custom Fields page to switch between supported objects, which we navigate during schema design. Picklist values require explicit value mapping before import.

Soffront Groups organize records for access control and segmentation. GoHighLevel uses Contact Tags and a sharing model based on Location and User roles. We map Soffront group memberships to GoHighLevel Contact Tags or a custom group-assignment field. If the customer relies on Soffront's access-control groups for data segmentation, we document the mapping and the customer configures GoHighLevel's Location-based access during post-migration setup.