Migrate from Freshsales to HighLevel

Freshsales Contacts map directly to GoHighLevel Contacts. All standard fields (name, email, phone, address) and custom fields migrate 1:1. We resolve Account lookups from Freshsales before Contact import so that the relationship is satisfied at insert time. If the customer uses Freshsales Lead Status to track lead quality, we preserve that value in a custom field fs_lead_status__c for segmentation in GoHighLevel.

Freshsales Leads and Contacts are separate objects; GoHighLevel has only Contacts. We migrate Freshsales Leads as GoHighLevel Contacts, applying the lifecycle stage consolidation rule: Freshsales leads with lifecycle_stage of Subscriber, Marketing Qualified Lead, or Lead map to GoHighLevel Contact with lifecycle_stage = Visitor; leads that were further along map to the equivalent GoHighLevel lifecycle stage. We preserve the original Freshsales lifecycle stage in a custom field fs_original_lifecycle__c on the GoHighLevel Contact for audit and reporting continuity.

Freshsales Accounts map to GoHighLevel Companies. The Account name becomes the Company name, and domain from Account maps to the Website field as a dedupe key. We create Company records before Contact import to satisfy the relationship lookup at the moment of Contact insert.

Freshsales Deals map to GoHighLevel Opportunities. The pipeline stages in Freshsales become GoHighLevel pipeline stage names that must be pre-configured in the destination before migration; we map each Freshsales stage to its GoHighLevel equivalent by name. Deal amount, close date, owner, and custom deal fields migrate directly. Probability migrates to a custom Opportunity field since GoHighLevel does not have a native probability field on Opportunities.

Freshsales Products map to GoHighLevel Products. Product name, SKU, price, and description migrate. We flag CPQ-related records during scoping because Freshsales CPQ is plan-gated (1 license on Growth, more on Pro) and GoHighLevel has no native CPQ; if CPQ workflows are active, the customer should plan a separate quoting process rebuild.

Freshsales Tasks migrate as GoHighLevel Activities with task_type = TASK. Subject, status, priority, due date, assigned user, and notes migrate directly. Owner resolution happens via email match to GoHighLevel User records. If a GoHighLevel User does not exist for the original Freshsales owner, the activity is assigned to the migration admin for manual re-assignment post-migration.

Freshsales Events (including call logs) migrate as GoHighLevel Activities with task_type = CALL for call records and task_type = MEETING for meeting records. For call records, call duration and disposition migrate to custom fields. Call recordings require Enterprise API access in Freshsales and may not be accessible for export depending on the source plan tier.

Custom fields must be pre-created in GoHighLevel before migration begins. GoHighLevel locks each custom field to either Contact or Opportunity type at creation and this cannot be changed afterward. We audit every Freshsales custom field, determine its target object in GoHighLevel, and create the schema in GoHighLevel during the setup phase. A field type mismatch (e.g., mapping a Contact-level Freshsales field to an Opportunity-type GoHighLevel field) is caught in the test migration before production data is touched.

File attachments on Contacts, Accounts, and Deals migrate to GoHighLevel's attachment storage. We sample attachment sizes during scoping because both platforms have storage limits: Freshsales caps at 2-100GB per user depending on plan tier, and GoHighLevel storage limits vary by plan. We flag records with attachments that may exceed the destination plan's allowance.

Freshsales pipeline configurations (stage names, stage order, stage probabilities) map to GoHighLevel Pipelines and stage definitions. Each Freshsales pipeline becomes a GoHighLevel Pipeline with stage names matched to the destination configuration. We configure this during the GoHighLevel setup phase before migration so that Deal-to-Opportunity mapping targets the correct pipeline.