Up to 70% off kits30% off services
CRM Field Mapping Template
Start from the standard fields for HubSpot ↔ Salesforce, Salesforce ↔ NetSuite, CRM ↔ QuickBooks or a Pipedrive → HubSpot migration, each with a recommended sync rule, a system of record and the reason. Change what doesn't fit, add your custom fields, and download the mapping as a CSV for your admin or developer.
Sync rules use the names in HubSpot's Salesforce connector settings. Salesforce is the usual system of record for sales fields; HubSpot for marketing fields.
Contact / Lead
| HubSpot field | Salesforce field | Sync rule | System of record | Why | Remove |
|---|---|---|---|---|---|
Company / Account
| HubSpot field | Salesforce field | Sync rule | System of record | Why | Remove |
|---|---|---|---|---|---|
Deal / Opportunity
| HubSpot field | Salesforce field | Sync rule | System of record | Why | Remove |
|---|---|---|---|---|---|
Every field has a direction and an owner. Nice.
Already synced and not sure what's mapped?30% OFF
A $349$499 sync audit reads your live mappings and rules, finds the fields that overwrite each other, and gives you this document filled in for your setup, credited toward the fix.
Frequently asked questions
Field mapping, systems of record and sync rules.
A table of every field that moves between two systems: the field name on each side, which direction it syncs, which system owns it (the system of record), and why. It is the first thing to write before connecting two tools, and the first thing to check when an existing sync misbehaves.
The one system whose value wins for a field. People edit the field there and nowhere else, and automation writes it there and nowhere else. A field without a system of record, synced two-way, is where most flip-flopping values and overwritten data come from.
Prefer Salesforce unless blank: Salesforce's value wins, unless it is empty and HubSpot has one. Always use Salesforce: Salesforce's value always wins in HubSpot. Two-way: the most recent change on either side wins. Don't sync: the field is not synced. Pick each one on purpose.
Yes. Add a row for each custom field, pick the rule and owner, and write down why. The download includes every row, so it can live in your wiki or go straight to whoever builds the integration.
No. The template lives in your browser tab and the CSV is created on your device. Close the tab and it is gone, so download it when you are done.
How to use a data mapping template
- List every field that must move. Start with what reports and handoffs need, not everything that exists. Fewer synced fields means fewer errors.
- Pick one system of record per field. Ask who edits it. Sales fields usually belong to the sales CRM, marketing fields to the marketing tool, money to accounting.
- Choose the sync rule to match. One-way for anything owned by one side. Two-way only for low-risk fields nothing automated writes.
- Check picklists and required fields. Unmatched picklist values and blank required fields cause most sync errors.
- Clean duplicates before the first sync. Our free CRM duplicate checker shows how many you have.