Migrate from XSale to HighLevel

XSale Rep records map to GoHighLevel Contact. The Rep's name, phone, email, and team assignment transfer to Contact's standard fields. We preserve the original XSale rep ID in a custom field xsale_rep_id__c for reconciliation and cross-reference. The Contact type is inferred from XSale rep_role if present; field reps map as Contact with a rep_type__c tag while manager-level reps receive an admin Contact designation.

XSale Routes map to a GoHighLevel Custom Object named Route. Each Route record carries the route name, assigned Rep(s), schedule (day of week, time window), geographic territory, and stop count. We create the Custom Object schema in GoHighLevel before migration, including custom fields for schedule_window__c, territory__c, and stop_count__c. Route is set as a lookup on the Contact record for rep routing context.

XSale Visit records split into GoHighLevel Task and Event records. Visits with a discrete check-in/check-out timestamp become Event records preserving StartDateTime and EndDateTime. Visits recorded as a single status update with no duration become Task records with ActivityDate set to the visit date. Location data from XSale visits migrates to custom fields visit_location__c and latitude_longitude__c. Each Activity record links to the Contact (Rep) and the Route Custom Object via WhatId.

XSale Orders map to GoHighLevel Opportunity. The order total, status, and associated customer account transfer to Opportunity fields (Amount, StageName, AccountId). We resolve the customer account by matching XSale order_customer_id against GoHighLevel Contact or Company records. Order line items map to Opportunity Products via the Price Book if the customer uses GoHighLevel's product catalog; otherwise line-item details migrate as custom fields on the Opportunity.

XSale Pre-order Transactions do not have a direct GoHighLevel equivalent. We model them as Opportunity records with a custom picklist field preorder_status__c set to Pre-order. The opportunity name carries the prefix PRE- for identification, stage defaults to a pre-sale stage configured during setup, and amount carries the pre-order value. Once fulfilled, the custom field updates to Fulfilled and the Opportunity moves through the standard pipeline.

XSale customer records map to GoHighLevel Company. The company name, address, phone, and website transfer to Company standard fields. Company is created before any Contact import so that Contact-Company lookups are satisfied at insert time. If XSale stores customer hierarchy (parent account, child accounts), the hierarchy replicates as multiple Company records with a parent_company_id__c custom field lookup.

XSale custom fields on Order and Visit objects require careful type planning against GoHighLevel's Contact versus Opportunity field distinction. Once a GoHighLevel custom field is created as Contact-type or Opportunity-type, it cannot be switched. We audit all XSale custom fields during discovery, categorize each as Contact-level (rep performance metrics, visit notes) or Opportunity-level (order-specific attributes, delivery confirmation flags), and create them with the correct object designation before data import begins.

XSale's rep-to-route assignment relationships do not map as a discrete object in GoHighLevel. We resolve these as Contact custom field assignments: each Contact (Rep) gets a multi-select picklist or lookup field linking to the Route Custom Object records they are assigned to. During migration we extract the assignment table from XSale, build the Contact-Route lookup records, and attach them to the relevant Contact. If assignments are date-ranged, we add effective_from__c and effective_to__c date fields to the Route Custom Object.