Migrate from HubSpot to Freshsales

HubSpot uses a single Contact object with Lifecycle Stage to represent both unqualified prospects and customers. Freshsales separates Leads (unqualified prospects) from Contacts (qualified buyers linked to Accounts). We split at the Sales Qualified Lead boundary during migration: HubSpot contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead become Freshsales Lead records; stages of sales qualified lead, opportunity, customer, or evangelist become Freshsales Contact records linked to an Account. The original HubSpot Lifecycle Stage value is preserved in a custom field on both the Lead and Contact for reporting continuity.

HubSpot Company records map directly to Freshsales Account. The HubSpot company domain becomes the Account website field and is used as the deduplication key during import. Account is created before any Contact import so the Account-Contact lookup relationship is satisfied at the moment of Contact insert. Custom HubSpot company properties map to Freshsales Account custom fields with equivalent data types.

HubSpot Deals map directly to Freshsales Deals with identical field names in most cases. Deal stage, amount, close date, owner, and probability migrate directly. If the customer uses multiple HubSpot pipelines, each maps to a Freshsales pipeline and stage set; Freshsales supports unlimited pipelines from Growth tier, removing HubSpot's Starter one-pipeline and Professional fifteen-pipeline limits.

HubSpot pipeline configurations (stages, probabilities, active/inactive status) map to Freshsales pipeline configurations. Freshsales allows unlimited pipelines at all paid tiers, so a customer moving from HubSpot Starter (one pipeline) or Professional (up to fifteen) gains additional flexibility. We preserve stage names, probability percentages, and display order during configuration migration.

HubSpot Products map directly to Freshsales Products. Product name, SKU, description, and price migrate. If HubSpot Line Items are used, these map to Freshsales Deal-Product associations with quantity and unit price preserved.

HubSpot Owners map to Freshsales Users via email matching. We extract every distinct owner referenced on Contact, Company, and Deal records and cross-reference against Freshsales User emails. Any HubSpot Owner without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision the corresponding Freshsales user before record import resumes.

HubSpot call engagements map to Freshsales Call records. Duration, disposition, direction (inbound/outbound), and recording URL transfer to Freshsales Call fields. The Call is linked to the parent Contact or Lead record using the resolved record ID. Note that Freshsales assigns new calling numbers to the team; existing HubSpot calling numbers do not port and reps will need to provision Freshsales dialer numbers or port existing numbers separately.

HubSpot email engagements map to Freshsales Email records with status (sent, open, click, bounce), subject, body, and timestamp preserved. Emails are linked to the parent Contact, Lead, Account, or Deal using Freshsales record associations. If Freshsales does not support native email logging in the customer's plan, emails migrate as Notes with an email type marker and full metadata preserved.

HubSpot meeting engagements map to Freshsales Meeting records with title, start time, end time, location, and description preserved. Meeting attendees map to Freshsales contact or lead associations. The original HubSpot timestamp is preserved as the meeting start time in Freshsales.

HubSpot Task engagements map to Freshsales Task records. Title, description, due date, status, priority, and owner migrate directly. Task is linked to the parent Contact, Lead, Account, or Deal using Freshsales association fields.

HubSpot notes migrate to Freshsales Note records with full rich-text body preserved. File attachments associated with HubSpot notes migrate as Freshsales attachment records and are linked to the parent Contact, Lead, Account, or Deal. We handle the attachment transfer separately using the Freshsales file attachment API.

HubSpot custom objects (available on Enterprise tier) migrate to Freshsales custom modules. Freshsales allows custom objects (called custom modules) on Pro and Enterprise tiers. We pre-create the destination schema in Freshsales before importing any custom object records, including all custom fields, field types, and any lookup relationships to standard objects. Custom object data migrates last in the dependency order since custom object records often reference standard object records as parents.