Migrate from ConSol to HighLevel

ConSol contacts migrate as HighLevel contacts. Name, email, phone, and address fields map directly. ConSol contact custom properties migrate as HighLevel custom fields. A contact's assigned technician in ConSol can be preserved as a custom text field or resolved by email match against HighLevel users. Duplicate detection runs during migration to prevent duplicate contact records based on email address.

ConSol company records migrate as HighLevel companies. Domain, address, industry, and employee count fields map directly. Companies without a ConSol contact are created as standalone HighLevel companies. Companies linked to multiple ConSol contacts get one primary contact assignment plus secondary contact relationships.

ConSol ticket history (incident records with status, priority, category, and description) migrates as HighLevel notes attached to the mapped contact. HighLevel has no native ticket object — ticket status and priority values are preserved as custom fields on the contact or in a dedicated 'Ticket History' custom object if you need to retain full ticket structure.

ConSol knowledge articles require a custom object in HighLevel to preserve title, content, category, and publication status. Articles can alternatively be stored as documents in HighLevel's file system and linked to relevant contacts or companies via custom fields. Searchable content fields are preserved for reference and training purposes.

ConSol technicians and users are matched to HighLevel users by email address. Unmatched technicians are flagged before migration — your team can invite them to HighLevel or reassign their ConSol records to a fallback HighLevel user before the migration runs.

ConSol custom objects (available in Enterprise editions) map 1:1 to HighLevel custom objects. Each custom object field type in ConSol maps to the equivalent HighLevel field type. N:N relationships in ConSol require junction objects in HighLevel — we flag these in the migration plan for pre-creation.

ConSol file attachments on tickets or contacts re-upload to HighLevel's file storage. File size limits apply (HighLevel's API enforces file size constraints per upload). Inline images in ConSol note content are extracted and re-hosted in HighLevel. All attachments retain their original filenames for traceability.

ConSol ticket status values (Open, In Progress, Pending, Resolved, Closed) map to a custom pick-list field in HighLevel on the contact record. Each ConSol status becomes a HighLevel pick-list value — value-by-value mapping is required if the source values differ from defaults.

ConSol ticket priority levels (Critical, High, Medium, Low) migrate as a custom pick-list field on HighLevel contacts. Priority values map directly unless ConSol uses non-standard labels, in which case value-by-value mapping handles the translation. Color coding for priority levels is preserved in the custom field configuration.

ConSol change management records (change requests with approval status, risk level, and implementation notes) migrate as notes on the related contact or as entries in a 'Change Management' custom object in HighLevel. Approval workflow logic does not transfer — rebuild required in HighLevel Workflows.

ConSol SLA definitions (response time, resolution time, business hours) have no native HighLevel equivalent. SLA metadata is preserved as text fields or notes on the contact for reference. SLA enforcement logic must be rebuilt using HighLevel Workflows and task automation.