ERPNext Salesforce Two-Way Sync

ECOSIRE builds a proper Frappe app — a real installable app in your bench, not a pile of client scripts — that treats Salesforce as a first-class integration. We add a Salesforce Settings single DocType holding the Connected App consumer key/secret, instance URL, and API version in encrypted password fields, with a Salesforce OAuth 2.0 token exchange (JWT bearer or web-server flow) and automatic refresh handled server-side. A Salesforce Sync Mapping DocType lets an admin declare, per object, how a Salesforce Account maps to an ERPNext Customer, a Contact to a Contact, an Opportunity to a Quotation/Opportunity, and an Order to a Sales Order — including per-field mappings, value transforms, and which side is the source of truth for each field. Every synced record stores its Salesforce Id and last-modified stamp in custom fields so the connector can match records across systems instead of creating duplicates.

Technically, the two directions are handled differently on purpose. ERPNext-to-Salesforce is event-driven: hooks.py doc events (on_update, on_submit) enqueue a background job via frappe.enqueue that pushes the change through the Salesforce REST API (sObject upsert against your External Id), so submitting a Sales Order in ERPNext writes the matching Order back to Salesforce without blocking the user. Salesforce-to-ERPNext runs on a scheduler_events cron that polls the Salesforce REST/Bulk API for records changed since the last watermark (or subscribes to Platform Events / CDC where available), then upserts into ERPNext inside a single transaction. A Salesforce Sync Log DocType records every attempt, payload hash, and outcome, and failed rows are retriable from a whitelisted method exposed on the Frappe REST API. Field-level conflict resolution is configurable per mapping — last-writer-wins by modified timestamp, a designated master system, or hold-for-review that parks the clash in the log for a human — so a rep editing a phone number in Salesforce and ops editing it in ERPNext never silently clobber each other. Permissions are enforced through a dedicated role profile and role-based DocType permissions so only authorised users touch the settings or replay failed syncs.

Because this is build-to-order, you are not downloading a generic app and hoping it fits. We start from your actual Salesforce org and ERPNext instance: which objects and fields matter, which side owns each field, how you want opportunities to become quotations or orders, and what your dedup rules are. We build the connector for Frappe/ERPNext v15 and v16, test it end-to-end against a Salesforce sandbox and an ERPNext staging site, and hand over source you own. Typical delivery is 2–4 weeks from confirmed scope, and we support it after go-live so schema or Salesforce API-version changes never break the bridge silently.