Migrate from solve 360 to HighLevel

solve 360 Contacts map directly to GoHighLevel Contacts. All standard fields (name, email, phone, address) and user-defined custom fields carry over. We pre-create custom fields in GoHighLevel during schema design, classifying each as a Contact type field since GoHighLevel requires this designation before any data loads and does not permit switching afterward. The HubSpot-style relationship between Contact and Company resolves via the GoHighLevel contact-company link after both objects exist.

solve 360 Companies map to GoHighLevel Accounts. Company name, domain, address, and custom fields migrate. We create the Account first during migration so that Contact import can satisfy the company link relationship at insert time rather than as a post-import update.

solve 360 Tasks map to GoHighLevel Tasks with status, priority, due date, assignee, and time tracking preserved. Task assignment resolves by matching the source hubspot_owner_id or user reference to the GoHighLevel user mapped during the owner reconciliation phase. Time entries attached to tasks become duration or time-tracking custom fields on the task.

solve 360 Follow-ups are a distinct activity type tied to a contact or company. We map them to GoHighLevel Task records with an activity type indicator preserved in a custom field. The original timestamp becomes ActivityDate to maintain chronological ordering in the contact's timeline.

solve 360 Support Requests track issues end-to-end against a contact or company. We map these to GoHighLevel Cases with the request history (status transitions, descriptions, linked conversations) preserved as Case descriptions and activity timeline entries. Case Record Type is configured to represent the support workflow.

Time records attach to tasks, site notes, calls, and meetings with duration, date, billing flag, and parent object reference. We preserve time data in GoHighLevel as either custom time-tracking fields on the related task or as structured notes appended to the parent record, depending on the volume and whether the customer requires billing-level granularity.

solve 360 users are both system actors and assignment targets. We export the user list and match by email against GoHighLevel users. Any owner reference without a matching GoHighLevel user enters a reconciliation queue for the customer to provision before record import resumes. Orphaned assignments are flagged post-migration for admin resolution.

solve 360 user-defined custom fields on Contacts and Companies (text, number, date, selection types) migrate to GoHighLevel custom fields of equivalent type. We classify each field as Contact or Opportunity during schema design. GoHighLevel does not permit retroactive type switching, making pre-migration classification mandatory. We flag any unsupported field types and propose a compatible GoHighLevel equivalent.

solve 360 pipelines and their stages (names, order, probability) export as structured metadata. We recreate the pipeline in GoHighLevel Opportunities, creating stage values with matching order and probability percentages. The pipeline becomes the GoHighLevel sales pipeline kanban view.

solve 360 tags on contacts, companies, and other records export as a tag list and re-apply as GoHighLevel tags attached to the corresponding Contact or Account. Tag associations per record are preserved. We flag any tags that exceed GoHighLevel's tag length or character restrictions for manual review.

solve 360 workflow definitions encode logic specific to its automation engine. We export them as structured JSON metadata with trigger events, conditions, actions, and delay steps. These cannot be replayed in GoHighLevel's workflow builder. We deliver the complete workflow inventory as a reference document so the customer's admin or a GoHighLevel specialist can rebuild each workflow from scratch.