Migrate from Prospect CRM to HighLevel

Prospect CRM Contact records migrate to GoHighLevel Contact as a 1:1 mapping on standard fields (name, email, phone, address). RFM segmentation assignments (Recency, Frequency, Monetary classification labels stored as Prospect CRM-specific properties) migrate as a custom Contact field of type multi-select picklist or text, depending on the customer's chosen representation. We capture the original RFM label per contact and confirm the field type during scoping before schema creation.

Prospect CRM Company records map to GoHighLevel Contact's company name and address fields, with the company phone preserved on the primary Contact record. GoHighLevel does not have a standalone Company or Account object at the same level as Salesforce; the company context lives on the Contact record. We extract all associated Contact links from Prospect CRM and attach them to the migrated Contact records under the same company name, preserving the business-unit grouping.

Prospect CRM Deals migrate to GoHighLevel Opportunities with pipeline stage names preserved explicitly. Stage values (e.g., 'Awaiting Stock', 'Quoted') map to GoHighLevel pipeline stages that we configure before migration. Deal value, close date, owner, and any deal-level custom properties migrate to GoHighLevel Opportunity fields or custom Opportunity fields depending on the property type.

Prospect CRM's custom pipeline stages (including non-standard statuses like 'Awaiting Stock' or 'Quoted') require explicit GoHighLevel pipeline configuration. We capture stage name, stage order, and probability percentage from Prospect CRM and create equivalent GoHighLevel pipeline stages before the Deal migration. Stage IDs are not portable; the mapping is explicit and documented.

Prospect CRM's Problem Pipelines (tracking delivery issues, returns, complaints) is a non-standard CRM object with no direct GoHighLevel equivalent. We extract Problem records with their Status, Outcome, linked Customer, and description fields. During scoping, the customer chooses whether to map Problems to GoHighLevel Opportunities in a dedicated pipeline or to a GoHighLevel custom Object with its own fields and pipeline. We document the chosen mapping explicitly and configure the destination schema before any data moves.

Activity history including notes, calls, and tasks migrates as chronological GoHighLevel Activity records linked to the parent Contact or Opportunity. Activity type labels from Prospect CRM (note, call, task) map to GoHighLevel's activity type equivalents. We preserve the original timestamp on each activity record to maintain the chronological timeline. Emails linked to Deals or Contacts migrate as GoHighLevel Activity entries with the email content preserved.

Product catalog data including SKU, name, pricing, and description migrates to GoHighLevel Products. The stock-aware flag and live inventory linkage from Prospect CRM cannot be preserved because GoHighLevel does not have native live inventory integration; these values migrate as product notes or custom fields, and the customer re-establishes the inventory connection through a Zapier workflow or custom API integration post-migration.

Custom fields on Prospect CRM Contacts, Companies, and Deals migrate as GoHighLevel Contact custom fields or Opportunity custom fields. GoHighLevel enforces a critical distinction: a field created as a Contact custom field cannot be switched to an Opportunity field, or vice versa, after creation. We confirm the Contact vs Opportunity field split with the customer during scoping and create all custom fields in the correct type before any data loads. Field type mapping (dropdown, date, number, text) is preserved from Prospect CRM to ensure validation consistency.