Attio
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
CRM · Two-way sync platform
Attio and Salesforce integration — two-way sync
Keep supported Attio and Salesforce records aligned with two-way sync. Give each team access to current data while controlling which system can update each field.
- Field mappings and sync direction under your control
- Inspect and resolve record errors in one dashboard
Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Example workflow
Company sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting eventA change involving Attio Companies or Salesforce Accounts needs a defined result in the other system.
Start with Attio Companies and Salesforce Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve parent organizations, business units, and currency references before dependent transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyUse two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Review records and field ownershipMapping essentials
Records and field ownership
Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.
Download the mapping worksheetCSV · No email required
| Attio record | Salesforce record | Record matching | Field ownership |
|---|---|---|---|
| CompaniesDocumented record: SupportedRecord matching | AccountsProposed record; confirm Stacksync object support. | Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. | Assign ownership separately for relationship details and finance-controlled billing details. |
| PeopleDocumented record: SupportedRecord matching | ContactsProposed record; confirm Stacksync object support. | Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. | Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone. |
| DealsDocumented record: SupportedRecord matching | OpportunitiesProposed record; confirm Stacksync object support. | Keep the opportunity/deal ID separate from any later order or invoice ID. | The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules. |
Use writable fields from the connected accounts. Read values from read-only fields without writing changes back to them, and define deletion handling separately.
Why teams connect Attio and Salesforce
Put your Attio and Salesforce data to work
Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one Attio and Salesforce workflow to test, define what success looks like, and decide who handles failed updates.
Run Attio for a fast-moving team while the wider org stays on Salesforce, with one shared account base.
Migrate from Salesforce to Attio incrementally, keeping Opportunities and Deals reconciled until cutover.
What records can you sync?
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Salesforce
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Connection essentials
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | Attio | Salesforce |
|---|---|---|
| Integration interface | REST API | REST, SOAP, and Bulk APIs |
| Authentication | Guided authorization in the Stacksync connection flow; the saved guide does not name the authentication protocol. | OAuth login via a Salesforce user |
| Change detection | The saved Stacksync guide does not specify the change-detection mechanism. | Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Attio
- Integration interface
- REST API
- Authentication
- Guided authorization in the Stacksync connection flow; the saved guide does not name the authentication protocol.
- Change detection
- The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Create an Attio connection in Stacksync and complete the guided authorization flow.
- Check that the required objects appear in the documented catalog; confirm write-back for each intended object.
Limitations to check
- The connector documents two-way sync, but the object table does not specify which individual fields are writable. Confirm field permissions and change detection for the intended use case.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Salesforce
- Integration interface
- REST, SOAP, and Bulk APIs
- Authentication
- OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
- Change detection
- Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
- Read access
- Available for supported records
- Write access
- Available for supported records
Setup requirements
- Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
- Test in a sandbox and make the intended objects and fields visible to the connected user.
Limitations to check
- Object eligibility depends on write access and the selected detection mode. Non-triggerable objects cannot use trigger mode.
- Read-only and formula fields need separate handling; a Salesforce platform capability does not establish support for every object.
Technical documentation
- Authorize Salesforce
- Enable API Access in Salesforce
- Fix the Salesforce OAuth Error
- Formula Fields
- Make Custom Fields Visible
- Salesforce
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare Attio and Salesforce access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Attio setup checklist
- Create an Attio connection in Stacksync and complete the guided authorization flow.
- Check that the required objects appear in the documented catalog; confirm write-back for each intended object.
Setup guides: Authorize Attio
Salesforce setup checklist
- Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
- Test in a sandbox and make the intended objects and fields visible to the connected user.
Setup guides: Authorize Salesforce
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Attio and Salesforce planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Record matching
Companies / Accounts
Compare whether Attio Companies and Salesforce Accounts describe the same company in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Attio
- Documented record · ✅ Supported
- Salesforce
- Object support to establish
- Record identity
- Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
- Field ownership
- Assign ownership separately for relationship details and finance-controlled billing details.
Fields to include
- Source record ID
- Legal or display name
- Business-unit reference
- Lifecycle status
- Record dependencies
- Resolve parent organizations, business units, and currency references before dependent transactions.
- Validation
- Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
- Recovery
- Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
References: Attio: Companies documentationSalesforce: Accounts documentation
Record matching
People / Contacts
Compare whether Attio People and Salesforce Contacts describe the same contact in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Attio
- Documented record · ✅ Supported
- Salesforce
- Object support to establish
- Record identity
- Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
- Field ownership
- Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.
Fields to include
- Source person ID
- Display name
- Email address
- Organization reference
- Consent state
- Record dependencies
- Resolve the organization relationship and any owner or consent references required by the destination.
- Validation
- Test an email change, two records sharing an email, and a person associated with multiple organizations.
- Recovery
- Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
References: Attio: People documentationSalesforce: Contacts documentation
Record matching
Deals / Opportunities
Compare whether Attio Deals and Salesforce Opportunities describe the same deal or opportunity in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
- Attio
- Documented record · ✅ Supported
- Salesforce
- Object support to establish
- Record identity
- Keep the opportunity/deal ID separate from any later order or invoice ID.
- Field ownership
- The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.
Fields to include
- Source deal ID
- Stage
- Amount and currency
- Expected close date
- Company reference
- Record dependencies
- Map the customer and sales pipeline before the opportunity; map stage values deliberately.
- Validation
- Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
- Recovery
- Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
References: Attio: Deals documentationSalesforce: Opportunities documentation
Compare integration approaches
Use Attio Companies and Salesforce Accounts for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Stacksync managed sync
- Best fit
- Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Attio and Salesforce record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Companies / Accounts, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Attio and Salesforce need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.
File or scheduled snapshot
- Best fit
- Consider for a one-time Attio / Salesforce migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Company sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Companies or Accounts record needs a defined result in the other system.
- Start with Attio Companies and Salesforce Accounts. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve parent organizations, business units, and currency references before dependent transactions.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Contact sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected People or Contacts record needs a defined result in the other system.
- Start with Attio People and Salesforce Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve the organization relationship and any owner or consent references required by the destination.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.
If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
Deal or opportunity sync test
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Deals or Opportunities record needs a defined result in the other system.
- Start with Attio Deals and Salesforce Opportunities. Use the record-matching and field-ownership rules from your mapping worksheet.
- Map the customer and sales pipeline before the opportunity; map stage values deliberately.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Plan the customer lifecycle across Attio and Salesforce
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A customer-facing change in Attio needs operational context in Salesforce.
- Select the relevant People or Companies records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
- Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
- Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.
Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.
If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Companies / Accounts
Test case
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
Expected result
The expected company relationship is preserved with no duplicate action or unintended write.
People / Contacts
Test case
Test an email change, two records sharing an email, and a person associated with multiple organizations.
Expected result
The expected contact relationship is preserved with no duplicate action or unintended write.
Deals / Opportunities
Test case
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
Expected result
The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated company change
Investigate
Inspect Attio Companies and Salesforce Accounts, their IDs, and the destination error.
Next action
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Rejected or repeated contact change
Investigate
Inspect Attio People and Salesforce Contacts, their IDs, and the destination error.
Next action
Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
Rejected or repeated deal or opportunity change
Investigate
Inspect Attio Deals and Salesforce Opportunities, their IDs, and the destination error.
Next action
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
A record type or update is unavailable
Investigate
Check the Attio and Salesforce connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Attio and Salesforce
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Attio Salesforce Timing depends on the connected systems
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesSelected writable fields update in Salesforce. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Salesforce Attio Timing depends on the connected systems
Detect changesStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
Apply updatesSelected writable fields update in Attio. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
FAQ
Attio and Salesforce integration FAQ
-
Stacksync connects Attio and Salesforce with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
-
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Create an Attio connection in Stacksync and complete the guided authorization flow. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Companies in Attio and Accounts in Salesforce. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Use Attio Companies and Salesforce Accounts for the first pilot. Verify its identity and permitted direction, then add dependent records only when the acceptance checks pass.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 561 integrations listed for Attio and Salesforce.
Popular · 8 of 561
-
Attio and Intercom -
Attio and Kommo -
Attio and Kustomer -
Attio and Nimble -
Salesforce and Gladly -
Salesforce and Gorgias -
Salesforce and Infor CRM -
Salesforce and Insightly
No integrations match .
More connections to explore
Next step
See your workflow in Stacksync
Walk through your Attio and Salesforce records, field mappings, and requirements with an integration engineer.
