Because this is build-to-order, there is an honest lead time — typically 2 to 4 weeks from kickoff, depending on how many objects you sync and how custom your Salesforce field model is. Timeline breaks down as: discovery and field mapping, build, install on your dev/staging, a UAT cycle against your data, then supervised production deployment. A simple customers+orders sync lands at the short end; heavy custom-object mapping and high-volume Bulk API tuning take longer. We give you a firm date after the scoping call.

You get a defined post-launch support window covering bug fixes, mapping adjustments, and compatibility with Salesforce API and Magento/Adobe Commerce version updates. Because the source ships to your repository, your team can extend it freely. Extended support and enhancement retainers are available, but you are never locked into a recurring license just to keep the connector running — it is yours.

Yes. The module is built on standard Magento 2 framework APIs (observers, service contracts, di.xml, message queues, declarative db_schema.xml) that exist in both editions. On Adobe Commerce we can additionally leverage commerce-only features such as the native RabbitMQ message broker and shared catalog data where relevant. We confirm your exact edition and version during scoping and build against it.

It supports both modes. In real-time mode, observers on events like sales_order_place_after publish a message to a Magento queue and a consumer writes to the Salesforce REST API asynchronously — so checkout is never blocked waiting on Salesforce. For large back-catalogs or nightly reconciliation you can run scheduled cron batches through Bulk API 2.0. The engine is governor-limit aware and retries failed records with backoff into a dead-letter queue.

You configure match keys (such as email or an external ID) and a direction plus conflict-resolution rule per field in the mapping UI — for example Salesforce-wins, Magento-wins, or most-recently-updated. The connector upserts on the match key rather than blindly inserting, and every record is idempotent so retries don't create duplicates. The sync log lets your CRM admin audit exactly what was written and replay anything that failed.

No plain-text passwords are used or stored. Authentication uses the Salesforce OAuth 2.0 JWT bearer flow via a connected app that you create in your own org; we guide you through it and the connector holds only the encrypted certificate/key material in Magento. You grant and can revoke access at any time from Salesforce setup, and access can be scoped to only the objects in your mapping.