Agency Migration Guide
Freshsales Suite to HubSpot Migration
What actually transfers, what quietly does not, and what has to be rebuilt by hand.
We mapped Freshsales Suite against HubSpot feature by feature: 48 features, 4 synced objects, 8 documented traps and 36 items that have to be rebuilt. The whole map is on this page, ungated.
The PDF is the same reference, formatted to send to a client.
Get The Guide And The Calculator
The full Freshsales Suite to HubSpot reference as a branded PDF you can send straight to a client, plus the Excel calculator we scope these migrations with: every one of the 48 features as a row, enter your counts, get hours.
Three files: the guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.
Freshsales Suite to HubSpot is a medium migration, typically 3-6 weeks. Of 48 features we mapped, 37 carry across as they are and 11 land with something lost. The work is not moving records: it is the 36 items nothing moves for you.
Migration Scorecard
- Migration complexity
- Medium
- Typical timeline
- 3-6 weeks
- Recommended method
- Sync then migrate
- Native sync
- Data sync, two way
- Smart transfer
- Not supported
- HubSpot subscription
- Free for default mappings. Data Hub Starter or higher for custom field mappings. Both Freshsales (classic) and Freshsales Suite have separate marketplace listings.
Feature parity across 48 capabilities
- Maps directly: 37 (77%)
- Maps partially: 11 (23%)
- No equivalent: 0 (0%)
4
Objects synced natively
8
Limitations and traps
36
Manual rebuild items
4
Source editions covered
Where this comes from: Our own research corpus, verified 2026-07-31, behind every number on this page.
The Four Objects That Sync Natively
What the connector moves for you, and which way each one flows.
Leads
Two wayBecomes Contacts
Freshsales Leads sync to HubSpot as Contacts. Only records with valid email addresses will sync - records without email are silently excluded and not logged. Configurable to sync both Leads and Contacts, leads only, or contacts only.
Contacts
Two wayBecomes Contacts
Freshsales Contacts also map to HubSpot Contacts. Both are synced as the same HubSpot object type.
Accounts
Two wayBecomes Companies
Company sync available via the Freshsales Suite data sync app.
Deals
Two wayBecomes Deals
Deal sync requires an accompanying contact and/or company sync to maintain associations.
Eight Things the Sync Does Not Tell You
Each one is documented, and each one has ended a migration in a bad week.
Records Without Email Addresses Are Silently Excluded
All records must have valid email addresses to sync. Records without emails are excluded silently and are not logged in error reports, making it easy to miss migrated data gaps.
Workaround: Audit Freshsales data before migration to identify records without email. Export these separately and import via CSV.
Notes and Files Do Not Sync Natively
Notes, file attachments, and documents connected to Freshsales records are not part of the native sync between Freshsales and HubSpot.
Workaround: Migrate notes and files separately via API, CSV import (for notes as activities), or third-party migration tools.
Activity History (calls, Meetings, Emails) Does Not Sync
Call logs, meeting records, email history, and other activity data from Freshsales do not transfer through the native sync integration.
Workaround: Export activity data from Freshsales and import via HubSpot API. Third-party tools like MigrateMyCRM can handle activity migration.
Default Sync Frequency Is Twice Daily
Unlike real-time sync available in some other HubSpot data sync integrations, the Freshsales sync runs twice daily by default. Manual sync is available but must be triggered manually.
Workaround: Use the manual 'Start sync' button for immediate synchronization when needed.
Dropdown Fields Require Choice-level Mapping
Dropdown/picklist fields require mapping at the individual choice level, not just the field level. This is tedious for fields with many options.
Workaround: Plan dropdown mappings in advance. Document all choice values in both systems before configuring the sync.
New Custom Fields Require Manual Refresh
When new custom fields are created in either system, they do not automatically appear in the mapping interface. A manual refresh is required.
Workaround: After creating new custom fields, refresh the integration mapping interface before configuring the new field sync.
Mandatory Fields Must Be Mapped Before Sync Activation
The sync cannot be activated until all mandatory/required fields in both systems are properly mapped. The 'Start sync' button remains disabled until this is complete.
Workaround: Identify all mandatory fields in both Freshsales and HubSpot before configuring the integration.
Freshsales Telephony Data Requires Reconfiguration
Freshsales' built-in telephony features (call logs, recordings, notes, activity timelines) are a major feature for many teams. This data forms the backbone of sales reporting and does not transfer to HubSpot.
Workaround: Reconfigure calling infrastructure in HubSpot. Export call logs and import as activities via API. Recordings may need to be stored externally.
The 36 Items That Get Rebuilt by Hand
This is the list that separates a quote that holds from one that does not.
Data And Objects
Notes and Annotations on Records
File Attachments and Documents
Call Logs and Recordings (built-in Telephony Data)
Email Conversation History
Meeting Records
Activity Timelines
Custom Module Data
Records Without Email Addresses (silently Excluded From Sync)
Automation
Freshsales Workflow Automations (alerts and Task Creation Rules)
Sales Sequences and Follow-up Cadences
Auto-assignment Rules
Lead Scoring Rules and Criteria
Territory Management Rules
Time-based Workflow Triggers
Reporting
Custom Reports and Analytics
Dashboard Configurations
Sales Forecasting Reports
Pipeline Velocity Reports
Activity/productivity Reports
Revenue Analytics
Sales And Marketing Config
Pipeline Stages and Deal Stage Mappings
Lifecycle Stage Alignment (Freshsales Statuses to HubSpot Lifecycle Stages: Lead, MQL, SQL, Opportunity, Customer)
Email Templates and Snippets
Web Forms and Landing Pages
Chat Widgets and Bot Configurations
Product Catalog
CPQ (Configure-Price-Quote) Configurations
Users And Permissions
User Roles and Territory Assignments
Record Visibility and Sharing Rules
Team Hierarchy Configurations
Profile-level Permissions
Integrations
Freshsales Marketplace App Connections
Freshdesk/Freshworks Ecosystem Integrations
Calendar Sync Configurations (Google/Outlook)
Third-party Telephony Integrations
Zapier/Make Automations Connected to Freshsales
The Sequence
Sync First, Then Migrate
Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.
- 1
Audit Freshsales Setup
catalog all fields, pipelines, automations, and integrations
- 2
Define HubSpot Goals and Map Freshsales Lifecycle Statuses to HubSpot Lifecycle Stages
Define HubSpot goals and map Freshsales lifecycle statuses to HubSpot lifecycle stages
- 3
Clean Data
deduplicate, ensure all critical records have email addresses, remove stale data
- 4
Set up HubSpot
create custom properties, configure pipelines, map deal stages
- 5
Install Freshsales Suite or Freshsales Data Sync App From HubSpot Marketplace
Install Freshsales Suite or Freshsales data sync app from HubSpot Marketplace
- 6
Configure Field Mappings Including Dropdown Choice-level Mappings
Configure field mappings including dropdown choice-level mappings
- 7
Enable Sync and Verify Initial Data Transfer Accuracy
Enable sync and verify initial data transfer accuracy
- 8
Migrate Notes, Activities, and Call History via API or Third-party Tool
Migrate notes, activities, and call history via API or third-party tool
- 9
Rebuild Automations as HubSpot Workflows With Clear Triggers and Actions
Rebuild automations as HubSpot workflows with clear triggers and actions
- 10
Recreate Reports and Dashboards in HubSpot
Recreate reports and dashboards in HubSpot
- 11
Run Test Migrations and Validate Data Before Full Cutover
Run test migrations and validate data before full cutover
- 12
Train Team on HubSpot and Execute Go-live With Transition Planning
Train team on HubSpot and execute go-live with transition planning
Typically 3-6 weeks end to end, depending on how much of the source configuration is actually in use.
Effort Estimator
How Big Is This Migration?
A handful of questions, no email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.
Estimated Effort
Answer a couple of questions and an hours range appears here.
Built from our research on 48 Freshsales Suite features. It is a range, not a quote.
A planning range, not a quote. It is delivery effort only, with no project management line and no agency markup, so add your own. What moves it most in practice is data quality.
What Goes Wrong Most Often
The failures that show up again and again, in roughly the order they bite.
Records Without Email Addresses Are Silently Dropped - Audit Before Migration
Records without email addresses are silently dropped - audit before migration
Freshsales Built-in Telephony Data Is a Major Loss - Plan Call Data Migration Separately
Freshsales built-in telephony data is a major loss - plan call data migration separately
Twice-daily Sync Frequency Means Data Can Be Stale for up to 12 Hours
Twice-daily sync frequency means data can be stale for up to 12 hours
Freshsales Automations Are Simpler Than HubSpot Workflows - This Is an Opportunity to Build Smarter Workflows, Not Just Replicate
Freshsales automations are simpler than HubSpot workflows - this is an opportunity to build smarter workflows, not just replicate
Dropdown Fields Require Tedious Choice-by-choice Mapping
Dropdown fields require tedious choice-by-choice mapping
Two Separate Marketplace Apps Exist (Freshsales Classic Vs Freshsales Suite) - Install the Correct One
Two separate marketplace apps exist (Freshsales Classic vs Freshsales Suite) - install the correct one
Pipeline Restructuring Needed - Not All Freshsales Pipelines May Map to Current Sales Motions
Pipeline restructuring needed - not all Freshsales pipelines may map to current sales motions
Post-migration Optimization Is Critical - Migration Is Only the First Phase
Post-migration optimization is critical - migration is only the first phase
Questions
Freshsales Suite To HubSpot, Answered
Yes. Data sync, two way, covering 4 objects. What it does not do is rebuild configuration: that is the 36 items below.
Typically 3-6 weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database is not by itself a long project.
Of 48 features we mapped, 37 (77%) carry across directly and 11 (23%) map partially, meaning something is lost or reshaped. 0 have no HubSpot equivalent at any tier.
36 items have to be rebuilt by hand, and 8 documented limitations are not surfaced by the connector at all. The full list of both is on this page.
Free for default mappings. Data Hub Starter or higher for custom field mappings. Both Freshsales (classic) and Freshsales Suite have separate marketplace listings.
Only in one direction. The sync is not bidirectional here, so a parallel period means picking a system of record and accepting drift in the other.
Ready to get started?
Let's do something great together.
Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."
Fill out this form, and someone from our Solutions team will be in touch with you soon!