Mapping Export Fields So They Land in the Right CRM Columns
Choose which fields go out, in what order, and what each key is called in the destination.
Every CRM names its columns differently, and a lead that exports cleanly to HubSpot can still land in the wrong fields in Notion if the key names don't match what that destination expects. Export settings exist so you set the mapping once per destination instead of fixing it after every export.
Order and visibility
Each destination (CSV, webhook, Notion, HubSpot, Google Sheets) keeps its own field list. Turn a field off if the destination doesn't need it — a webhook endpoint that only wants email and company doesn't need the full experience summary riding along. Reorder fields to match the column order you actually read in that destination.
Renaming keys
Some CRMs already have a property called job_title; others call it position or role. Rename the exported key per field, per destination, so it matches the property your CRM already has instead of creating a duplicate column every time you export.
Test before a bulk export
Send a test lead pushes a single record through the current mapping, so you can check it landed in the right columns with the right names before running it across a full list of leads from the leads table.