Skip to content
Get a quote

Free CRM field mapping template

Pick the system you're leaving, then the one you're moving to. You get the researched field mapping for that pair, ready to download and adapt.

In short

A field mapping template lists each source field, where it lands in the new system and how the value changes. This tool has researched mappings for 148 migration pairs, downloadable as CSV, plus a blank template for any other pair. Free, no signup.

By

What the template covers5
  • Source object and field
  • Destination object and field
  • Mapping type for each field
  • Transformation rules
  • Notes on picklists and owners

Choose your migration

Salesforce to HubSpot · 48 fields mapped

Source fieldDestination fieldMappingNote
Lead.FirstNameContact.firstnamedirect
Lead.LastNameContact.lastnamedirect
Lead.EmailContact.emaildirect
Lead.PhoneContact.phonedirect
Lead.MobilePhoneContact.mobilephonedirect
Lead.TitleContact.jobtitledirect
Lead.CompanyContact.associatedcompanyidtransformedLead.Company creates or links to a HubSpot Company record; association is set on the Contact after the Company exists.
Lead.StatusContact.sf_lead_status__ccustom field requiredHubSpot has no Status field on Contact; we create a custom property to preserve the original Salesforce Lead Status value.
Lead.LeadSourceContact.hs_analytics_sourcevalue mappingSalesforce LeadSource pick-list maps to HubSpot's contact source property; unmapped values default to 'Other'.
Lead.IsConvertedContact.sf_was_converted_lead__ccustom field requiredHubSpot stores a boolean flag indicating the record was a converted Salesforce Lead.
Lead.CreatedDateContact.original_create_date__ccustom field requiredHubSpot's createdate is set at import time; original Salesforce CreatedDate preserved as a custom datetime property.
Lead.IdContact.source_system_id__ccustom field requiredSalesforce Lead ID stored on the HubSpot contact for traceability and delta-run de-duplication.
Contact.FirstNameContact.firstnamedirect
Contact.LastNameContact.lastnamedirect
Contact.EmailContact.emaildirect
Contact.PhoneContact.phonedirect
Contact.MobilePhoneContact.mobilephonedirect
Contact.TitleContact.jobtitledirect
Contact.AccountIdContact.associatedcompanyidtransformedSalesforce AccountId resolves to a HubSpot Company ID; the Company must be migrated before the Contact.
Contact.BirthdateContact.date_of_birth__ccustom field requiredBirthdate is not a native HubSpot property; migrated as a custom date property.
Contact.CreatedDateContact.original_create_date__ccustom field requiredOriginal Salesforce CreatedDate preserved as a custom datetime for reporting continuity.
Contact.LastModifiedDateContact.original_last_modified_date__ccustom field requiredOriginal Salesforce LastModifiedDate preserved as a custom datetime for delta-tracking.
Contact.IdContact.source_system_id__ccustom field requiredSalesforce Contact ID stored on the HubSpot contact for traceability and delta-run de-duplication.
Account.NameCompany.namedirect
Account.WebsiteCompany.domaindirect
Account.IndustryCompany.industryvalue mappingSalesforce Industry pick-list values mapped to HubSpot industry options; unmapped values mapped to 'Other'.
Account.NumberOfEmployeesCompany.numberofemployeesdirect
Account.AnnualRevenueCompany.annualrevenuedirect
Account.BillingStreetCompany.addressdirect
Account.BillingCityCompany.citydirect
Account.BillingStateCompany.statedirect
Account.BillingPostalCodeCompany.zipdirect
Account.BillingCountryCompany.countrydirect
Account.ParentIdCompany.parent_company_id__ccustom field requiredHubSpot does not have a native parent-company lookup; we create a custom property linking to the parent Company record.
Account.TypeCompany.company_type__cvalue mappingSalesforce Account Type values (Customer, Prospect, Partner) mapped to a HubSpot custom pick-list.
Account.IdCompany.source_system_id__ccustom field requiredSalesforce Account ID stored on the HubSpot company for traceability and delta-run de-duplication.
Opportunity.NameDeal.dealnamedirect
Opportunity.AmountDeal.amountdirect
Opportunity.StageNameDeal.dealstagevalue mappingSalesforce StageName values map to HubSpot pipeline stage IDs; each pipeline has its own stage set derived from a Salesforce record type.
Opportunity.CloseDateDeal.closedatedirect
Opportunity.RecordTypeIdDeal.pipelinetransformedSalesforce RecordTypeId determines which HubSpot pipeline the deal enters; each record type maps to one HubSpot pipeline.
Opportunity.ProbabilityDeal.sf_probability__ccustom field requiredHubSpot does not have a probability field; the original Salesforce probability is stored as a custom number property on the deal.
Opportunity.ForecastCategoryDeal.forecast_category__ccustom field requiredSalesforce forecast category (Commit, Best Case, Omitted) migrates as a custom pick-list on the HubSpot deal.
Opportunity.OwnerIdDeal.hubspot_owner_idtransformedOwner resolved by email match to HubSpot users; unmatched owners flagged before migration runs.
Opportunity.AccountIdDeal.associatedcompanyidtransformedSalesforce AccountId resolves to a HubSpot Company ID; the Company must be migrated before the Deal.
Opportunity.LeadSourceDeal.hs_analytics_sourcevalue mappingSalesforce LeadSource pick-list maps to HubSpot deal source property.
Opportunity.TypeDeal.deal_type__ccustom field requiredSalesforce Opportunity Type (New Business, Upsell, Renewal) migrates as a custom pick-list on the HubSpot deal.
Opportunity.IdDeal.source_system_id__ccustom field requiredSalesforce Opportunity ID stored on the HubSpot deal for traceability and delta-run de-duplication.

Moving between systems that aren't listed? Start from the blank field mapping template (CSV): the same columns plus data type, owner and status for tracking review.

How to use it

  1. Start from your pair

    Download the mapping for your source and destination, or the blank template.

  2. Add your custom fields

    Export your source schema and add every custom field and picklist the template doesn't list.

  3. Decide every transform

    Picklist values, owners, dates and record IDs need a rule each. Write it in the note column.

  4. Test on a sample

    Migrate a few hundred real records and check them in the new system before the full run.

Mapping types

DirectCopied as is; same type on both sides.
TransformChanged on the way: split, joined, reformatted or converted.
Value mappingPicklist or stage values matched one by one.
LookupA reference to another record, rebuilt as an association.
Custom fieldNo standard field exists; a custom property is created first.

Questions, answered

Field mapping questions

What is a field mapping template?

A spreadsheet that lists every field in the system you are leaving, the field it lands in on the new system, and how the value changes on the way: copied as is, transformed, looked up or dropped. It is the plan every CRM migration runs from.

Which columns should a CRM field mapping have?

Source object and field, destination object and field, mapping type (direct, transform, lookup, value mapping), the transformation rule, and a note for anything that needs a decision, such as picklist values, owners and record IDs.

Is this mapping complete for my account?

It covers the standard and most-used fields for each pair. Your custom fields and picklist values come from your own schema; we add those during scoping, or you can add them to the template yourself.

Is the template free?

Yes. No signup; the mapping and the CSV download are free to use for your own migration.

Get a quote

Want the mapping done for you?

We map every field, custom objects included, run a sample you approve, then migrate with one-click rollback.

Get a quote