Skip to content
Get a quote

Freshsales to HubSpot migration

Moving from Freshsales to HubSpot CRM is one of the most common SMB-to-mid-market CRM transitions we handle at FlitStack AI. We map every Freshsales object — leads, contacts, accounts, deals, pipeline stages, and Freddy AI scores — into HubSpot's contact lifecycle model, preserving original create dates, close dates, and owner assignments so your HubSpot reports reflect the full history from day one.

Short answer

FlitStack AI migrates contacts, companies, deals, pipelines and lifecycle_stages from Freshsales to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

By

Source Freshsales
DestinationHubSpot
ContactCompanyDealPipelinelifecycle_stage
Mapped field by field · sample run · one-click rollback

What moves from Freshsales to HubSpot?

Freshsales organizes its CRM around a Lead-Contact-Account-Opportunity model with a contact lifecycle stage property, deal pipelines with configurable stages, built-in Freddy AI scoring, and a product catalog with deal line items.

Read the full summary

HubSpot uses a unified Contact object with a lifecycle_stage property, deals with drag-and-drop pipeline stages, and a slightly different convention for product-to-deal linking via line items. FlitStack AI extracts Freshsales data via its REST API, normalizes field names and value pick-lists across all objects, maps lifecycle stages to HubSpot's lifecycle_stage property, preserves the product catalog as line items, and delivers a sample migration with field-level diff before the full run. Our migration engine handles owner resolution by email lookup, date-field preservation as custom properties, and deal stage value-mapping per pipeline. Workflows, sequences, and Freddy AI scoring models must be rebuilt in HubSpot — we export Freshsales workflow definitions as JSON and provide a rebuild reference document so your admin can reconstruct automation logic in HubSpot workflows and sequences after migration completes.

direct

Lead → Contact

Freshsales Lead maps to HubSpot Contact.

How it maps

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.

direct

Contact → Contact

One-to-one mapping. Freshsales contacts transfer as HubSpot contacts with name, email, phone, job title, and address fields preserved.

How it maps

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.

direct

Account → Company

Freshsales Account maps to HubSpot Company.

How it maps

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.

direct

Deal → Deal

Freshsales deal maps to HubSpot deal.

How it maps

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.

transformed

Pipeline → Pipeline (Deal)

Freshsales pipelines become HubSpot deal pipelines.

How it maps

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.

custom_field_required

Lifecycle Stage → lifecycle_stage (Custom Property)

HubSpot has no direct equivalent to Freshsales lifecycle stage values.

How it maps

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.

What moves10 objects
FreshsalesHubSpot
  • LeadContact1:1
  • ContactContact1:1
  • AccountCompany1:1
  • DealDeal1:1
  • PipelinePipelinetransformed
  • Lifecycle Stagelifecycle_stagetransformed

+ 4 more in the mapping below

How Freshsales and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionFreshsalesHubSpot
Data model for peopleFreshsales maintains separate Lead and Contact objects with lifecycle_stage on ContactHubSpot uses a single Contact object with lifecycle_stage and a separate Lead object for unqualified records
Pipeline stagesFreshsales supports multiple parallel pipelines with independent stage sets per pipelineHubSpot Sales Hub Starter supports one pipeline; additional pipelines require Enterprise tier
AI lead scoringFreddy AI contact scoring is available on Pro ($39/user/mo) and Enterprise plansHubSpot predictive lead scoring is a separate paid add-on not included in Starter tier
Deal product linkingFreshsales links products to deals via deal_products with quantity and discount per lineHubSpot links products via the Products object and line items on the deal record
Custom objectsFreshsales supports custom objects (Enterprise-only) with N:N relationships via appsHubSpot supports custom objects on Professional and Enterprise tiers with associations
File attachmentsFreshsales stores files up to 100GB per user on EnterpriseHubSpot enforces a 25MB per-file limit on file attachments during import
Reporting depthFreshsales reporting is curated dashboards and basic custom reports on Pro+HubSpot Reports provides drag-and-drop custom reports with filtering across all objects

Freshsales to HubSpot field mapping

The 30 most-used fields of 45 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
FreshsalesHubSpot
  1. firstnameContact firstnameContact
  2. lastnameContact lastnameContact
  3. emailContact emailContact
  4. phoneContact phoneContact
  5. mobilephoneContact mobilephoneContact
Freshsales fieldHubSpot fieldMappingNote
Contact.firstnameContact.firstnamedirect
Contact.lastnameContact.lastnamedirect
Contact.emailContact.emaildirect
Contact.phoneContact.phonedirect
Contact.mobilephoneContact.mobilephonedirect
Contact.job_titleContact.jobtitledirect
Contact.lifecycle_stageContact.lifecycle_stagecustom_field_requiredHubSpot has a native lifecycle_stage property but values differ per account. We preserve Freshsales lifecycle values as a custom property to maintain history and map HubSpot's native property for new records.
Contact.lead_statusContact.hs_lead_statusvalue_mappingFreshsales lead_status pick-list values map to HubSpot's hs_lead_status pick-list via value-by-value mapping. Custom lead statuses require pre-migration coordination with HubSpot admin.
Contact.ai_scoreContact.freddy_ai_scorecustom_field_requiredFreddy AI contact score migrates as a custom number field (freddy_ai_score__c). Scores outside the 0-100 range are capped; non-numeric values are stored as text and flagged for manual review.
Contact.owner_idContact.hubspot_owner_idtransformedOwner resolved by email lookup against HubSpot users. Unmatched owners are flagged before migration and assigned to a fallback owner specified by your team.
Contact.account_idContact.associatedcompanyidtransformedFreshsales account_id maps to HubSpot associatedcompanyid. The Company record must be migrated before contacts for the lookup to resolve.
Contact.created_atContact.original_create_datecustom_field_requiredHubSpot's CreatedDate is set at import time. Original Freshsales created_at preserved as a custom datetime field (original_create_date__c) for reporting continuity.
Contact.updated_atContact.original_update_datecustom_field_requiredOriginal last-modified timestamp preserved as a custom field for audit purposes.
Contact.fs_idContact.source_system_idcustom_field_requiredFreshsales internal ID stored on the HubSpot record for traceability and delta-run de-duplication.
Company.nameCompany.namedirect
Company.domainCompany.domaindirect
Company.industryCompany.industryvalue_mappingIndustry pick-list values mapped per value. Freshsales industry taxonomy differs from HubSpot — mismatched values default to 'OTHER' and are flagged for review.
Company.number_of_employeesCompany.numberofemployeesdirect
Company.annual_revenueCompany.annualrevenuedirect
Company.phoneCompany.phonedirect
Company.cityCompany.citydirect
Company.stateCompany.statedirect
Company.countryCompany.countrydirect
Company.zip_codeCompany.zipdirect
Company.parent_account_idCompany.parent_company_idtransformedFreshsales parent_account_id maps to HubSpot parent_company_id. Parent company must be migrated first; circular references are flagged during validation.
Deal.nameDeal.dealnamedirect
Deal.amountDeal.amountdirect
Deal.closedateDeal.closedatedirect
Deal.deal_stageDeal.dealstagevalue_mappingFreshsales deal stage values map to HubSpot deal stage values per pipeline. Stage probability and forecast category are re-applied from HubSpot's stage metadata.
Deal.pipeline_idDeal.pipelinetransformedFreshsales pipeline_id becomes HubSpot's pipeline field. Multiple Freshsales pipelines map to separate HubSpot pipelines (Enterprise) or are consolidated into stages within one pipeline.

What to watch for in a Freshsales to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Freddy AI contact scoring has no native HubSpot equivalent

Freshsales Freddy AI contact scoring generates a numeric score stored on the contact record.

How we handle it

HubSpot has no built-in AI scoring engine at the CRM level — predictive lead scoring requires a separate paid add-on on top of HubSpot's base subscription. We migrate the historical score as a custom number field (freddy_ai_score__c) so historical score data is preserved. However, the scoring model itself — which behaviors drive points up or down — must be rebuilt in HubSpot's workflow-based scoring or a third-party enrichment tool. This is a high-severity gotcha for teams whose sales process relies on Freddy AI to prioritize outreach.

high

Multiple Freshsales pipelines require HubSpot Enterprise licensing or pipeline consolidation

Freshsales supports multiple parallel deal pipelines with independent stage sets on the same account — a common configuration for teams managing different product lines or business units.

How we handle it

HubSpot Sales Hub Starter and Professional support one deal pipeline. Multiple pipelines require HubSpot Sales Hub Enterprise. We flag every Freshsales pipeline during the discovery phase. If your team uses more than one pipeline, either upgrade to HubSpot Enterprise before migration or consolidate pipelines into a single pipeline with grouped stages — each option affects the migration mapping and requires a decision before the migration runs.

high

Lifecycle stage migration preserves values but not progression logic

Freshsales lifecycle stages track how a contact progresses through the sales funnel — Subscriber, Lead, MQL, SQL, Customer, Evangelist.

How we handle it

HubSpot has its own lifecycle_stage property with a default set of values. We map Freshsales lifecycle values to a custom property, preserving the original values for each contact. However, the stage-transition triggers that advance contacts through stages in Freshsales (workflows, form submissions, email opens) do not migrate. Your team needs to rebuild lifecycle-progression logic in HubSpot workflows using enrollment criteria. Without this rebuild, contacts imported with a Customer lifecycle stage will not auto-advance on future activities.

medium

File attachments exceeding 25MB require pre-migration handling

Freshsales stores files up to 100GB per user on Enterprise tier.

How we handle it

HubSpot enforces a 25MB per-file limit on file attachments during import. We flag every Freshsales file attachment over 25MB before the migration runs. Options include splitting large files into smaller chunks, compressing images, or archiving oversized files to a linked storage URL referenced in a custom text field on the record. This is not automatic — teams need to decide on an archival strategy before migration day.

medium

Deal product line items require product catalog pre-setup in HubSpot

Freshsales links products to deals via deal_products with quantity, unit price, and discount per line.

How we handle it

HubSpot links products to deals through the Products object and line items. The Freshsales product catalog must exist as HubSpot Products before deal line items can link correctly. If products do not exist in HubSpot at migration time, deal line items land as orphaned text values. We create the product catalog in HubSpot as part of the migration plan — but product descriptions, pricing, and bundles require an admin review step before we can finalize the mapping.

How the migration runs

  1. Export and audit Freshsales data via API

    FlitStack AI connects to Freshsales via its REST API using scoped read credentials.

    What this step covers

    We export all standard objects (leads, contacts, accounts, deals, pipeline stages, products, activities) and any custom objects present on your account. During export, we run a data quality audit: flag duplicate contacts, identify missing required fields, and surface any field values that will not map cleanly to HubSpot's property types. This audit report goes to your team before the migration plan is finalized.

  2. Map Freshsales objects and properties to HubSpot schema

    We create a detailed mapping document for every object and property in your Freshsales account.

    What this step covers

    Lifecycle stages map to a custom lifecycle_stage property in HubSpot. Freddy AI scores map to a custom number field. Deal pipelines map to HubSpot deal pipelines or stage groups depending on your target HubSpot tier. Products map to the HubSpot Products object. Each mapping is reviewed with your team and validated against HubSpot's property type restrictions before any data moves.

  3. Run a sample migration with field-level diff

    A representative sample — typically 50-200 records spanning contacts, accounts, deals, and a few activities — migrates into your HubSpot account before the full run.

    What this step covers

    We generate a field-level diff between the source Freshsales record and the destination HubSpot record so you can verify lifecycle stage mapping, deal stage mapping, owner resolution, and file attachment handling. Any mapping corrections are applied before the full migration commits.

  4. Execute full migration with delta-pickup window

    The full migration runs against HubSpot using bulk API operations with batched record processing for efficiency.

    What this step covers

    A delta-pickup window (typically 24-48 hours) captures any records created or modified in Freshsales during the migration and cutover period to ensure HubSpot reflects your final Freshsales state at go-live. Every operation is logged in a detailed audit report with record counts, error details, and skipped records. One-click rollback is available if reconciliation identifies data integrity issues. After rollback verification, your team can decommission the Freshsales account.

Freshsales HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 recordsTypical, smaller accounts
5–7 days for over 500,000 records or multi-pipeline / heavy custom-object setupsLarge or heavily customised accounts

A quote scales with record count, custom property count, and pipeline complexity. Freshsales setups with multiple deal pipelines, Freddy AI scoring fields, or Enterprise-tier custom objects fall in the upper range because lifecycle-stage mapping, stage-value translation, and line-item structure add validation overhead. Additional factors include the number of custom objects requiring schema review, file attachment volume requiring pre-migration flagging, and whether pipeline consolidation decisions require Enterprise tier planning. HubSpot Professional or Enterprise tier licensing is a separate cost from migration — Starter tier supports basic pipeline structures only and cannot accommodate multiple parallel pipelines without upgrade. We provide a fixed-price quote after reviewing your Freshsales data export and the target HubSpot tier. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Freshsales to HubSpot →

Why teams move from Freshsales to HubSpot

  • Freshsales reporting caps out at curated dashboards and basic custom reports on Pro — teams managing pipeline forecasting across multiple reps need HubSpot's drag-and-drop custom reports and attribution modeling to trust their numbers, especially when compensation depends on deal stage accuracy.
  • Freddy AI contact scoring is locked behind the Pro plan at $39/user/month — growing teams that need AI lead scoring on Starter or Growth feel forced into an upgrade cost that doesn't scale. HubSpot's predictive lead scoring is a separate add-on but the tier economics differ.
  • Freshsales workflows and sales sequences require rebuild from scratch in HubSpot — teams cite frustration that years of automation logic built in Freshsales does not transfer, and the process of rebuilding creates enough friction to reconsider the migration scope entirely.
  • HubSpot's native integration with the HubSpot App Marketplace (1200+ apps) and the broader inbound marketing ecosystem offers tighter ecosystem alignment for teams that rely on marketing automation, content tracking, and lead nurturing as part of their go-to-market motion. The unified platform reduces the need for third-party integrations and provides a consistent data model across marketing and sales.

Questions, answered

Freshsales to HubSpot migration questions

How long does a Freshsales to HubSpot CRM migration take?

Most Freshsales-to-HubSpot migrations complete in 48-72 hours of clock time for under 50,000 records. Larger datasets with 500k+ records, multiple deal pipelines, or Enterprise-tier custom objects extend to 5-7 days. The longest step is pipeline consolidation planning and lifecycle-stage mapping configuration before any data moves. HubSpot Enterprise licensing must be in place before migration if your Freshsales account uses multiple pipelines.

Will my Freshsales workflows migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Freshsales workflows, sales sequences, and Freddy AI scoring models do not transfer. They must be rebuilt in HubSpot's automation tools (workflows, sequences, or a third-party scoring tool). We export your Freshsales workflow definitions as JSON and provide a rebuild reference document for your HubSpot admin. This is the most common source of post-migration surprises — plan 2-4 weeks for workflow rebuild after data migration.

What happens to Freshsales lifecycle stages in HubSpot?

Freshsales lifecycle stages migrate as a custom property on HubSpot contacts, since the two platforms use different default stage sets. The original stage values are preserved. However, HubSpot's native lifecycle_stage property and Freshsales' values may not align — we map both, and your admin should review the merged contact record after migration. Stage-progression logic (what advances a contact from Lead to MQL) must be rebuilt as HubSpot workflows.

Can I migrate Freshsales custom objects to HubSpot custom objects?

Yes. Freshsales custom objects (Enterprise tier) map to HubSpot custom objects (Professional/Enterprise tier). Custom object schemas are reviewed for compatibility with HubSpot's field type restrictions — some Freshsales field types (e.g., formula fields, roll-up summaries) have no HubSpot equivalent and are converted to read-only custom fields or preserved as text. N:N associations between custom objects and standard objects in Freshsales require HubSpot custom associations, which we configure during migration.

What happens to Freshsales deal products in HubSpot?

Freshsales deal products migrate as HubSpot deal line items linked to the deal record. The product catalog (name, description, price) migrates as HubSpot Products so line items can reference them. If a product does not exist in HubSpot at migration time, the line item lands as a text value and is flagged for manual cleanup. Bundled or composite products in Freshsales require manual reconstruction in HubSpot's product bundles feature.

Does the migration affect my Freshsales account during the cutover?

No. FlitStack AI uses scoped read access on Freshsales — your team continues working in Freshsales throughout the migration. A delta-pickup window (24-48 hours after the full migration run) captures any records created or modified in Freshsales during the cutover so HubSpot reflects Freshsales' final state at go-live. Freshsales remains fully functional until you choose to decommission it after migration sign-off.

What happens to Freddy AI scores after migration?

Freddy AI contact scores transfer as a custom number field (freddy_ai_score__c) on HubSpot contacts. Historical scores are preserved. However, the scoring model — which signals (email opens, page views, form submissions) contribute points and by how much — does not migrate. HubSpot's native predictive lead scoring is a separate paid add-on with its own configuration. We recommend rebuilding scoring logic as a HubSpot workflow-based property or subscribing to a third-party enrichment service.

How do you handle Freshsales custom fields in HubSpot?

Freshsales custom fields migrate as HubSpot custom properties. Field types are mapped to HubSpot property types: text to text, number to number, pick-list to pick-list. Freshsales date fields become HubSpot date properties. Read-only calculated fields (e.g., derived fields) convert to text fields in HubSpot. Custom field labels and help text are preserved. If a Freshsales custom field uses a field type HubSpot does not support, we flag it during the discovery audit and recommend a compatible conversion.

Get a quote

Moving from Freshsales to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

Get a quote