Migrate from HighLevel to Freshsales

HighLevel Contacts migrate to Freshsales Contacts with standard field mapping for name, email, phone, address, and lifecycle stage. The hubspot_owner_id maps to Freshsales Owner via email match. We preserve all tags as a comma-delimited tag field and optionally as Freshsales Topics depending on the customer's segmentation strategy. Sub-account origin is recorded in a custom field gl_subaccount__c so that multi-sub-account migrations maintain client context.

HighLevel Companies map to Freshsales Accounts. The domain field from the Company record populates the Account Website. Account is created before Contact import so the lookup relationship is satisfied at insert time. We use Company name as the dedupe key to prevent duplicate Accounts during migration.

HighLevel Opportunities migrate to Freshsales Deals. The dealstage property maps to Freshsales Deal Stage, and HighLevel Pipeline assignment maps to a Freshsales Deal stage group that we configure before import. Closed-Won and Closed-Lost amounts and reasons map to Freshsales custom fields if configured. Amount, probability (if set in HighLevel), and expected close date transfer directly.

HighLevel Pipelines map to Freshsales Deal Stage groups. Each HighLevel Pipeline Stage becomes a Freshsales Deal Stage with its display name and probability percentage preserved. Stage ordering matches the source pipeline sequence. We configure the stage group in Freshsales before Deal migration begins.

HighLevel Custom Objects migrate to Freshsales custom objects created via Freshsales's custom field builder. We introspect the HighLevel Custom Object schema (field names, data types, relationships) during discovery, pre-create the equivalent Freshsales custom object with matching field types and lookup relationships to Contact and Account, then import the records via Freshsales's API. Custom object data is imported last in the migration sequence to satisfy any cross-object lookups.

HighLevel tags migrate as a comma-delimited tag field on Contact (and optionally on Account and Deal). If the customer uses tags for content classification or routing, we migrate them as Freshsales Topics with TopicAssignment records linked to the relevant object. The customer chooses tag strategy during scoping based on how Freshsales's reporting will use the segmentation data.

HighLevel email engagements migrate to Freshsales Activity records with type set to Email. The email body, subject, timestamp, and associated contact link transfer. We resolve the Freshsales Contact reference using the email address mapping before insert.

HighLevel call engagements migrate to Freshsales Activity records with type set to Call. Call disposition, duration, and recording URL (if available) transfer to custom Activity fields. Activity timestamp preserves the original HighLevel call time for timeline ordering.

HighLevel meeting engagements migrate to Freshsales Activity records with type set to Meeting. Date, duration, and location transfer. The associated contact link resolves via email address match to the migrated Freshsales Contact.

HighLevel note engagements migrate to Freshsales Note records linked to the parent Contact, Account, or Deal via the object reference. Note body transfers as plain text with timestamp preserved. Notes are imported after the parent record exists in Freshsales.

HighLevel Task engagements migrate to Freshsales Tasks with Status, Priority, and due date preserved. Assignment maps from hubspot_owner_id to Freshsales OwnerId via email match. Completed status and completion timestamp transfer directly.

HighLevel Users referenced on Contact, Company, Opportunity, and Engagement records map to Freshsales Users by email address match. Any HighLevel User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before final import. This step gates the Contact and Deal migration phases.