Migrate from SalesPro CRM to HighLevel

SalesPro Contacts migrate to GoHighLevel Contacts with first_name, last_name, email, phone, and address fields mapped directly. The SalesPro company association (foreign key link to Company) maps to GoHighLevel's company_id field on the Contact record. We resolve the company reference by creating the GoHighLevel Company record first, then linking Contacts during import. SalesPro permission-based sharing flags have no GoHighLevel equivalent and are noted for admin configuration post-migration.

SalesPro Company records map to GoHighLevel Company records linked by company_name on the Contact. GoHighLevel's Contact object has both a company_name text field and a company_id lookup — we populate company_name directly during import and create a matching Company record so that the lookup resolves correctly. This preserves the SalesPro contact-to-company relationship without requiring the admin to manually re-link records post-migration.

SalesPro Events migrate to GoHighLevel Opportunities with event name as the opportunity name, event start and end dates mapped to the opportunity's date fields, group size as a custom field, and event type as the pipeline or stage. The SalesPro event-to-contact linkage migrates as a note on the Opportunity referencing the linked Contact. Event dates that represent booking windows map to GoHighLevel Opportunity custom date fields for timeline visibility.

BEO records in SalesPro are derived outputs from Events, not standalone database objects. We reconstruct them as GoHighLevel custom objects with fields for event reference, cost breakdown, timeline specifications, and BEO status. The event-BEO linkage is preserved as a text reference to the parent Opportunity name and date. Customers specify their preferred custom object name during scoping (e.g., BEO, Event Order, Venue Booking). This reconstruction is necessary because GoHighLevel has no native BEO object equivalent.

SalesPro Tasks migrate to GoHighLevel Tasks with subject, due date, status, and priority preserved. The assignee (hubspot_owner_id in SalesPro) maps to GoHighLevel User by email match. Email reminder flags migrate as GoHighLevel Task reminder settings. Completion status and completion timestamps transfer directly. Tasks without an assignee are assigned to the migrating user's GoHighLevel account during import and flagged for admin review.

SalesPro custom milestones tied to sales cycles or goal-based scenarios migrate to GoHighLevel Tasks with a milestone tag or as a custom multi-select field on the Opportunity. The customer chooses during scoping whether milestones should appear as separate Task records or as Opportunity custom fields. Milestone ordering and relative sequence are preserved in the task subject or custom field value.

SalesPro pipeline and stage configurations migrate to GoHighLevel Pipeline stages. We map stage names by exact match and preserve relative ordering. Custom stage names are created as GoHighLevel stage values before record migration begins. Stage probability values migrate as a custom numeric field if GoHighLevel's default stage probability does not match the SalesPro configuration.

SalesPro users are resolved by email address against GoHighLevel User accounts. We extract every distinct user referenced on Contacts, Events, Tasks, and Milestones and create a reconciliation list. The customer provisions any missing GoHighLevel Users before migration resumes. Role-based access flags from SalesPro are noted as a configuration item for GoHighLevel team permission sets post-migration.

SalesPro calendar entries migrate to GoHighLevel Appointments with start and end timestamps, resource assignments, and booking details preserved. The webhook-based API limitation in SalesPro means calendar data depends on the vendor-export response — we flag this during scoping so customers understand that calendar export completeness relies on SalesPro's delivery timeline. Booking-linked contacts and events are cross-referenced using the appointment's linked Contact and Event names.