Salesforce to HubSpot Smart Transfer Guide

What Smart Transfer is (and isn’t)

Smart Transfer is a one-way migration into HubSpot with a structured flow: Audit → Configure → Sync → Optional post-sync transfer → Cleanup.

A few realities you need to know up front:

• Access: only Super Admins can run Smart Transfer.
• Custom field mappings: transferring custom field mappings requires a Data Hub subscription.
• Custom objects: Smart Transfer does not transfer Salesforce custom objects.

If your Salesforce org is heavily custom-object-driven, you’ll likely need an additional approach. For standard CRM objects and core activity history, Smart Transfer is usually the cleanest and fastest path.

‍

Is Smart Transfer the right path for your Salesforce migration?

Most Salesforce to HubSpot migrations stall not on moving data, but on discovering too late that something will not come across. Smart Transfer is the fastest path for standard CRM objects and core activity history. Where your Salesforce org leans on custom objects or encrypted fields, it needs a second route planned upfront.

The decision is rarely “Smart Transfer or a different tool.” It is “Smart Transfer for the standard model, plus a named plan for the rest” — and that plan belongs in the audit, before the first sync, not in the troubleshooting phase.

Salesforce → HubSpot mapping you must understand

Smart Transfer follows a defined mapping. Here’s the important part for Salesforce migrations:

• Accounts → Companies
• Contacts → Contacts
• Leads → Contacts (important nuance)
• Opportunities → Deals
• Email Messages → Email activities
• Events → Meetings
• Tasks → Tasks
• Notes → Notes
• Cases → Tickets

Associations you’ll get (if the source data supports it):

• Contacts link to Companies via Salesforce “Account Name”
• Deals link to Companies via Salesforce “Account Name”
• Contact ↔ Deal links can come from “Opportunity Contact Roles”
• Tickets link to Companies/Contacts via Case fields

‍

Leads don’t become “HubSpot Leads”

This is where teams get tripped up: Salesforce Leads migrate into HubSpot as Contacts, not as a separate “Lead object.”
So your “Lead vs Contact” distinction becomes a classification problem in HubSpot (lifecycle stage, lead status, source markers), not an object boundary.

‍

Pre-flight checklist (do this before you click Transfer)

You’ll save days by deciding these five things upfront:

1) Define your migration scope

Start with what people actually need Day 1:

• Companies, Contacts, Deals
• Notes, Meetings, Tasks, Email activities
• Tickets only if Cases matter to your CS motion

Avoid migrating “everything because we can.” That’s how portals get bloated.

2) Decide how you’ll handle “Lead context”

Since Salesforce Leads turn into HubSpot Contacts, you need a simple rule to preserve meaning:

• Keep a clear “origin” marker (e.g., marketing lead vs product trial vs outbound)
• Make lifecycle stages and lead status the language your teams use consistently

3) Confirm users/owners are ready

Ownership chaos after a migration kills adoption. If you want reps and teams mapped correctly, ensure HubSpot users exist and your team structure is agreed before syncing large volumes. Team/user issues are a common Smart Transfer error category.

4) Multi-currency check

If you use multiple currencies, enable multi-currency in HubSpot before you configure the transfer. Otherwise, configuration can fail with currency import errors.

5) Know what won’t migrate

Some Salesforce field types are not supported (e.g., encrypted, calculated, reference-style fields). If any of those contain critical info, plan a separate archive/export strategy.

Step 1: Access Smart Transfer

In HubSpot, go to Data Management → Data Integration → Transfer data, find Salesforce, and start the transfer. Smart Transfer provides a “User Guide” checklist view and a “Smart Transfer” tab for individual steps.

Step 2: Run the audit (don’t skip this)

Click Audit my data.

The audit is your migration X-ray. It shows:

• how Salesforce objects map to HubSpot objects
• record counts per object
• pipelines/stages/fields and whether fields are supported
• extra config items like users, currencies, date formats

What I look for in the audit:

• record volume surprises (e.g., way more leads than expected)
• fields that won’t transfer cleanly (you’ll need a workaround)
• pipeline complexity (do you actually want 7 pipelines mirrored into HubSpot?)

You can run a second audit later and compare changes—useful if Salesforce is still “alive” while you prepare the move.

‍

Step 3: Configure transfer (this is where migrations succeed or fail)

Click Transfer my data / Configure your data.

This step prepares your HubSpot portal by creating the framework needed for the migration. You control which:

• properties
• pipelines and stages
• currencies
• users
  get created in HubSpot.

Important: Smart Transfer may automatically create supporting workflows during configuration to handle model differences. Those workflows are turned on after configuration.
For Salesforce specifically, configuration can create a deal create date backfill workflow to align HubSpot create dates with Salesforce “Created Date.”

My best practice: don’t auto-sync on your first run

During configuration, HubSpot offers an Automatically sync toggle. It’s recommended by default—but if you need filters or want to confirm mappings before pulling records, turn it off to avoid transferring unwanted data.

Then:

1. Select the objects and data types you want.
2. Select which properties to transfer (be intentional).
3. Review what will be created.
4. Start the configuration transfer.
5. Download the error log if needed.

‍

Step 4: Sync your records

After configuration, click Sync my data.

This starts the actual record sync. Depending on volume, it can take hours. HubSpot will notify you when it’s done.

Pragmatic rollout tip: Treat the first sync like a pilot. Validate key records, then expand scope if necessary.

‍

Step 5: Post-sync transfer (one-time extras)

Some Salesforce data types can be pulled via a one-time post-sync transfer, not ongoing sync.

For Salesforce, Smart Transfer supports:

• Attachments
• Campaign lists (based on Campaign Membership)

Important nuance: post-sync transfers do not stay continuously updated. They’re a one-time pull.

‍

Step 6: Cleanup (remove “migration artifacts”)

Smart Transfer includes a cleanup stage to mark empty properties for deletion and clean up empty properties (including removing transfer-specific workflows and archiving empty properties you don’t need long-term).

This is the step most teams skip—and then complain their portal feels “bloated.”

‍

Troubleshooting: the sync errors you’ll actually see (and how to fix them fast)

Sync errors are normal. The difference between a clean migration and a painful one is having a repeatable triage routine.

‍

Property mapping errors

If Smart Transfer can’t create custom mappings, the recommended pattern is: revert and retry configuration.
If a property is “already present in default mappings,” you can usually ignore it—HubSpot will use the default mapping property.

Attachment errors

If an attachment can’t transfer because the associated record wasn’t migrated, sync the associated record first, then rerun the post-sync step.

Currency errors

If multi-currency isn’t active, configuration won’t work. Enable multi-currency, add required currencies, then revert and rerun the configuration step.

Team/user errors

If a user wasn’t migrated into HubSpot, they can’t be assigned to a team. Fix users first, then revert and rerun the configuration step for users/teams.

Workflow creation errors

If workflow creation fails because required properties/options are missing, add what’s missing and rerun configuration (often via revert + rerun).

Your “undo button”: Revert transfer (use it intentionally)

If you mis-scoped configuration or created unwanted properties/pipelines/users/workflows, you can revert the transfer. Reverting can remove updated settings and delete records created by the configure transfer action (and related post-sync created records).

Two key limits:

• revert only rolls back Smart Transfer changes
• it can’t delete records that were synced via a standard sync connection outside Smart Transfer

This is why I recommend running the first pass as a controlled pilot.

‍

Post-migration validation (the checklist that prevents “CRM theater”)

Before you call the migration “done,” validate reality—not row counts.

‍

1) Associations

Spot-check:

• contacts correctly linked to companies
• deals linked to companies
• contact roles connected to deals where expected
• tickets linked correctly if you migrated cases

2) Activity history

Pick 10 high-value accounts and confirm you can see what matters:

• notes
• meetings
• tasks
• email activities

3) Pipeline usability

Smart Transfer can mirror structure—but you still need a usable HubSpot pipeline design.
Don’t perfect this mid-migration. Migrate first, consolidate second.

4) Field sanity

Check for:

• fields that didn’t come over due to unsupported types
• accidental duplicates caused by “same label, different meaning”
• required fields missing in HubSpot that your processes rely on

5) Adoption guardrails

Lock down:

• who can create properties
• who can create pipelines
• who can edit stage logic
  Otherwise the portal drifts immediately post go-live.

‍

Best practices (the no-bull*hit version)

• Pilot first: validate with a controlled run before turning on automatic sync everywhere.
• Keep scope tight: migrate what people use, not what exists.
• Plan lead handling: Salesforce Leads → HubSpot Contacts means you must preserve “lead meaning” via process, not objects.
• Use post-sync deliberately: attachments and campaign lists are one-time pulls—treat them like an archive import, not a living sync.
• Clean up after: remove empty properties and transfer artifacts so HubSpot stays fast and usable.
• Keep revert in your back pocket: especially in a production portal.

‍

SalesPlaybook is a HubSpot Diamond Solutions Partner with 39+ five-star reviews in the HubSpot Solutions Directory, and runs Salesforce-to-HubSpot migrations for B2B software companies in the DACH region. What that is worth at the end is in the Workist case study: "We save approximately €200,000 every year—not only through fewer, better technologies, but also by eliminating complexity and the staffing cost of one full role." The move took under 3 months.