Workflow · Clean · Opening soon
Map fields between two systems
Use a data mapping template to line up HubSpot contact exports with Salesforce import columns. Your field mapping sheet drives the matches, and fields with no match are flagged.
Someone typed
“map our hubspot contact export to the salesforce import columns using my field mapping and flag fields with no match”
The agent read it as
map our HubSpot contacts export to the Salesforce import columns using my Field mapping sheet and flag fields with no match, keeping HubSpot values for fields marked map_to_picklist.
What the agent built
6 steps, each one an ordinary Mammoth step you can open and change.
File
HubSpot contacts export
CSV export · 14 rows
File
Field mapping sheet
CSV export · 14 rows
File
Salesforce import columns
CSV export · 14 rows
Step
Normalize mapping keys
Step 1
Step
Normalize import field keys
Step 2
Step
Expand contacts by field
Step 3
Join
Join field mapping
182 of 182 paired
Join
Join Salesforce import fields
154 of 182 paired
Step
Keep HubSpot picklist values
Step 6
Result
Salesforce Field Mapping
182 rows · 182 flagged
Schedule
Runs when you say
Proposed
- FileHubSpot contacts exportCSV export · 14 rows
- FileField mapping sheetCSV export · 14 rows
- FileSalesforce import columnsCSV export · 14 rows
- StepExpand contacts by fieldStep 3
- StepNormalize mapping keysStep 1
- StepNormalize import field keysStep 2
- JoinJoin field mapping182 of 182 paired
- JoinJoin Salesforce import fields154 of 182 paired
- StepKeep HubSpot picklist valuesStep 6
- ResultSalesforce Field Mapping182 rows · 182 flagged
- ScheduleRuns when you sayProposed
Checked on the sample files: every step ran, 182 rows came out, and the join paired 182 of 182 rows; the join paired 154 of 182 rows.
- Download HubSpot contacts export sample (14 rows)HubSpot: Contacts > Contacts > Export view
- Download Field mapping sheet sample (14 rows)Spreadsheet used by operations team: HubSpot to Salesforce field map
- Download Salesforce import columns sample (14 rows)Salesforce: Setup > Object Manager > Contact > Fields & Relationships > Export field names
What you get back
The result of that run, the rows to look at first.
Salesforce Field MappingSample data182 rows
154 mapped28 no match
| Contact ID | Salesforce field | Status | Salesforce value | HubSpot property | Salesforce API name | Salesforce data type | Required | Field length | Picklist values |
|---|---|---|---|---|---|---|---|---|---|
| c_10421 | · | No match | 2026-10-02 00:00:00 | Create Date | · | · | · | · | · |
| c_10421 | · | No match | 2026-11-05 00:00:00 | Last Activity Date | · | · | · | · | · |
| c_10422 | · | No match | 2026-10-04 00:00:00 | Create Date | · | · | · | · | · |
| c_10422 | · | No match | 2026-10-28 00:00:00 | Last Activity Date | · | · | · | · | · |
| c_10423 | · | No match | 2026-10-07 00:00:00 | Create Date | · | · | · | · | · |
| c_10423 | · | No match | 2026-11-07 00:00:00 | Last Activity Date | · | · | · | · | · |
| c_10424 | · | No match | 2026-10-10 00:00:00 | Create Date | · | · | · | · | · |
| c_10424 | · | No match | 2026-10-30 00:00:00 | Last Activity Date | · | · | · | · | · |
| c_10425 | · | No match | 2026-10-14 00:00:00 | Create Date | · | · | · | · | · |
| c_10425 | · | No match | 2026-11-03 00:00:00 | Last Activity Date | · | · | · | · | · |
| c_10426 | · | No match | 2026-10-18 00:00:00 | Create Date | · | · | · | · | · |
| c_10426 | · | No match | 2026-10-22 00:00:00 | Last Activity Date | · | · | · | · | · |
How do you map a HubSpot contacts export to Salesforce import columns?
Export your HubSpot contacts and your Salesforce import columns, then load your field mapping sheet. The workflow normalizes the field names, matches each HubSpot field to the Salesforce column you set, and flags fields with no match. For fields marked map_to_picklist, it keeps the HubSpot values.
How it works
How to use the Salesforce Field Mapping workflow
- 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and checked on the sample files.
- 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
- 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.
Salesforce Field Mapping: questions
Which export should you use?
Use a HubSpot contacts export and the Salesforce import columns export or file. The workflow reads those exported files and matches them against your field mapping sheet.
What happens to rows that do not match?
Rows or fields that do not find a match are flagged as no match. They stay in the output so you can review them and decide what to map.
How do you change the rules?
Edit the field mapping sheet in words, then run the workflow again. Change the source field, target field, or map_to_picklist rule to update how values are matched.
Get early access to this workflow
It will open already built and checked on the sample files. Swap in your own exports and see your result.
Workflows like this
Remove duplicate rows, catch invoices paid twice, match messy names to a master list, standardise spellings and turn wide tables long.
- Pivot table from raw dataTurn a raw sales export into a pivot table of revenue by region and month.See the workflow Built by the agent
- Remove duplicatesOne row of each, with a Copies column saying how many there wereSee the workflow Template
- Match names to a master listEach record with its master name (and ID), and how it matchedSee the workflow Template
- Compare two listsCompare two exported spreadsheet lists by email, see matches, and label rows where name and email agree or differ.See the workflow Built by the agent
- Duplicate invoice checkPairs of bills that look paid twice: same supplier, same amount, close dates or the same numberSee the workflow Template
- Standardise namesA Standard name for every row, so spellings of the same name group togetherSee the workflow Template