Map every Salesforce object and property to its HubSpot equivalent before moving any data, migrate in stages (users, companies, contacts, deals, tickets and activities) and validate each stage with counts and samples against the source. HubSpot offers the Salesforce integration and the Smart Transfer tool, but neither moves everything. In Chile and Latin America, what usually gets left behind are attachments, products and the historical source of leads.
| Salesforce | HubSpot | Watch out for |
|---|---|---|
| Accounts | Companies | Load them before deals |
| Contacts and leads | Contacts | Matched by email: clean up duplicates |
| Opportunities | Deals | Each record type creates a pipeline |
| Cases | Tickets | Existing ones are imported separately |
| Tasks and events | Activities | Turning on the sync does not bring history |
| Products and price books | Products | They do not travel with the sync |
Accounts become companies; contacts and leads, contacts; opportunities, deals; cases, tickets; and tasks and events, activities. Each opportunity record type creates a deal pipeline in HubSpot, so decide beforehand whether you keep that structure or redesign it.
Not everything has a match. Products and price books do not travel with the opportunity sync; Salesforce custom objects need custom objects in HubSpot, which are Enterprise; and the two systems' campaigns do not correspond. Decide what gets migrated, what gets archived and what gets rebuilt.
The native Salesforce integration requires HubSpot Professional or Enterprise and a Salesforce admin user with API access. HubSpot recommends it to import records: it brings leads, contacts, accounts, opportunities, tasks, cases and events, with up to 500 field mappings per object.
Smart Transfer, available to Super Admins on all plans, transfers one way into HubSpot and allows one-time loads of what the sync does not cover, such as attachments. File imports handle the rest: up to 1,048,576 rows per file on paid plans.
Users first: the owner is assigned only if the HubSpot user matches an active Salesforce user's name and email. Then companies, because deals need company sync turned on and accounts already loaded. Then contacts, deals, tickets and, last, activities and attachments.
Keep the Salesforce ID on every record: the integration maintains properties such as the Salesforce lead and contact IDs, and for the rest a unique property of your own is worth having. That is what lets you reconcile, deduplicate and reload without creating duplicates.
With counts and samples per stage: how many accounts, contacts and opportunities there were in Salesforce, how many reached HubSpot and why they differ. Review ten random records of each object, with their associations, amounts, stages and owners, together with the team that uses them.
Also look for what gets lost silently: activities that did not arrive because turning on the sync does not bring history, Salesforce records sharing an email that HubSpot merges into one contact, and the source of leads, since migrated contacts show up as offline sources. In Chile and Latin America, keep that source in a property of your own.
With a full test before the cutover.
Objects, fields in use, record types, automations and duplicates. Merge records with the same email in Salesforce before migrating.
Each field with its destination property, its type and its rule: prefer Salesforce, always use Salesforce, sync both ways or do not sync.
HubSpot users with the same name and email as in Salesforce, pipelines by record type or redesigned, and the currencies you use.
Companies, contacts, deals, tickets and activities, in that order, keeping the Salesforce ID on every record.
Per object: totals, ten random records with associations and amounts, and a review by the team that uses them.
A cutover date, a final load of changes and Salesforce in read-only mode until you confirm nothing is missing.
Migrating everything at once and finding the errors when the team already works in HubSpot.
Users with different emails in each system: deals left without an owner.
Forgetting attachments, products and price books, which do not travel with the sync.
Losing the source of leads and being left without historical attribution.
30 minutes with Roberto. No demo and no access to your CRM.
We migrate from Salesforce, Zoho, Pipedrive or spreadsheets without losing history: we map objects and properties before moving any data, migrate in stages and validate with samples alongside your team. The migration is part of the HubSpot Implementation, at a fixed price and with everything documented in your name.
From spreadsheets or another CRM to HubSpot in 3 to 4 months, with history migrated and a fixed price.
See ImplementationWhich hubs and seats you need for the integration and the migration, without overpaying.
See LicensesIf you already migrated and something does not reconcile, 10 hours of inventory with risks and backlog.
See the DiagnosticThe guarantees that apply
Workflows, integrations, code and keys documented and in your name. If you change partners, you lose nothing.
We check the numbers your management uses against the records, with definitions and sources documented.
We put them in writing because they are what we control.
Yes: the native Salesforce integration, which HubSpot recommends to import records and which requires Professional or Enterprise, and Smart Transfer, which transfers one way into HubSpot. File imports cover the rest.
Smart Transfer lets you transfer them as a one-time load, outside the ongoing sync. Check the volume and file types before deciding what to migrate and what to archive.
They do not travel with the opportunity sync. Products can be imported; price books need a custom object, available on Enterprise, or a pricing redesign in HubSpot.
Yes, if the HubSpot user matches an active Salesforce user's name and email. Create and check the users before migrating.
It depends on the volume, the custom objects and how much needs cleaning. Within an implementation it is planned inside the project's 3 to 4 months, with a full test before the cutover.
During the migration, yes, with the integration syncing. For the cutover, it is best to put Salesforce in read-only mode: two active systems end up with different data.
Designs the CRM architecture, integrations and operation of each account. He writes these guides from what he sees every week in HubSpot portals of B2B companies across Chile and Latin America.
Meet the teamWe review one concrete problem, its impact and your starting point. No demo and no access to your CRM.
