Front
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. |
Business productivity / CRM
Front and Salesforce integration — two-way sync
Keep supported Front and Salesforce records aligned with two-way data 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 Front Accounts or Salesforce Accounts needs a defined result in the other system.
Start with Front Accounts 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
| Front record | Salesforce record | Record matching | Field ownership |
|---|---|---|---|
| AccountsDocumented 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. |
| ContactsDocumented 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. |
Use writable fields from the connected accounts. Keep read-only values one-way and define deletion handling separately.
Why teams connect Front and Salesforce
Put your Front 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 Front and Salesforce workflow to test, define what success looks like, and decide who handles failed updates.
Sync conversations, messages, and tags into Postgres for response-time and volume analytics across inboxes.
Write CRM account tier, owner, and renewal data into Front contact and account custom fields so it shows next to the conversation.
Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
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 | Front | Salesforce |
|---|---|---|
| Integration interface | REST API (Core API) | REST, SOAP, and Bulk APIs |
| Authentication | OAuth authorization via the Stacksync UI | 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
Front
- Integration interface
- REST API (Core API)
- Authentication
- OAuth authorization via the Stacksync UI ("Connections" > "create new connection" > "Front" > "Authorize") — no coding required
- 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 a Front connection in Stacksync and complete the authorization flow.
- Check the documented Accounts, Contacts, Contact Groups, and Events coverage against the required use case.
Limitations to check
- Two-way sync is documented at connector level. The object list does not specify writable fields or change-detection behavior; validate both for the selected records.
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 Front 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.
Front setup checklist
- Create a Front connection in Stacksync and complete the authorization flow.
- Check the documented Accounts, Contacts, Contact Groups, and Events coverage against the required use case.
Setup guides: Authorize Front
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 Front 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
Accounts / Accounts
Compare whether Front Accounts 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.
- Front
- 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: Front: Accounts documentationSalesforce: Accounts documentation
Record matching
Contacts / Contacts
Compare whether Front Contacts 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.
- Front
- 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: Front: Contacts documentationSalesforce: Contacts documentation
Compare integration approaches
Use Front Accounts 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 Front 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 Accounts / Accounts, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Front 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 Front / 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 Accounts or Accounts record needs a defined result in the other system.
- Start with Front Accounts 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 Contacts or Contacts record needs a defined result in the other system.
- Start with Front Contacts 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.
Preserve service context between Front and Salesforce
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A case or customer conversation in Front needs context from Salesforce.
- Select Accounts or Contacts and identify the customer, case, and conversation IDs separately.
- Decide which public status or approved context can appear with Accounts or Contacts; keep private notes, participants, and file access within the intended audience.
- Model reopened or merged cases and linked work items explicitly instead of assuming identical status workflows.
Expected result: A reopened or merged case retains its customer relationship; private service content is not exposed through another system.
If it fails: Review the current case/thread and any message already sent before retrying; a status repair should not create another reply.
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.
Accounts / 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.
Contacts / 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.
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 Front Accounts 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 Front Contacts 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.
A record type or update is unavailable
Investigate
Check the Front 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 Front 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.
Front 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 Front 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 Front. 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
Front and Salesforce integration FAQ
-
Stacksync connects Front 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.
-
Both connectors support reading and writing data, but the chosen objects and fields must also permit both directions. Read-only fields remain one-way. Stacksync database-view sync is one-way; 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 a Front connection in Stacksync and complete the 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 Accounts in Front 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 Front Accounts 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 520 integrations listed for Front and Salesforce.
Popular · 7 of 520
-
Front and Zoho CRM -
Front and Shopify -
Front and Affinity -
Salesforce and Slack -
Salesforce and BetterContact -
Salesforce and Agiloft -
Salesforce and Gainsight
No integrations match .
Next step
See your workflow in Stacksync
Walk through your Front and Salesforce records, field mappings, and requirements with an integration engineer.
