---
title: "HubSpot to Freshsales Migration: Field Mapping & Rollback"
description: "Migrate HubSpot to Freshsales with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/hubspot/to/freshsales"
---

# HubSpot to Freshsales migration

We migrate Contacts, Companies, Deals, and Engagement history from HubSpot Sales Hub into Freshsales with the Contact-versus-Leads split resolved upfront, activity records mapped to Freshsales Call, Email, Meeting, and Task objects, and every HubSpot custom property typed to a matching Freshsales field before cutover.

Short answer

FlitStack AI migrates lead or contacts, accounts, deals, pipelines and products from HubSpot to Freshsales, 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: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/hubspot/to/freshsales#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Destination Freshsales ![](https://flitstack.ai/platforms-trim/freshsales.webp)

Lead or Contact Account Deal Pipeline Product

Mapped field by field · sample run · one-click rollback

## What moves from HubSpot to Freshsales?

Moving from HubSpot Sales Hub to Freshsales is a simplification migration driven by cost predictability and feature bundling.

Read the full summary

HubSpot gates calling, advanced automation, and custom reporting behind Professional at $100 per seat with mandatory onboarding fees that can add 30-40 percent to year-one cost. Freshsales includes call minutes, Freddy AI-powered lead scoring, and workflow automation in its Growth plan at $15 per seat with no per-user floor. We resolve the HubSpot Contact model (one object with Lifecycle Stage) against Freshsales separate Leads and Contacts by splitting at the Sales Qualified Lead boundary during migration. We use the Freshsales REST API for standard records and handle email, call, meeting, and task engagements with proper object linkage. Workflows, sequences, and automation logic do not migrate; we deliver a written inventory for the admin to rebuild in Freshsales' automation builder.

1:N split

### Contact → Lead or Contact (split required)

HubSpot uses a single Contact object with Lifecycle Stage to represent both unqualified prospects and customers.

How it maps

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.

1:1

### Company → Account

HubSpot Company records map directly to Freshsales Account.

How it maps

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.

1:1

### Deal → Deal

HubSpot Deals map directly to Freshsales Deals with identical field names in most cases.

How it maps

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.

configuration

### Pipeline → Pipeline

HubSpot pipeline configurations (stages, probabilities, active/inactive status) map to Freshsales pipeline configurations.

How it maps

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.

1:1

### Product → Product

HubSpot Products map directly to Freshsales Products.

How it maps

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.

lookup

### Owner → User

HubSpot Owners map to Freshsales Users via email matching.

How it maps

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.

******What moves 12 objects

HubSpot Freshsales

- Contact Lead or Contact split
- Company Account 1:1
- Deal Deal 1:1
- Pipeline Pipeline transformed
- Product Product 1:1
- Owner User transformed

\+ 6 more in the mapping below

## How HubSpot and Freshsales 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.

| Dimension        | HubSpot                                                                                                                         | Freshsales                                                                                                    |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Contact model    | Single Contact object with Lifecycle Stage property for all prospect and customer records                                       | Separate Lead (unqualified) and Contact (qualified, linked to Account) objects with explicit conversion step  |
| Pipeline count   | Starter 1, Professional 15, Enterprise 100 deal pipelines                                                                       | Unlimited deal pipelines at all paid tiers (Growth, Pro, Enterprise)                                          |
| Feature bundling | Sequences, calling, advanced automation, and AI tools gated at Professional ($100/seat) and Enterprise ($150/seat)              | Calling minutes, Freddy AI lead scoring, workflow automation, and customization included at Growth ($15/seat) |
| Pricing model    | Per-seat with Marketing Contacts metering; mandatory onboarding fees of $1,500 (Pro) and $3,500 (Ent) not shown on pricing page | Per-seat with no onboarding fees and no per-user minimums at any tier                                         |
| Automation       | Property-triggered Workflows with visual builder, gated at Professional                                                         | Workflow automation builder included from Growth plan with no feature gates                                   |
| AI capabilities  | AI features (call transcription, deal forecasting) bundled in Professional and Enterprise tiers                                 | Freddy AI copilot and lead scoring available from Growth tier with no add-on cost                             |
| Calling plan     | Calling available only at Professional and Enterprise; metered minutes at extra cost                                            | Included call minutes at every paid tier; no per-minute overage at lower plans                                |

## What to watch for in a HubSpot to Freshsales migration

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

high

### Contact-Leads split requires upfront rule definition

HubSpot uses one Contact object with a Lifecycle Stage property for all prospect and customer records.

How we handle it

Freshsales separates Leads (unqualified) from Contacts (qualified, attached to Accounts). We define the split rule during scoping based on the customer's Lifecycle Stage matrix, apply it as the first transformation during migration, and preserve the original HubSpot Lifecycle Stage in a custom field on both the Lead and Contact record. Migrations that skip this step produce orphaned Contacts with no Account or Leads that should have converted on day one.

high

### HubSpot Workflows and Sequences do not migrate

HubSpot property-triggered Workflows and sales engagement Sequences have no direct Freshsales equivalents.

How we handle it

Freshsales uses its own automation builder with event-action logic, and its sales engagement tools (called Sequences in Freshsales) have a different cadence model. We do not migrate automations as code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger, conditions, actions, and recommended Freshsales automation equivalent. The customer's admin rebuilds them in Freshsales' workflow builder post-migration.

high

### Notes and Files require explicit linked-record migration

HubSpot community posts confirm that Notes and Files connected to records in HubSpot do not migrate through standard CSV-based or basic API tools.

How we handle it

Freshsales stores attachments separately from notes, and both require explicit linking to parent records (Contact, Lead, Account, Deal) via the Freshsales attachment API. We handle this linkage explicitly during migration, but any HubSpot Files attached to notes require additional file processing that adds scope to engagement migration.

medium

### Freddy AI scoring is not portable

Freshsales includes Freddy AI-powered lead scoring and deal insights from the Growth plan at no additional cost.

How we handle it

HubSpot's predictive scoring is gated at Professional and Enterprise or available as a separate AI add-on. Any HubSpot predictive lead scoring model was trained on HubSpot data and does not carry over to Freshsales Freddy AI. Teams should plan for a four-to-eight week calibration period as Freddy AI builds fresh signals from migrated data.

medium

### HubSpot calling numbers do not port to Freshsales

Freshsales assigns calling numbers to team members within its built-in phone system.

How we handle it

Existing HubSpot calling numbers associated with reps do not transfer to Freshsales. Teams using HubSpot's built-in dialer need to either port existing numbers through Freshsales' carrier or provision new Freshsales dialer numbers for each rep post-migration. This is a separate provisioning step outside the data migration scope.

## How the migration runs

1. ### Discovery and scoping

   We audit the source HubSpot portal across plan tier, custom properties, custom objects, pipeline count and stage definitions, active workflows, sequence count, and engagement volume by type (calls, emails, meetings, tasks).

   What this step covers

   We pair this with a Freshsales edition recommendation: Growth ($15/seat) covers most migrations with included calling, Freddy AI, and automation; Pro ($49/seat) adds advanced reporting and territory management; Enterprise ($79/seat) adds custom modules and advanced permissions. The discovery output is a written migration scope, a Contact-Leads split rule definition, and a Freshsales edition recommendation.

2. ### Schema design and Freshsales configuration

   We configure Freshsales as the destination environment before any data import.

   What this step covers

   This includes creating custom modules matching HubSpot custom objects, adding custom fields mapped from HubSpot properties with equivalent data types, defining pipeline and stage structures matching HubSpot pipelines and deal stages, configuring the Contact-Account relationship model, and enabling any Freshsales features (Freddy AI, automation builder, calling) included in the selected edition. We validate the schema in a Freshsales test environment before production migration begins.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Freshsales sandbox environment using production-like data volume.

   What this step covers

   The customer's RevOps lead reconciles record counts across all object types, spot-checks fifty random records against the HubSpot source for field-level accuracy, and validates that the Contact-Leads split rule was applied correctly. Any mapping corrections and schema adjustments happen in sandbox before production migration begins.

4. ### Owner reconciliation and User provisioning

   We extract every distinct HubSpot Owner referenced on Contact, Company, and Deal records and match by email against the Freshsales destination User table.

   What this step covers

   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. Migration cannot proceed past this step because Owner lookups must be satisfied before records can be imported with correct assignments.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Accounts (from HubSpot Companies), Leads and Contacts (with the Lifecycle Stage split applied and Account lookups resolved), Deals (with Owner and pipeline assignments), Products, Deal-Product associations, then engagement history (Calls, Emails, Meetings, Tasks, Notes with attachments).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins. We use the Freshsales REST API with batch chunking and rate-limit handling for large engagement sets.

6. ### Cutover, validation, and automation rebuild handoff

   We freeze HubSpot writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record.

   What this step covers

   We deliver the Workflow and Sequence inventory document to the customer's admin team with recommended Freshsales automation equivalents. We support a one-week hypercare window to resolve any reconciliation issues. We do not rebuild HubSpot Workflows in Freshsales' automation builder inside the migration scope; that is a separate configuration task for the customer's admin team.

![](https://flitstack.ai/platforms/hubspot.svg) HubSpot ![](https://flitstack.ai/platforms/freshsales.svg) Freshsales

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Freshsales Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**7-12 weeks** Large or heavily customised accounts

A quote scales with record volume, engagement history size, and whether custom objects are involved. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for HubSpot to Freshsales →](https://flitstack.ai/contact)

## Why teams move from HubSpot to Freshsales

- HubSpot pricing scales faster than teams expect. Sequences, calling, and advanced automation are gated behind Professional at $100 per seat with a five-seat minimum and a $1,500 mandatory onboarding fee not shown on the main pricing page. A five-person team on HubSpot Professional pays $6,000 in base subscription alone before overage charges. Freshsales Growth at $15 per seat with unlimited users, included call minutes, and Freddy AI costs the same five-person team $75 per month total with no onboarding, a difference of over $5,000 in year one.
- HubSpot Starter locks advanced automation and calling behind Professional tier, leaving teams with minimal automation tooling. Reddit reviewers comparing Freshsales to HubSpot Starter note that Freshsales has tools available at $47 per month that HubSpot gates at $100 per seat, making Freshsales the more practical choice for teams that need workflow automation without the Professional tier commitment.
- HubSpot's Marketing Contacts billing model causes cost shocks during migration. All contacts imported into HubSpot default to marketing-billed status unless explicitly flagged, multiplying the monthly bill by three to four times for teams with large prospect databases. Freshsales does not use a contact-based billing meter, so teams migrating from HubSpot retain predictable per-seat costs without the risk of a billing spike tied to contact volume.
- HubSpot workflow complexity increases at scale, requiring either a HubSpot partner or significant admin time to maintain advanced automation. Capterra and G2 reviewers note that teams outgrow the visual workflow builder quickly and face a sharp learning curve. Freshsales' automation builder is included from Growth tier with a simpler event-action model that teams adopt faster without formal training or partner involvement.
- HubSpot frequently updates its interface and feature set, forcing ongoing re-training that disrupts sales team productivity. Reddit reviewers in the HubSpot community cite difficulty keeping pace with constant new features and UI changes. Freshsales maintains a stable interface with quarterly update cycles, reducing the re-training burden for sales teams that prioritize CRM consistency over continuous feature releases.

Questions, answered

## HubSpot to Freshsales migration questions

How long does a HubSpot Sales Hub to Freshsales migration take?

Most migrations land between three and five weeks for accounts under 10,000 Contacts and 3,000 Deals with no custom objects and a straightforward Contact-Leads split. Migrations with custom objects, multiple pipelines, large engagement histories (over 200,000 activity records), or complex field mapping move to seven to twelve weeks because of Freshsales API batch processing, the engagement linkage work, and the Contact-Leads split validation.

What records and data can migrate from HubSpot Sales Hub to Freshsales?

We migrate Contacts (split into Freshsales Leads and Contacts), Companies (as Accounts), Deals, Products, Line Items, Owners (as Users), and full engagement history including Calls, Emails, Meetings, Tasks, and Notes with attachments. Custom object records migrate when the Freshsales plan supports custom modules (Pro and Enterprise tiers). Historical timestamps, deal amounts, stage assignments, and owner records are preserved throughout. All active HubSpot sequences, workflows, and automation rules do not migrate as code; we deliver a written inventory for the admin to rebuild in Freshsales.

Do HubSpot Workflows, Sequences, and automations migrate to Freshsales?

No. HubSpot Workflows and Freshsales automation use different event-action models and are not directly compatible. Sequences (sales engagement cadences) similarly do not migrate. We do not migrate automations as configuration code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger conditions, actions, and a recommended Freshsales automation equivalent. The customer's admin rebuilds these in Freshsales' workflow builder and sequence tools post-migration.

How do we handle the Contact-Leads split during migration?

We define the split rule during scoping using the customer's HubSpot Lifecycle Stage matrix. Contacts with Lifecycle Stage of subscriber, lead, or marketing qualified lead become Freshsales Lead records. Contacts with Lifecycle Stage of sales qualified lead, opportunity, customer, or evangelist become Freshsales Contact records linked to a Freshsales Account. We preserve the original HubSpot Lifecycle Stage in a custom field on both the Lead and Contact record for reporting continuity and audit trails.

Can we keep HubSpot Marketing Hub while moving Sales to Freshsales?

Yes, but it requires careful planning. HubSpot Marketing Hub and Freshsales are separate CRM platforms with no native bidirectional sync. If the team needs both marketing automation (HubSpot Marketing Hub) and a CRM for sales reps, Freshsales can receive HubSpot Marketing Hub leads via webhook, Zapier integration, or a custom API connector. We configure this data handoff during migration so that new marketing-qualified leads flow into Freshsales as Leads. The customer continues paying for HubSpot Marketing Hub while moving sales seat licensing to Freshsales.

What happens to our HubSpot engagement history (calls, emails, meetings, tasks)?

We preserve full engagement history by mapping each HubSpot engagement type to the corresponding Freshsales object: Calls to Freshsales Calls, Emails to Freshsales Emails, Meetings to Freshsales Meetings, Tasks to Freshsales Tasks, and Notes to Freshsales Notes with attachments. Each engagement is linked to the parent Contact, Lead, Account, or Deal record using Freshsales association fields. Historical timestamps, duration, disposition, and content are preserved during migration.

What is Freddy AI and does our scoring model migrate?

Freddy AI is Freshsales built-in artificial intelligence layer that provides lead scoring, deal insights, and next-best-action recommendations from Growth tier onward. HubSpot's predictive scoring (where available) was trained on HubSpot-specific data and does not carry over to Freshsales. Any HubSpot lead score values migrate as a custom field that the customer can use for reference, but the Freddy AI scoring model rebuilds fresh from migrated data over a four-to-eight week calibration period.

## Related migrations

[![](https://flitstack.ai/platforms-trim/freshsales.webp) Migrate to **Freshsales** Every source we move into Freshsales, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/crm/freshsales) [**Freshsales to HubSpot** The same pair in reverse](https://flitstack.ai/migrations/crm/freshsales/to/hubspot) [**Sharpspring to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sharpspring/to/freshsales) [**Dynamics 365 to Freshsales** Mapping · history · rollback](https://flitstack.ai/migrations/crm/dynamics-365-sales/to/freshsales) [**HubSpot to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/salesforce-sales-cloud) [**HubSpot to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/zoho-crm) [**HubSpot to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/pipedrive)

## Sources: official documentation

1. [Freshsales / Freshmarketer Migration FAQs — Freshworks Support](https://crmsupport.freshworks.com/support/solutions/articles/50000003712-freshsales-freshmarketer-migration-faqs)
2. [What are custom field limits? — Freshsales Suite Support](https://support.freshsales.io/support/solutions/articles/226676-what-are-custom-field-limits-)
3. [Freshsales bulk upsert — Freshworks Support](https://support.freshsales.io/support/solutions/articles/freshsales-bulk-upsert)
4. [How to import contacts from a CSV/XLSX file — Freshsales Classic](https://support.freshsales.io/support/solutions/articles/218558-how-to-import-contacts-from-a-csv-xlsx-file-)
5. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
6. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
7. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)

Get a quote

## Moving from HubSpot to Freshsales?

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

[Get a quote](https://flitstack.ai/contact)
