Migrate from Xapsys CRM to HighLevel

Xapsys Companies map to GoHighLevel Locations with a direct field-level mapping for company name, address components (street, city, postcode, country), and classification fields. The Location object serves as the account-level record in GoHighLevel. We import Locations first in all migrations so that Contact imports can resolve the location_id reference during insert.

Xapsys Contacts map to GoHighLevel Contacts with first name, last name, email, phone, and address fields transferring directly. GoHighLevel stores phone and email in a separate Contacts/PhoneEmail related table; we resolve the contact_id lookup during import so that multiple contact methods are correctly associated. Owner assignment maps via email match to the GoHighLevel User. The Xapsys parent Company reference resolves to the Location id that was created in the first import phase.

Xapsys Opportunities map to GoHighLevel Opportunities with deal name, amount, stage, expected close date, and description transferring directly. The pipeline assignment maps to a GoHighLevel pipeline that we configure during schema setup. Note that GoHighLevel's Opportunity object includes a native Stage field with pre-set values; we add any Xapsys custom stage names as Stage options in the destination pipeline configuration before import.

Xapsys's custom entity builder is the defining architectural challenge for this pair. GoHighLevel restricts custom fields to Contact and Opportunity objects with two distinct branches. We evaluate each Xapsys custom entity during schema discovery: entities that store person-level attributes (buyer type, referral source, birthday) become Contact custom fields; entities that store deal-level attributes (budget range, property type, timeline to close) become Opportunity custom fields. Entities that reference neither Contacts nor Opportunities directly, or that have relationships to other custom entities, have no clean GoHighLevel destination and are documented as unsupported with a data extraction in CSV for manual re-entry.

Xapsys pipeline stages are user-defined strings stored per deployment. GoHighLevel pipelines have Stage values configured per pipeline. We capture the complete stage list from Xapsys during discovery, create matching Stage options in the destination GoHighLevel pipeline, and produce a stage map that the customer validates before import. Stage ordering and probability percentages transfer as part of this configuration step.

Xapsys engagement notes (engagement type NOTE) migrate to GoHighLevel notes attached to the parent Contact or Opportunity record. GoHighLevel does not have a unified activity object; notes are stored in a separate table and linked by reference_id. We map note body, created date, and owner by resolving the contact_id or opportunity_id from the migration's parent lookup table. Activity ordering is preserved via the created date timestamp.

Xapsys task engagements map to GoHighLevel Tasks with task name, description, due date, status, and priority preserved. Owner assignment resolves by email match to the GoHighLevel User. GoHighLevel tasks display in the contact record timeline and in the task list view. We use the GoHighLevel API to create tasks with the resolved contact_id or opportunity_id as the reference_id, which is the most reliable path for activity timeline display.

Xapsys workflow rules — automated triggers, stage-change actions, and email sequences — are not exposed via any documented export endpoint. They do not migrate as code. We document every active Xapsys workflow during discovery: trigger type, conditions, actions, and active status. The output is a written workflow inventory that the customer's admin uses to rebuild each automation in GoHighLevel's visual workflow builder. Workflow rebuild is outside the data migration scope and is a separate engagement or admin task.

Xapsys classification tags and label values map to GoHighLevel Tags on Contact or Opportunity records depending on what entity they annotate. We extract the full set of unique tag names and values from Xapsys, then apply them to the matching GoHighLevel records during import. Tags with no clear semantic equivalent in GoHighLevel are flagged in the migration report for the customer's admin to consolidate or recategorise post-migration.