Salesforce and commercetools integration
A move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
Both waysSalesforce and commercetools
What moves between them
- Into SalesforceCustomers and orders from the new platform, mapped to the same Salesforce accounts as before, with the source platform recorded on each record.
- Out of SalesforceNew customers and companies created on commercetools from Salesforce, through the same switch that served the old platform.
How we build it
- A gateway, not a rewriteSalesforce calls one interface; configuration decides whether it reaches the old platform, the new one, or both. The cutover is a setting, not a deployment.
- Source platform on every recordA field records which platform each customer and order came from, so reports work during the overlap.
- Customer IDs carried acrossThe new platform stores the Salesforce ID from day one, so the match is exact.
- Retire in stepsReads and writes move one operation at a time, each with counts checked before the next.
What goes wrong, and the fix
Problems we have found and fixed in production.
- Orders counted twice during the overlapBoth platforms report the same order. The source field and a match on order number keep each order once.
- Customers created on both platformsCreation calls still point at the old platform. The gateway routes each call to one place.
- Callouts hard-coded to the old platformEndpoints and credentials scattered across code. They move into named credentials and one routing table first.
Questions
Do we need to rebuild the Salesforce side?
Rarely. Most of the work is putting one gateway in front of the existing calls and moving IDs across.
Other Salesforce integrations
- Salesforce and SnowflakeWarehouse metrics on every Salesforce account, Salesforce data in the warehouse for reporting, and one definition both sides agree on.
- Salesforce and DocuSignAgreements go out from the deal with the right template and signers, and signed terms, dates and signers come back onto it every time.
- Salesforce and Adobe Commerce (Magento)Customers, orders and catalogue kept in step between Salesforce and the storefront, with one ID both sides trust and a switch in front of every write.
- Salesforce and Microsoft Dynamics 365Closed deals become billing records in Dynamics 365 with the right product codes and dates, and billing status comes back to the account.
- Salesforce and Apollo.ioProspects and enrichment from Apollo.io without blanked fields, wrong owners or “new” leads that are already customers.
- Salesforce and IntercomSupport chats logged on the right contact and account, credited to the person who answered, and the account owner and region visible to the support team.
Talk to us about Salesforce and commercetools.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.