Connect Salesforce or HubSpot
Import records, review updates to your existing CRM and resolve matching or sync errors.
You need an account that can authorize the external CRM connection and a Sotto administrator. Decide which fields to sync and which CRM takes priority when values differ.
Connect and import
Updates to the external CRM follow the write-back settings and the approved changes. When Write approved changes to HubSpot / Salesforce (under the connection cards) is on, only changes approved in Sotto are written to the connected CRM. When it is off, nothing is written even after approval, and changes stay in Sotto only. Only admins can change it, so check with your administrator before you start.
- Select the provider's connect button, such as Connect HubSpot, and authorize access.
- After returning, select the import button. Review the proposed differences before applying them.
- Check the counts for pending approval, records requiring a match and applied changes. Connection status also shows the last update sent to the external CRM.
Review changes sent to the external CRM
An approved Sotto update can produce a proposal to update Salesforce or HubSpot. Check the before-and-after values, confidence and reason before selecting the apply button.
When that setting is on, an inbox approval can also update the external CRM automatically. Check the update history for applied, skipped or failed changes. Failed operations may offer a retry.
Match an existing record
If a match is ambiguous, Sotto asks whether to link an existing record. Select the correct record or choose to create a new one. Review the customer before proceeding.
Choose the sync rules
The modes Read only, CRM wins, Sotto wins and Two-way control read-only access, CRM priority, Sotto priority or two-way syncing. Field mappings also determine which values are updated.
For a bulk historical import, use the CRM migration procedure.
Resolve a sync error
Open sync history, find the failed item and read the reason. Use a retry only when it is offered. If permissions or a field mapping must be fixed, update those first. Check whether the external CRM already received a change before retrying.
If the issue persists, send the details described in Contact support.