What's Happening?
Salesforce is preparing for the retirement of its Salesforce to Salesforce (S2S) feature, a declarative tool used for sharing records between two Salesforce organizations. This feature will be retired with the Spring '27 release, necessitating that organizations currently
relying on S2S implement a different data integration strategy. S2S allowed for bi-directional record synchronization between Salesforce orgs without requiring code or middleware, authenticating through mutual invitation. The publishing organization selected objects and fields to share, while the subscribing organization chose what to accept and mapped it to its own fields. Records were sent asynchronously, with Salesforce retrying failed sends and logging unresolved errors. The company is advising users to assess their current S2S usage and explore alternative solutions, as no single replacement offers the exact same functionality. Salesforce has outlined various options, including partner-facing capabilities like Experience Cloud or Partner Connect, or platform-based integrations using Salesforce Connect, Data 360, or MuleSoft.
Why It's Important?
The retirement of Salesforce to Salesforce (S2S) by the Spring '27 release carries significant implications for U.S. businesses that have integrated their operations using this feature. Companies that have relied on S2S for sharing leads, opportunities, and other critical data with partner organizations will need to re-evaluate and potentially overhaul their data integration strategies. This change could lead to increased operational costs and resource allocation for businesses as they invest in new solutions, training, and implementation. The shift also presents an opportunity for organizations to upgrade their data sharing capabilities, potentially leveraging more advanced features offered by Salesforce's alternative solutions like Partner Cloud or Data 360. However, the transition requires careful planning to avoid disruptions in data flow and ensure business continuity, impacting various stakeholders from IT departments to sales and marketing teams who depend on seamless data exchange.
What's Next?
Organizations currently utilizing Salesforce to Salesforce (S2S) must begin assessing their existing connections and planning for the transition away from the feature before the Spring '27 release. Salesforce recommends creating an inventory of all S2S connections, identifying what data is shared, how it's forwarded, and who owns the connection, along with any dependencies such as automation or assignment rules. After identifying and retiring unneeded connections, businesses should gather requirements for the remaining use cases to select the most appropriate alternative. Salesforce suggests considering partner-facing options like Experience Cloud or Partner Connect for partner scenarios, or platform-based integrations using Salesforce Connect, Data 360, or MuleSoft. For complex or unique requirements, building a custom solution using Apex and REST API calls is also an option. The transition will require careful planning, including coordination with partner organizations, updating automation dependencies, and thorough testing in a sandbox environment to prevent duplicates and ensure data integrity.
Beyond the Headlines
The retirement of Salesforce to Salesforce (S2S) highlights a broader trend in enterprise software towards more robust, scalable, and specialized integration solutions. While S2S offered a straightforward, declarative method for inter-org data sharing, its limitations in handling complex scenarios, high volumes, or specific data types likely prompted Salesforce to encourage adoption of more advanced platforms. This move pushes businesses to adopt modern integration architectures, potentially leading to more resilient and efficient data ecosystems. The emphasis on solutions like MuleSoft and Data 360 suggests a strategic direction by Salesforce to promote its broader suite of integration and data management tools, which offer greater flexibility, governance, and scalability. This shift could also encourage organizations to re-evaluate their overall data strategy, moving towards more centralized data management and identity resolution, ultimately enhancing their ability to derive insights and activate data across their business operations.













