CRM and cold email tool field map
Thirteen fields mapped between a CRM and Instantly or Smartlead, with one owner per field so the two systems stop overwriting each other.
- Published in full
- No email required
- One owner per field
The short answer
- A CRM and a cold email tool stay in sync when every field has exactly one system that owns it and the other system only reads it.
- The CRM owns who the contact is and whether they may be emailed; the cold email tool owns send activity and the reply signal until it lands back in the CRM.
- Email address is the match key on both sides, and Smartlead requires it on every lead you add to a campaign.
- Suppression flows both ways: bounces and unsubscribes from the tool go into the CRM's suppression list, and the CRM's list goes to the tool's block list.
Why a CRM and a cold email tool drift apart
Drift starts when both systems can edit the same field. A rep fixes a job title in the CRM, the next CSV export overwrites it in the cold email tool, and a reply updates the tool but never reaches the CRM. After a month nobody trusts either one.
The fix is a written field map. For each field, you name the owner, the direction it flows, and the field name on each side. The map below uses the lead field names from the Instantly and Smartlead APIs, so you can hand it straight to whoever builds the sync.
The field map
Owner = the only system allowed to write the field. Arrows show the direction of sync.
| Field | CRM (SalesCrew Data Bank) | Instantly lead field | Smartlead lead field | Owner | Direction |
|---|---|---|---|---|---|
| CRM | CRM → tool (match key) | ||||
| First name | First name | first_name | first_name | CRM | CRM → tool |
| Last name | Last name | last_name | last_name | CRM | CRM → tool |
| Company | Company | company_name | company_name | CRM | CRM → tool |
| Job title | Job title | job_title | custom_fields.job_title | CRM | CRM → tool |
| Phone | Phone | phone | phone_number | CRM | CRM → tool |
| Website | Website | website | website | CRM | CRM → tool |
| LinkedIn profile | LinkedIn URL | custom_variables.linkedin_url | linkedin_profile | CRM | CRM → tool |
| Location | Location | custom_variables.location | location | CRM | CRM → tool |
| First line | AI field or custom field | personalization | custom_fields.first_line | CRM | CRM → tool |
| Segment | Batch tag or segment name | custom_variables.segment | custom_fields.segment | CRM | CRM → tool |
| Reply and interest | Reply label on the inbox thread | lt_interest_status | Reply webhook event | Tool, then CRM | Tool → CRM |
| Do not contact | Suppression list | Block list entry | Block list | CRM | Both ways |
Lead field names checked on developer.instantly.ai (Create lead) and api.smartlead.ai (Add leads to a campaign), September 2026.
Four rules that keep the map working
First, key on email and nothing else. Names change and companies get renamed, but the address is what both tools match on. Smartlead checks new leads against its block list and duplicates when you add them, and Instantly accepts a lead with only a name, so make email required in your sync.
Second, the CRM owns identity. Names, company, title and location are edited in one place, and the cold email tool gets a fresh copy when a contact enters a campaign. Third, the tool owns activity until it syncs. Sends and replies happen there, then land in the CRM as events on the contact.
Fourth, suppression has two owners by design. Whichever side learns about an unsubscribe or a bounce first writes it, and the other side copies it within the same sync. That's the only field where a two-way write is safe, because it only ever moves in one direction: toward "do not contact".
Setting up the sync with SalesCrew
The mechanism differs by tool. Both keep SalesCrew as the owner of the contact.
- 1
Instantly: registry sync and send provider
SalesCrew mirrors your Instantly sender and domain registry, so your sending mailboxes and domains sit beside your cadences with their daily caps. On the Outbound tier, Instantly is also a send provider for SalesCrew campaigns.
- 2
Smartlead: webhooks and the API
SalesCrew reaches Smartlead through outbound webhooks and the SalesCrew API or MCP, with Zapier, Make or n8n in the middle. Map the fields in that middle step using the table above.
- 3
Send the audience out
Freeze a Data Bank segment into an audience. Suppression runs at freeze, so only contacts you may email reach the cold email tool.
- 4
Bring replies back
Route the tool's reply and unsubscribe events back into SalesCrew. Replies land on the contact, and unsubscribes and bounces go onto the suppression list.
Keep the map beside the sync
Where the Data Bank fits
SalesCrew's Data Bank is the pool every audience comes from. A CSV import maps your columns in three steps, matches existing contacts on email, and fills blanks without overwriting values you trust. Suppression is checked at freeze and again at send, so a contact who unsubscribed in the cold email tool this morning stays out of this afternoon's cadence. See the Data Bank page and the Instantly integration for the detail.
Make the CRM the owner of every contact
Data Bank, suppression and webhooks on SalesCrew Core, $299 a month with unlimited seats.