Your accounts, contacts and deals, with the supported notes, tasks and files. See what travels and what stays in Freshsales before switching over.
Start free assessmentWe run Freshsales CRM to HubSpot CRM migrations. The assessment is free and comes before any commitment.
Running this for a client? Explore partnership options.
Freshsales CRM
HubSpot CRM
Keep deals linked to contacts and companies, and activities linked to their records in HubSpot CRM.
We find your custom fields in Freshsales CRM and plan how their values will travel to HubSpot CRM before migrating their records.
Your activity history arrives on the record it belongs to. This page names which types transfer and any limit on them.
We match them to your HubSpot CRM users and stages.
The plan flags values that change during migration. The original value comes across beside the converted one.
Where possible, we create a field in HubSpot CRM for data with no matching field.
We read accounts, contacts and deals from the saved views selected for the migration. We check those views with you so the scope includes the records you intend to bring. Notes and files are read with their parent records. Keep access to Freshsales for the calls, emails and other records listed as outside this migration.
Accounts become companies. Contacts, deals, notes, tasks and appointments are handled as the corresponding HubSpot records.
Connect Freshsales using the API key and account address from Profile Settings, API Settings. Your source connection gives you the free record count and price.
Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.
How many custom properties HubSpot will hold depends on your plan
View detailsHide detailsHubSpot caps custom properties per object, and the cap moves with your subscription. A Freshsales account that has grown a lot of custom fields can exceed it.
Verified against knowledge.hubspot.comWe count yours in the free assessment and show you the number against your plan's limit, so you can decide what to bring rather than find out during the run.
Missing required fields can block records
View detailsHide detailsHubSpot rejects records that are missing fields your admin requires. Some fields are required only when another field has a particular value. We report which field is missing so you can correct it.
Verified against developers.hubspot.comWe report missing required fields during the migration. The assessment does not check these rules. Fill in the missing values in your source CRM or ask your HubSpot admin to change the rule, then we retry without duplicating records.
Linking records requires Edit Associations permission
View detailsHide detailsHubSpot calls links between records associations, such as a deal linked to a company. Without Edit Associations permission, HubSpot blocks us from creating those links.
Verified against developers.hubspot.comConnect using a HubSpot user with Edit Associations permission. If you have already connected, ask your admin to grant that user the permission. We can then retry the missing links.
Closed-deal reporting needs a stage review
View detailsHide detailsOur Freshsales source carries stage names without declaring whether each stage means won, lost or open.
We review how your stages should be treated before the migration runs.
Calls and email conversations stay in Freshsales
View detailsHide detailsOur Freshsales source does not read phone calls or email conversations.
Your notes, tasks and appointments can still travel.
Custom modules, products and line items are outside this migration
View detailsHide detailsOur Freshsales connector does not carry these records in either direction.
Accounts, contacts, deals, notes and tasks are included in the supported scope.
Marketing consent is not migrated
View detailsHide detailsWe do not read or write subscription status through our Freshsales connector.
Review consent separately before using the destination for marketing.
One action removes the records we wrote to HubSpot CRM. Review what will remain before you undo and retry.
A paused run resumes where it stopped, without losing progress or duplicating records.
We only read Freshsales CRM. Nothing is written back to it.
Keep working in Freshsales CRM while you check the results. Then bring across the latest changes before switching over.
In HubSpot CRM after the migration
After you undo
Covers up to 20,000 records. Larger migrations use higher tiers. You pay once per migration, with no recurring charge.
Connect Freshsales CRM to see your record count and price before you commit.
Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of HubSpot CRM and refund you.
We discover your Freshsales custom fields and plan them for the matching HubSpot CRM records. Review the plan for type changes and fields you prefer to leave behind.
No. Our connector leaves calls and email conversations in Freshsales. Review the supported activity types above before switching over.
We review stage choices with you. The Freshsales connector does not infer won or lost from a stage name, so this needs attention before you rely on destination reports.
We run the migration and stay reachable. Connect Freshsales for the free assessment and price, then HubSpot to complete the plan. Nothing moves until you ask.
Yes. We only read Freshsales and never write back to it. Keep working while you check the results, then bring across the latest changes before switching over.
You can undo the migration, correct the issue and run again. Created fields, shared catalogue data and any other items listed as retained stay in place.
One payment, based on the records that move. The free assessment of Freshsales gives you the exact count and price before you commit. Payment is by invoice, with no subscription.
Next step
Create an account and connect Freshsales CRM for your free assessment. See your record count and price before you commit. Nothing moves until you ask.
Start free assessment