How Conversion works with Salesforce
Conversion connects to Salesforce through a managed package and a two-way sync. Leads and contacts become Conversion contacts, accounts become companies, and campaign membership stays aligned in both directions. Opportunities and their contact roles sync in read-only, and you choose field by field which system wins when both change.
What syncs
| Data | Direction | Details |
|---|---|---|
| Leads and contacts | Two-way | Sync in as Conversion contacts. New Conversion contacts can create Salesforce leads or contacts, your choice. |
| Accounts | Two-way | Sync in as companies. New contacts can match existing accounts by email domain or create new ones. |
| Campaigns and members | Two-way | Link to an existing Salesforce campaign or create one. Member statuses sync both ways. |
| Opportunities and contact roles | Into Conversion | Read-only. Stage, amount, and contact roles appear on records and in email personalization. |
| Custom objects | Into Conversion | Read-only and related to contacts. Enabled per workspace by the Conversion team. |
| Tasks and lead queues | Out of Conversion | Workflow steps create Salesforce tasks and assign leads to queues. |
How to connect Salesforce
- 1 Install the Conversion managed package in your Salesforce production org or sandbox.
- 2 Connect from Conversion settings with OAuth, using a system administrator or a dedicated integration user with the Conversion permission set.
- 3 Choose which objects sync in, whether Conversion can write back, and whether new contacts create leads or contacts.
- 4 Review field mappings and set a sync mode for each field, then let the initial import run.