Migrate from Sellsation CRM to HighLevel

Sellsation Customers (account-level records) map to GoHighLevel Company records. We preserve all standard address fields, the customer name, and any linked location metadata extracted from the geo map feature. GoHighLevel does not require a mandatory Company for a Contact, but we create Company records first to satisfy any Contact-to-Company lookups used in the customer's Sellsation data model. Customer unique identifiers are stored in a custom field for audit trail.

Sellsation Contact Persons map directly to GoHighLevel Contacts. The Contact Person's link to its parent Customer becomes the GoHighLevel Contact's Company lookup. We map standard fields: first name, last name, email, phone, and any custom fields enumerated during scoping. UTF-8 encoding is validated on all text fields before import to handle any accented characters in the source data.

Sellsation Sales Projects map to GoHighLevel Opportunities. The Sales Project pipeline stages map to GoHighLevel pipeline stages, which we configure before migration. Deal value, expected close date, and any automated potential analysis fields migrate as custom fields on the Opportunity. Stage change history migrates as Activity records with descriptive notes rather than native stage history because GoHighLevel does not preserve stage change timestamps as a standard object.

Sellsation call activity records map to GoHighLevel Tasks with call subtype. Call duration, disposition notes, and user assignment migrate as custom Task fields. We batch calls by time window (typically 90-day periods) to manage export file size since active accounts with years of calling history can generate tens of thousands of records. The parent Contact lookup resolves at migration time using the Sellsation Contact Person ID stored in our staging table.

Sellsation appointment records map to GoHighLevel Calendar Events. Start time, end time, location, and attendee list migrate directly. Attendees resolve to GoHighLevel Contact records by email match. Appointment notes migrate as Activity notes attached to the event. Time zone handling is validated during scoping since Sellsation's Austrian-market time zone assumptions may differ from the customer's current timezone configuration in GoHighLevel.

Sellsation note activities map to GoHighLevel Notes attached to the parent Contact or Opportunity. Note text migrates as plain text; any formatted content is preserved where GoHighLevel's note field allows. We resolve the parent record by matching the Sellsation Contact Person or Sales Project ID stored in our staging lookup table.

Sellsation Tasks map to GoHighLevel Tasks with Status, Priority, and due date preserved. Task assignment migrates by resolving the assigned user email to a GoHighLevel user account. Tasks linked to Contact Persons resolve to the corresponding GoHighLevel Contact lookup. Tasks without an assignable user are flagged for the customer's admin to map before production migration.

Sellsation custom fields on Customers, Contact Persons, and Sales Projects map to GoHighLevel Contact Custom Fields, Company Custom Fields, and Opportunity Custom Fields respectively. We enumerate all custom fields during scoping, flag any with picklist dependencies or formula-based logic that may not export cleanly, and create matching custom field definitions in GoHighLevel before data import. Custom field type mapping (text, number, date, picklist) is validated against GoHighLevel's supported field types.

Sellsation's geo map and territory heatmap data stores internal map state rather than standard geographic coordinates. We extract the linked Sales Project location data as standard address fields (street, city, postal code, country) so the geographic context is preserved in GoHighLevel. The native heatmap visualization cannot be replicated because GoHighLevel does not have a comparable territory heatmap feature. We document the source heatmap data structure in the migration deliverable so the customer can evaluate third-party mapping tools if territory visualization is business-critical.