Can Freshsales and SAP sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the Freshsales and SAP initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Freshsales account, edition, environment, and business objects the integration must access. Identify the SAP account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Freshsales to SAP sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

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.

How do I map Freshsales fields to SAP?

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.

What should I do if a record fails to sync?

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.

What does a Freshsales and SAP integration cost?

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.

Which records should the Freshsales and SAP pilot start with?

Start by reviewing Accounts in Freshsales and Business Partners in SAP. 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.

CRM / ERP

Freshsales and SAP integration

Plan how Freshsales and SAP should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Freshsales

SAP

Review the integration scope

Teams building with Stacksync

Plan the connection your business needs

Explore a Freshsales and SAP integration with a Stacksync engineer. Stacksync support for Freshsales and SAP is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

01 / Business process

Start with one meaningful update

Identify the record that changes in Freshsales or SAP, where it needs to appear, and which team depends on it.

02 / Data access

Establish the available connection

Bring the objects, account editions, and required directions. An engineer can review the connector path, permissions, and field access.

03 / Success criteria

Define a result you can verify

Agree on record matching, acceptable delay, expected volume, and how your team will resolve failed updates.

Explore the technical references

Technical referenceAvailable documentation, candidate record relationships, and questions for your technical review.

What records can you sync?

Explore the record types and read/write requirements for each system.

FreshsalesConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Contacts	Confirm support for this record type and the direction you need.
Accounts	Confirm support for this record type and the direction you need.
Deals	Confirm support for this record type and the direction you need.
Tasks	Confirm support for this record type and the direction you need.
Appointments	Confirm support for this record type and the direction you need.
Notes	Confirm support for this record type and the direction you need.

Discuss Freshsales requirements

SAPConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Business Partners	Confirm support for this record type and the direction you need.
Materials (Products)	Confirm support for this record type and the direction you need.
Sales Orders	Confirm support for this record type and the direction you need.
Purchase Orders	Confirm support for this record type and the direction you need.
Outbound Deliveries	Confirm support for this record type and the direction you need.
Billing Documents	Confirm support for this record type and the direction you need.

Discuss SAP requirements

Connection requirements and limits

Freshsales

Integration interface: REST API
Authentication: Confirm the credentials, API plan, and permissions required for Freshsales.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for Freshsales and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

SAP

Integration interface: OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication: Confirm the credentials, API plan, and permissions required for SAP.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for SAP and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare your technical review

Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.

Implementation reference

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet

CSV · No email required · Record matching, ownership, and test cases

Customer identityAccounts Business Partners

Before linking Freshsales Accounts to SAP Business Partners, check whether the customer is an individual or a company. Match the correct record type in each system.

Freshsales: Object support to establish
SAP: Object support to establish

Record identity

Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.

Field ownership

Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Customer identityContacts Business Partners

Before linking Freshsales Contacts to SAP Business Partners, check whether the customer is an individual or a company. Match the correct record type in each system.

Freshsales: Object support to establish
SAP: Object support to establish

Record identity

Field ownership

Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Business processDeals Sales Orders

Approved sales handoff: Freshsales Deals provides context for SAP Sales Orders. These are related records, not equivalent entities.

Freshsales: Object support to establish
SAP: Object support to establish

Record identity

Link the originating deal ID to a newly assigned order ID; do not reuse the deal ID as an order number.

Field ownership

Define the approval event and the customer/product data required to create an order. A sales stage alone must not authorize every order.

Fields to include

Source record reference
Destination record reference
Approved handoff state
Duplicate-detection key

Record matchingProducts Materials (Products)

Compare whether Freshsales Products and SAP Materials (Products) describe the same product or catalog item in your business.

Freshsales: Object support to establish
SAP: Object support to establish

Record identity

Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.

Field ownership

Assign ownership for catalog content, price, and stock separately.

Fields to include

Source product ID
SKU or variant reference
Description
Unit of measure
Price-list reference

Architecture decision

Choose how to connect your systems

Choose a method around one example record and the update your business needs. Use Accounts / Business Partners to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
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: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are 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 Freshsales and SAP 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 / Business Partners, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider explicit orchestration for the Deals / Sales Orders handoff.
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. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time Freshsales / SAP 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 reference

From a business event to the right update

Open a workflow to see its trigger, record relationships, and expected result.

Customer sync test

Starting event: A change to the selected Accounts or Business Partners record needs a defined result in the other system.

Start with Freshsales Accounts and SAP Business Partners. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before 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: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer sync test

Starting event: A change to the selected Contacts or Business Partners record needs a defined result in the other system.

Start with Freshsales Contacts and SAP Business Partners. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before 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: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Deal or opportunity process handoff

Starting event: A change to the selected Deals or Sales Orders record needs a defined result in the other system.

Start with Freshsales Deals and SAP Sales Orders. 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: Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.

If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Reconcile SAP business records with Freshsales

Starting event: A finance-owned record in SAP needs operational visibility through Contacts or Accounts.

Select Business Partners or Materials (Products) with the correct legal entity, period, and currency.
Define a reporting relationship in Freshsales; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in SAP.

SAP Freshsales Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in Freshsales.

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.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Freshsales and SAP 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.

Freshsales setup checklist

Identify the Freshsales account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for Freshsales, including read/write support, authentication, and initial-load limits.

SAP setup checklist

Identify the SAP account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for SAP, including read/write support, authentication, and initial-load limits.

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 Freshsales and SAP planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Security and control for your integrations

Use SSO and SCIM to manage access, secure connection options to reach your systems, and record-level retry and revert controls to resolve sync errors.

Explore security controls

FAQ