TLDR
- HubSpot Salesforce field mapping decides where each Salesforce object, field and relationship lands in HubSpot. The four big objects map cleanly. The relationships around them are where data gets lost.
- Leads and contacts both become HubSpot contacts, accounts become companies, opportunities become deals and cases become tickets. Contact roles, record types, formula fields, campaign members and files all need a decision first.
- Some targets depend on your HubSpot tier. Custom objects need Enterprise. The Leads object, association labels and calculation properties need Professional or Enterprise.
- Lookups and junction objects become associations, and association labels carry the role a record played. Without them, a deal shows five contacts and nobody knows who signed.
- Write every decision into a field mapping workbook and test it with a real working day before cutover. An import that passes record counts can still leave the team unable to work.
Salesforce and HubSpot organize CRM data differently, so migrating records requires more than matching fields between the two platforms.
Leads and contacts, opportunities and accounts have straightforward equivalents in HubSpot. But Salesforce record types, contact roles, formula fields and custom objects often need additional configuration.
Without proper field mapping, records may transfer successfully while important relationships, calculations and reporting details are lost.
This guide explains how to map Salesforce objects and fields to HubSpot, which features require specific HubSpot subscriptions, and how to document and test your mapping before migration. If you still need the full migration process, start with our Salesforce to HubSpot migration guide. If you plan to keep both CRMs and sync them, the HubSpot Salesforce integration guide covers sync rules and API limits.
Why Salesforce objects do not map one to one
Salesforce and HubSpot model the same business in different ways, so a field mapping is a translation, not a copy. Salesforce stores a lot of meaning in structure: separate lead and contact objects, record types, junction objects and formula fields. HubSpot stores more of it in a smaller set of standard objects, properties, pipelines and labeled associations.
Three differences drive most of the mapping decisions:
- Relationships. Salesforce links records with lookup and master-detail fields, and uses junction objects such as Opportunity Contact Role and Campaign Member to describe a role. HubSpot links records with associations, and association labels describe the role.
- Process variants. Salesforce uses record types to give one object several page layouts, picklists and sales processes. HubSpot usually expresses the same thing with separate pipelines or a property.
- Logic in fields. Formula and roll-up summary fields calculate on the fly in Salesforce. Their values can be exported, but the formula does not travel. In HubSpot, the logic has to be rebuilt as a calculation or rollup property, or retired.
The practical rule is to map the business meaning, then the data. For every Salesforce object, ask what the team actually uses it for today, then choose the HubSpot structure that does that job. Our CRM migration services page reports that a typical mid-market portal migration retires 30% to 60% of custom properties, so expect the mapping to shrink the data model, not copy it.
Salesforce to HubSpot object mapping
Most Salesforce objects have a natural home in HubSpot, but about half of them need a decision before you import. The table below covers the objects a B2B sales, marketing and service team usually holds. The HubSpot tier column shows what you need for the target to exist, based on HubSpot's Knowledge Base as of November 2026.
| Salesforce object | HubSpot target | HubSpot tier needed | Decision to make first |
|---|---|---|---|
| Lead | Contact, plus an optional Lead record | Contacts on all tiers. Leads object needs Sales Hub Professional or Enterprise | Whether open leads become Lead records or only a lifecycle stage and lead status |
| Contact | Contact | All tiers | Which email address wins when a lead and a contact share one |
| Person Account | Contact, with or without a company | All tiers | Whether B2C buyers get a company record at all |
| Account | Company | All tiers | The deduplication field (usually domain) and how parent accounts are kept |
| Opportunity | Deal | All tiers. Pipeline limits depend on your Sales Hub tier | Which pipeline each record type goes to |
| Opportunity Contact Role | Deal to contact association with a label | Labels need Professional or Enterprise | Which roles you keep and what each label is called |
| Opportunity Line Item, Product, Price Book | Line item and product library | Product library on all plans. Tiered pricing needs Revenue Hub | How several price books collapse into one product library with a price per currency |
| Case | Ticket | All tiers. Check ticket pipeline limits for your Service Hub tier | Which case record types become separate ticket pipelines |
| Campaign and Campaign Member | Campaign, plus a property or list for members | Campaigns object needs Marketing Hub Professional or Enterprise | Whether member status history is needed after go-live |
| Task, Event, Email, Call | Activities on the timeline | All tiers | How many years of history to bring, and the owner of activities by people who have left |
| Note, Attachment, File | Notes and files on the record | All tiers | Which files matter and how to keep links to the original record |
| Formula and roll-up summary fields | Calculation or rollup property, or a static value | Calculation properties need Professional or Enterprise | Rebuild the logic, keep a frozen value or retire it |
| Custom object | Custom object, or a standard object plus properties | Custom objects need Enterprise | Whether the object is still used weekly |
| User, Queue, Role | Users, teams and owner properties | All tiers | Who owns records from inactive users |
Sources: HubSpot Knowledge Base on leads, association labels, products, campaigns, custom objects and calculation properties. Tier requirements change often, so check them against your own subscription.
Leads, contacts and person accounts
Salesforce leads and contacts both become HubSpot contacts, because HubSpot keeps one record per person. The decision is what happens to the lead stage in between. Salesforce marks it by object, so a person is a lead until conversion. HubSpot marks it with the lifecycle stage and lead status properties on the contact.
You have two ways to map open Salesforce leads:
- Contact plus lifecycle stage. Every lead becomes a contact, and its lead status and lifecycle stage carry where it stands. This is the simplest model and works on every tier.
- Contact plus a Lead record. HubSpot's Leads object, available on Sales Hub Professional and Enterprise, tracks prospecting work as its own record. According to HubSpot's leads documentation, a lead "cannot exist on its own" and must have a primary association with a contact or a company. Use it when your SDR team works leads through stages and you want that history kept apart from the contact.
Either way, map Salesforce Lead Status to a defined value, not a copy of whatever text was in the picklist. If marketing and sales never agreed what each status means, the migration is the moment to fix it. Our post on sales and marketing alignment in HubSpot covers how to define lifecycle stages and lead status before you build.
Duplicates between leads and contacts. The same person often exists as an unconverted lead and as a contact. HubSpot matches people by email address, so two Salesforce records with one email become one HubSpot contact. Decide in advance which record's values win, usually the contact, and merge in Salesforce before you export. Our guide to HubSpot deduplication covers the merge rules on the HubSpot side.
Person accounts. HubSpot has no person account. Each one becomes a contact, and the question is whether it also needs a company record. For B2C buyers the answer is usually no. If your reports group revenue by company, plan how those contacts appear in them, because a person account without a company will not show up in company-level reporting.
Accounts, opportunities and contact roles
Accounts map to companies and opportunities map to deals, and both mappings are simple until you look at the relationships around them. Those relationships are what reps and finance actually rely on.
Accounts to companies. Pick the field HubSpot will use to match companies before you import. HubSpot deduplicates companies on an exact match, and its account sync documentation notes that a similar account name does not guarantee a match. Domain is the usual choice, so clean blank and malformed websites first. Keep the Salesforce Account ID in a custom property on every company. It is your audit trail and your key for associating everything else.
Parent accounts. If you use account hierarchies, map the Parent Account lookup to a company to company association, not a text field. A text field shows the parent's name but cannot roll up deals or revenue across the group.
Opportunities to deals. Each opportunity becomes a deal, and each Salesforce sales process becomes a HubSpot pipeline with its own stages. Map stages by meaning, not by name. If two Salesforce stages mean the same thing to the team, merge them. If one stage hides two real steps, split it and give each a clear exit criterion. Watch currency too. HubSpot's opportunity sync documentation states that the integration copies only the numeric value of a currency field and applies no exchange rate, so multi-currency orgs need the currency code mapped alongside the amount.
Opportunity contact roles. This is the relationship most migrations lose. In Salesforce, Opportunity Contact Role is a junction object that says who the decision maker, economic buyer or champion was on each deal. If you import deals and contacts with plain associations, the contacts arrive but the roles do not. In HubSpot, the role belongs on the association itself, as an association label. HubSpot allows up to 50 labels per object pair on Professional and Enterprise, so you can recreate every role you actually use.
| Salesforce relationship | HubSpot equivalent | What breaks if you skip it |
|---|---|---|
| Opportunity Contact Role (Decision Maker, Economic Buyer) | Deal to contact association with matching labels | Reps cannot see who signed, and win/loss analysis by role is gone |
| Primary contact on an opportunity | A "Primary" label on one deal to contact association | Sequences and renewal tasks go to the wrong person |
| Account Contact Relationship (one contact, several accounts) | Contact to company associations with labels such as Former Employee or Billing Contact | Contacts appear under only one company |
| Parent Account | Company to company association (Parent and Child labels) | No rollup of revenue across a group of companies |
Create the labels before you import, then load the associations in a separate pass that references both records by their Salesforce IDs.
Record types, picklists and formula fields
Record types, picklists and formula fields are where a mapping that looks finished on paper fails in daily use. Each needs a rule, not just a target column.
Record types. A record type usually means a different process, so map it to a HubSpot pipeline when the stages differ and to a property when only the fields differ. New business, renewal and upsell opportunities with different stages become three deal pipelines. Two case types that follow the same steps become one ticket pipeline with a Case Type property. Keep the original record type name in a property either way, so historical reports still work. If you keep both CRMs connected during a phased move, note that HubSpot names synced pipelines after the Salesforce record type ID, according to its opportunity sync documentation.
Picklists. Salesforce picklists become HubSpot dropdown select properties, and multi-select picklists become multiple checkbox properties. Map the internal values, not only the labels, and decide what happens to inactive values that still sit on old records. Dependent picklists have no direct equivalent, so list each one and decide whether it is rebuilt with conditional logic on forms and record views or retired.
Field types. Most types translate directly. These need a rule:
| Salesforce field type | HubSpot property type | Rule to set |
|---|---|---|
| Text Area (Long) and Rich Text | Multi-line text, or a note on the timeline | Long free text that nobody reports on reads better as a note |
| Currency | Number formatted as currency | Map the record's currency code in multi-currency orgs |
| Lookup to another object | Association | Never import a lookup as a text field |
| Formula | Calculation property, or a static number or date | Rebuild live logic, freeze historical values |
| Roll-up summary | Rollup property | Check the source object can be associated first |
| Auto Number | Single-line text | Keep it as a legacy reference, not a new ID |
| Geolocation and encrypted fields | Text, or not migrated | Agree with security which values may leave Salesforce |
Formula and roll-up fields. The formula does not travel. Only the value on the day you export it does. For each one, decide whether the business still needs it live. If yes, rebuild it as a HubSpot calculation or rollup property, available on Professional and Enterprise. Rollups can count, sum or average values from associated records, and can be limited to records with a specific association label. If the value is only needed for history, import it once as a static property and label it clearly. Contract start dates and ARR fields are the usual casualties, so check them with finance before you sign off the mapping.
Custom objects and lookups
A Salesforce custom object should become a HubSpot custom object only when the team still uses it as a separate thing with its own records and its own lifecycle. Otherwise it usually fits as properties on a standard object, which keeps you off a tier you may not need. HubSpot custom objects require an Enterprise subscription, and each one needs a primary display property that names its records.
Ask three questions of every custom object:
- Does anyone open these records weekly? If not, export them to an archive and leave them out.
- Is it one-to-one with a standard object? A Contract object with exactly one record per account is really a set of company properties.
- Does it have its own stages or many records per parent? Subscriptions, assets, installed equipment and projects usually do, so they earn a custom object.
Lookups and master-detail fields become associations. In Salesforce, a child record points to its parent through a lookup field. In HubSpot, the two records are associated, and the association can carry a label. HubSpot's custom object sync documentation is explicit that lookup fields on custom objects cannot be field-mapped and have to come across as associations instead. The same logic applies to a one-time import. Load the records first, then load the associations in a second pass using the Salesforce IDs on both sides.
Junction objects. A Salesforce junction object that only links two records, such as a Project Contact object with a Role field, becomes a labeled association, not a custom object. If the junction object holds real data of its own, like hours or dates, it may still need to be a custom object.
When your custom objects depend on logic that HubSpot's standard tools cannot hold, such as calculations across several objects or a sync to an ERP, a custom integration can keep that logic outside the CRM and write the result back.
Products, campaigns, activities and files
The objects around the core four decide whether history still makes sense after go-live. They are also the ones most often left for "phase two" and then forgotten.
Products, price books and line items. Salesforce products become items in HubSpot's product library, and opportunity line items become line items on deals. Price books are the hard part. HubSpot keeps one product library and stores a price per currency on each product, according to its products documentation, so several regional or partner price books need a rule: separate products, a price per currency, or discounts applied on the line item. Import line items with the price that was actually sold, not today's list price, or historical deal amounts stop matching. If quoting rules, approvals and bundles are part of the move, treat them as their own project. Our CPQ implementation team handles that side.
Campaigns and campaign members. Campaign Member is another junction object, with a status such as Sent or Responded for each person. HubSpot campaigns are available on Marketing Hub Professional and Enterprise, and they group marketing assets rather than store a status per contact. Decide which campaign history the team still reports on. Members of those campaigns are usually kept as a static list per campaign or a contact property such as Original Salesforce Campaign, with the member status in a second property.
Tasks, events, emails and calls. These become activities on the record timeline. Agree how many years to bring, because activity volume is usually far larger than record volume. Map the activity owner and the associated records, and decide who owns activities logged by people who have left. Load activities last, after every record they attach to exists.
Notes, attachments and files. Files are easy to forget and painful to lose, especially contracts and signed order forms. In our FlexKey migration, we moved 7,976 files and attachments out of Salesforce, along with Chatter messages and comments. Map every file to the HubSpot record that replaces its Salesforce parent, and keep the Salesforce record ID in a property so anyone can trace a file back.
Users, queues and owners. Owner fields only map cleanly when every Salesforce user has a matching HubSpot user. Build the user map first. Queues usually become HubSpot teams, and records owned by inactive users need a named new owner before import, not after.
How to build and test your field mapping
A field mapping is finished when someone who was not in the room can read it and know exactly where every value goes and why. That means one workbook, one row per field, signed off by the people who use the data.
The workbook. Give each Salesforce object its own tab, with these columns:
| Column | What goes in it |
|---|---|
| Salesforce object and field API name | The exact source, for example Opportunity.Contract_Start__c |
| Field type and sample values | What the data really looks like, including blanks |
| Used by | The team or report that relies on it. Blank means candidate for retirement |
| HubSpot object and property | The internal name of the target property |
| Transformation rule | Value mapping, format change, merge or split |
| Decision | Migrate, rebuild as calculation, freeze as static value, or retire |
| Owner | The person who signs off this row |
The load order. Records have to exist before anything can attach to them:
- Users and owner map
- Companies, with the Salesforce Account ID
- Contacts, with Lead ID and Contact ID
- Deals, line items and tickets
- Custom object records
- Associations and labels between all of the above
- Activities, notes and files
When HubSpot's native import is enough. For a small org with standard objects and clean data, HubSpot's built-in Salesforce import can bring in leads, contacts, accounts, opportunities, tasks, cases, events, a campaign and custom objects. It runs through the Salesforce integration and its sync settings, though, so read how it treats each object first. For leads and contacts, HubSpot notes that only the email address syncs at import, and other fields follow only for records allowed by your inclusion settings. Once you need contact roles, record type logic, frozen formula values or files, a scripted import or a migration tool gives you more control.
Test with a real working day. Record counts prove the data moved. They do not prove the team can work. Before cutover, load a sample into a HubSpot sandbox or test portal and ask each team to run its normal day on it:
- An account executive opens five live deals and finds the decision maker, the products sold and the next step.
- A service lead opens open tickets from two former case record types and confirms they sit in the right pipeline.
- Finance pulls last quarter's closed-won revenue and gets the same number Salesforce gives.
- Marketing checks that campaign history and lead status still answer the questions they report on.
If any of these fail, fix the mapping, not the data in HubSpot. A fix made by hand after go-live is a fix nobody can repeat.
How Elefante RevOps helps
We run Salesforce to HubSpot migrations for B2B revenue teams with $10 million to $500 million in revenue. As a HubSpot Diamond Partner with HubSpot's Data Migration accreditation, and a Salesforce Consulting Partner, we work on both sides of the mapping, so a Salesforce record type or junction object gets a HubSpot design that fits how your team sells today.
Every CRM migration starts with a 45-minute assessment of your current CRM and your three highest-risk integration points. The Design phase produces a field-by-field mapping document that sales, operations and finance sign off together, because we map fields by meaning, not by name. Before cutover we run a parallel migration test on production-scale data. If a check fails, the cutover stops. Every project includes a documented rollback plan, and across our last 12 migrations, 0 records were lost.
For UrbanBound, an HR tech SaaS company, we designed and delivered a full Salesforce to HubSpot migration in 12 weeks, with data mapping and a test migration before the full move. The UrbanBound case study reports 100% of historical Salesforce data migrated and 92% GTM-team adoption within the first 30 days.
If your mapping needs logic HubSpot cannot hold natively, our custom integrations team builds it. If quoting and price books are part of the move, our CPQ implementation team takes that piece. And if HubSpot is not the right fit for your data model, the assessment will say so before any work begins.
FAQ
What is HubSpot Salesforce field mapping?
HubSpot Salesforce field mapping is the set of rules that decides which HubSpot object and property receives each Salesforce field. In a migration it is a one-time translation documented in a mapping workbook. In an ongoing integration it also sets the sync rule for each field, which our HubSpot Salesforce integration guide covers.
Do Salesforce leads become HubSpot leads or contacts?
Every Salesforce lead becomes a HubSpot contact, because HubSpot keeps one record per person. On Sales Hub Professional or Enterprise you can also create a record in HubSpot's Leads object for open leads your team is still working. A HubSpot lead must be associated with a contact or a company.
What happens to opportunity contact roles in HubSpot?
They become associations between the deal and each contact, and the role moves into an association label such as Decision Maker or Economic Buyer. Labels are available on Professional and Enterprise, with up to 50 per object pair. If you import plain associations, the contacts arrive on the deal but the roles are lost.
Do I need HubSpot Enterprise to migrate Salesforce custom objects?
You need Enterprise only if the data must stay a separate custom object in HubSpot. Many Salesforce custom objects turn out to be one-to-one with an account or opportunity and fit as properties on a standard object. Others are junction objects that become labeled associations.
Do Salesforce formula fields migrate to HubSpot?
The value migrates, but the formula does not. You can rebuild the logic as a HubSpot calculation or rollup property on Professional or Enterprise, or import the value once as a static property when it is only needed for history.
How do Salesforce record types map to HubSpot?
Record types that follow different stages usually become separate HubSpot pipelines. Record types that only change the fields shown usually become a property. Keep the original record type name in a property so historical reports still work.
Can HubSpot's built-in Salesforce import handle the whole migration?
It can for a small org with standard objects and clean data. HubSpot's import covers leads, contacts, accounts, opportunities, tasks, cases, events, a campaign and custom objects through the Salesforce integration. Contact roles, record type logic, frozen formula values and files usually need a scripted import or a migration tool.

