Settings → Integrations → Salesforce → OAuth as an integration user with API access. Map fields, choose sync direction, enable. First sync completes within an hour for most orgs.
Prerequisites
A Salesforce edition with API access (Enterprise or above, or Professional with the API add-on) and an integration user with read/write on Leads, Contacts, Accounts, and Opportunities. Use a dedicated integration user, not a personal login.
Connect and map
OAuth sign-in, then field mapping: turgo's canonical fields map to your SF fields with sensible defaults pre-filled. Review custom-field mappings carefully — that's where every org differs.
Sync configuration
Choose per-object direction (bi-directional recommended for Contacts/Accounts, SF-to-turgo for Opportunities), conflict rule (most-recent-wins default), and sync scope (all records vs filtered views).
Verify
After the first sync, spot-check 20 records both directions: fields landed correctly, no duplicate creation, activity logging appears on the SF timeline. The sync log shows any per-record failures with reasons.
