Migrate from Freshsales to HubSpot

Freshsales Lead maps to HubSpot Contact. Unconverted Freshsales leads land as HubSpot contacts directly. The Freshsales lead_status field maps to HubSpot's hs_lead_status property via value-mapping. Original lead create date is preserved as a custom datetime field since HubSpot overwrites CreatedDate at import time.

One-to-one mapping. Freshsales contacts transfer as HubSpot contacts with name, email, phone, job title, and address fields preserved. The Freshsales lifecycle_stage property becomes a HubSpot custom property since HubSpot's native lifecycle_stage model differs. Freddy AI score migrates as a custom number property.

Freshsales Account maps to HubSpot Company. Company name, domain, industry, employee count, and annual revenue transfer directly as matching HubSpot properties. Freshsales parent_account_id maps to HubSpot's parent_company_id for hierarchy preservation between parent and subsidiary companies. N:N contact-to-account associations in Freshsales collapse to HubSpot's primary company association per contact, so each contact retains one primary company link in HubSpot.

Freshsales deal maps to HubSpot deal. Deal name, amount, close date, owner, and create date all transfer. Pipeline stages map via value-mapping to HubSpot deal stages — teams using multiple Freshsales pipelines should note that HubSpot Starter supports one pipeline; additional pipelines require Enterprise licensing.

Freshsales pipelines become HubSpot deal pipelines. When Freshsales has multiple pipelines, we map each to a separate HubSpot pipeline on Enterprise tier or consolidate into stages within a single pipeline on Starter/Professional tier. Stage ordering, probability percentages, and forecast categories transfer as deal stage metadata. Pipeline consolidation decisions are made during the discovery phase before migration mapping is finalized.

HubSpot has no direct equivalent to Freshsales lifecycle stage values. We create a custom lifecycle_stage property in HubSpot and migrate the original values as a pick-list. Stage-change history is preserved as a custom audit text field. Sales teams should rebuild stage-progression logic in HubSpot workflows after migration.

Freshsales call logs, emails, meetings, and notes attach to their parent contact record in HubSpot as engagements. Original timestamps, owners, and direction metadata (inbound/outbound for calls) are preserved during transfer. Meeting start/end times and duration transfer to HubSpot's meeting engagement record format, including location and invitee details where available.

Freshsales products migrate as HubSpot Products with name, description, and price preserved. Freshsales deal_products (quantity, discount, unit price) map to HubSpot deal line items linked to the deal record. Product associations between line items and the parent Product record are established during migration so HubSpot reporting can roll up product revenue. Bundled or composite product relationships require manual reconstruction in HubSpot's product bundles feature after migration.

Freshsales custom objects (Enterprise tier) map 1:1 to HubSpot custom objects (Professional/Enterprise tier). N:N associations between custom objects and standard objects in Freshsales require HubSpot custom associations, which we configure during migration. Custom object schemas must be reviewed for compatibility with HubSpot's custom object field type restrictions.

Freshsales file attachments on contacts, accounts, and deals re-upload to HubSpot Files and attach to the corresponding record. Files larger than 25MB are flagged before migration — teams should split or compress oversized files. Inline images embedded in Freshsales notes download and rehost during migration.