Exante syncs three core Salesforce objects through Merge’s unified CRM API. Data flows inbound only — from Salesforce into Exante.
Accounts to parties
Salesforce accounts are synced as Exante parties (companies).
| Salesforce field | Exante field | Notes |
|---|
| Name | Party name | Required |
| Description | Metadata | Stored in integration metadata |
| Industry | Metadata | Stored in integration metadata |
| Website | Metadata | Stored in integration metadata |
| Salesforce field | Exante field | Notes |
|---|
| First name + Last name | Contact name | Combined into a single name |
| Email | Contact email | Primary email from Salesforce |
| Phone | Contact phone | Primary phone from Salesforce |
| Account | Party link | Contact is attached to the synced party |
Contacts are only synced if their parent account has already been synced. Orphaned contacts (without an account) are skipped.
Opportunities to documents
Salesforce opportunities are synced as Exante documents with deal metadata.
| Salesforce field | Exante field | Notes |
|---|
| Name | Document name | Opportunity name |
| Amount | Metadata | Stored as integer (cents) in integration metadata |
| Status | Metadata | OPEN, WON, or LOST |
| Stage | Metadata | Pipeline stage name |
| Close date | Metadata | Expected or actual close date |
| Account | Party link | Opportunity linked to the synced party |
Sync behavior
| Behavior | Detail |
|---|
| Sync direction | Inbound only (Salesforce to Exante) |
| Initial sync | Full import of all accounts, contacts, and opportunities |
| Incremental sync | Webhook-triggered when Merge completes a sync cycle |
| Polling safety net | Periodic polling catches any events missed by webhooks |
| Sync order | Accounts first, then contacts, then opportunities |
| Duplicate handling | Merge IDs used for deduplication; existing records are updated |
| Deletion | Deleted Salesforce records are not automatically removed from Exante |
