Moving from Salesforce to HubSpot means mapping your data object by object, rebuilding your automation and reports in HubSpot, and planning the cutover around your Salesforce contract.
Most problems come from moving messy data as is, losing access to Salesforce too early, getting caught by an auto renewal, and not getting the team using HubSpot from day one.
UpLaunch is a HubSpot Diamond Partner based in Sydney, serving Australian and New Zealand businesses. We have migrated many businesses from Salesforce to HubSpot. The practical work starts with your contract and data, before anyone imports a record.
Why businesses move from Salesforce to HubSpot
Businesses make the move to reduce licence and administration costs, simplify daily work and connect sales, marketing and service on one platform.
Compare the full operating cost, including subscriptions, specialist administration, integrations and ongoing changes. HubSpot can reduce that cost, but savings depend on your required hubs, seats and features. Buying more capability than you need can undo the saving.
Ease of use matters too. Your team needs to find customer history, update opportunities and manage follow-up without working around the system. Managers need reporting they can maintain without sending every change to a Salesforce administrator.
A shared platform also gives teams a common customer record. Marketing can see sales progress, and service can see the relationship behind a support request. The implementation still needs clear processes and ownership.
Sort out your Salesforce contract first
Turn off auto renewal and give written notice that you do not want the Salesforce subscription renewed. Deal with both before the renewal deadline, and keep written confirmation.
Salesforce's standard agreement generally requires at least 30 days' written notice before the current term ends, unless your order form says otherwise. Check your signed agreement, notice method and renewal date rather than assuming the standard terms apply.
Missing the deadline can mean another year of Salesforce while you are already paying for HubSpot. Put the notice deadline and subscription end date in the migration plan, with one person responsible for confirming them.
Giving notice of non-renewal is different from cutting off access immediately. Your exit plan must leave enough access to finish the migration and check the result.
Keep Salesforce access until the migration is done
The migration needs Salesforce admin access throughout the project. Do not cancel or downgrade access until every record in the agreed scope has been migrated and checked.
Admin access is needed to extract data, inspect relationships, resolve permissions and investigate differences between the source and destination. An export alone may not explain why a field or attachment is missing.
Take a full Salesforce export as a backup before the subscription ends. Include the required objects, activity history, files and attachments, and check that the backup can be opened independently of Salesforce.
Store the backup securely with an agreed owner. Once Salesforce access ends, links pointing back into the old system are not a substitute for having the underlying data and files.
Clean up and map before you import
Clean Salesforce before importing it into HubSpot. Moving clutter into a new CRM just moves the problem.
Archive dead records, merge duplicates and drop unused fields from the migration scope. Agree what must be retained for business or record-keeping purposes before removing anything. Preserve useful history rather than deleting records simply because they are old.
Give every remaining Salesforce field a decision: keep, merge or drop. Record that decision in a project document alongside the destination property, field type, allowed values and any transformation needed.
Then run a test import. Check representative customers, open opportunities and unusual records, not just the easiest examples. Confirm dates, currency, ownership and associations before approving the full import.
Keep source record identifiers in the mapping. They help reconcile imports, investigate discrepancies and match related records without relying on names that may be duplicated.
How Salesforce objects map to HubSpot
Salesforce objects map to corresponding HubSpot objects, with the final design reflecting how your team works.
| Salesforce | HubSpot |
|---|---|
| Accounts | Companies |
| Contacts | Contacts |
| Leads | Leads, each associated to a contact, or Contacts with a lead lifecycle stage if there is no separate lead process |
| Opportunities | Deals |
| Products and opportunity products | Products and line items |
| Cases | Tickets |
| Tasks and Events (activities) | Tasks, calls, emails and meetings on the record timeline |
| Notes | Notes |
| Files and attachments | Files attached to the matching record |
| Users | Users and record owners |
| Custom objects | Custom objects |
Associations are part of the migration too. A contact must stay linked to its company and deals. Importing the records without their relationships leaves your team with an incomplete customer view.
Keep a separate lead process where you need one
HubSpot has its own Leads object for working and qualifying leads in Sales Hub Professional and Enterprise. Salesforce leads can map into this process, with each person represented by a contact and an associated lead record.
You do not have to fold lead qualification entirely into contact lifecycle stages. However, this requires deliberate mapping: the native Salesforce contact sync does not automatically create HubSpot Lead-object records.
Check custom objects before choosing your subscription
HubSpot custom objects require an Enterprise subscription. Some Salesforce custom objects can instead be represented by ready-made Object Library objects on Professional, such as appointments, courses, listings or services.
Check the fit before choosing. A similar name does not guarantee the object supports your required relationships, reporting or process.
Bring across activity history and files
Salesforce activity history and files can be migrated so your team retains customer context in HubSpot. Include them explicitly in the scope rather than assuming they come with the main records.
Map tasks and events to the appropriate timeline activities, and migrate notes to the matching records. Check dates, content, ownership and associations so the history remains useful to the person picking up the customer relationship.
Files can be migrated and attached to the right records. Test that attachments open from HubSpot rather than depending on a Salesforce link that stops working after cancellation.
The native sync does not transfer every historical activity type automatically. Agree the extraction and import method for each category, then validate representative records against Salesforce.
What gets rebuilt rather than moved
Salesforce automation, reporting and layouts need to be rebuilt in HubSpot. They are configuration and business logic, not records you can simply import.
Flows and Apex-driven processes are redesigned using HubSpot workflows where appropriate. More complex code may need a custom-coded action or integration. Start with the business outcome, then choose the implementation.
Reports and dashboards are rebuilt around HubSpot's data model. Salesforce page layouts become HubSpot record views, organised around what each team needs to see and update.
Treat this as a chance to simplify. Retire unused reports, remove redundant automation and confirm the rules behind routing and stage changes. Rebuilding every historical workaround preserves complexity you may no longer need.
Run both systems with the Salesforce sync
HubSpot's native Salesforce integration keeps supported data in sync while both systems remain active. It suits a staged transition, such as moving one team before another.
The Salesforce integration requires an eligible HubSpot Professional or Enterprise subscription and supported Salesforce access. Confirm your Salesforce edition, API access and integration-user permissions early. Edition restrictions also affect your available export and migration methods.
Set the sync scope, field rules and ownership before connecting. Installing the integration does not automatically transfer every existing record or all historical activity.
The sync depends on Salesforce staying active and connected. Keep the subscription in place for as long as the sync is running.
Coordinate ongoing sync and one-time migration tooling carefully. Do not run overlapping transfer connections without a tested plan for matching records and preventing duplicates.
Reconnect every Salesforce integration
List every system connected to Salesforce before cutover. Each connection needs a HubSpot replacement, a rebuild or an explicit decision to retire it.
Include finance software, website forms, phone systems, quoting tools, support platforms and custom connections. Record what each integration sends, what triggers it and which system owns the data.
Reconnect through a suitable HubSpot Marketplace app where available, or rebuild the connection. Test the required behaviour rather than assuming an app with the right name covers your existing process.
Check both directions. A new deal reaching your finance system is only half the test if payment or customer updates also need to return to HubSpot.
Get the team using HubSpot from day one
Agree a clear cutover date and train your team to work in HubSpot from day one. Training must cover their daily work, using the setup they will use.
Sales needs to practise managing opportunities and follow-up. Managers need to check pipeline reporting. Service and marketing need to understand the handoffs that affect them.
At cutover, make Salesforce read-only for day-to-day users while retaining the access needed for final checks. Otherwise, people can continue updating the old system and create two competing versions of customer information.
Assign someone to resolve questions after cutover. Check that ownership, access and essential connections work before treating the migration as complete.
Pre-migration checklist
- Auto renewal switched off and at least 30 days' written notice given, subject to your agreement.
- Admin access to Salesforce confirmed for the whole project.
- Salesforce edition checked for API access.
- Full Salesforce backup taken.
- Every connected system listed.
- Data cleaned: duplicates merged, dead records archived, unused fields dropped.
- HubSpot seats and hubs planned.
- Cutover date agreed with the team.
What a Salesforce to HubSpot migration costs
UpLaunch builds start from $4,500 + GST. Salesforce data imports are $500 per object, files import is $2,000, and custom objects are $2,000 each.
Most sales team migrations land between $6,000 and $12,000 + GST. These figures are in Australian dollars, with the final scope confirmed before work starts.
HubSpot licences are billed separately by HubSpot. Every UpLaunch pack includes licence and credit design, so you decide which seats and hubs you need before you buy and do not overpay. See pack pricing.
Frequently asked questions about Salesforce to HubSpot migration
Will we lose any data?
Everything in the agreed scope is mapped and test imported first, then validated after migration. UpLaunch checks records, relationships and history before sign-off. These safeguards reduce the risk of loss; they are not a blanket guarantee that every Salesforce feature transfers unchanged.
Can we keep using Salesforce during the migration?
Yes, until cutover. The Salesforce sync can keep supported data in step if both systems need to run together. Agree which system owns updates during the transition.
Will our activity history come across?
Yes. Tasks, events and notes can be migrated to each record's timeline as part of the agreed scope. UpLaunch tests activity types and associations rather than relying on the native sync to bring over all history.
Can our custom objects be migrated?
Yes, into HubSpot custom objects with an Enterprise subscription. Where a ready-made Object Library object fits, that may be an alternative on Professional.
When should we cancel Salesforce?
Turn off auto renewal and give at least 30 days' written notice before the term ends, subject to your agreement. Keep access until the migration is checked, and keep Salesforce active while any required sync is running.
Where do we start?
Start with a discovery call to map what you have in Salesforce. UpLaunch reviews your data, processes and connections so the migration scope and HubSpot requirements are clear before the build.
Book a discovery call to discuss your Salesforce setup and what needs to move.
Build your own estimate to explore the pack and migration options before you speak with us.
Planning a HubSpot build?
Choose a pack, add what you need and see your fixed price in two minutes.
