Salesforce to Salesforce Retirement (S2S): What’s Next & How to Prepare
If your business operates across multiple Salesforce orgs, you’ve likely used Salesforce to Salesforce (S2S) to share data between them. Its simple setup and native record-sharing capabilities made it a go-to solution for seamless cross-org collaboration.
However, just last year, Salesforce announced its retirement, marking a significant shift in how cross-org integrations will be handled moving forward.
In this blog, we break down why this decision was made, what it means for existing users, and how to prepare for what’s next in Salesforce integrations.
What is Salesforce to Salesforce (S2S)?
Salesforce to Salesforce (S2S) is a native feature that enables real-time, secure sharing of records and data between different Salesforce orgs. It allows organizations to collaborate across business units, partners, or subsidiaries without relying on external integration tools.
With S2S, users can establish connections between orgs, define which objects and fields to share, and control access using standard Salesforce security settings. This made it a practical choice for businesses managing multiple orgs.
One of the key reasons for its adoption was its simplicity. Setup was straightforward, enabled from Salesforce Classic, followed by basic configuration to establish connections and start sharing data.
However, after the Spring ’26 release, this is no longer the case, as S2S can no longer be enabled in new orgs.
Why Salesforce is Retiring S2S
S2S is being retired as it no longer meets the requirements of modern integration and collaboration. It was designed for basic, point-to-point data sharing between two Salesforce orgs, which limits its ability to scale in complex, multi-org environments.
One of the primary limitations is its architecture. Each connection must be configured and managed separately, making it difficult to maintain consistency, governance, and visibility as the number of orgs increases. This approach does not support centralized data management or enterprise-wide reporting.
S2S also focuses only on record synchronization, without addressing broader needs such as partner lifecycle management, unified customer data, or advanced collaboration workflows. These capabilities have become essential for growing organizations.
As a result, Salesforce is shifting toward more integrated and scalable solutions that support centralized governance, better visibility, and modern integration patterns across systems.
Understanding the S2S Retirement Timeline
The retirement scheduled for February 2027 is planned in phases, giving organizations time to transition to alternative solutions without immediate disruption. Understanding this timeline is essential for planning a smooth migration.
The retirement will take place as follows:
Spring ’26: The feature can no longer be enabled in new orgs. Existing implementations will continue to function.
Summer ’26: Support will be discontinued, with no further assistance or updates provided.
Spring ’27: The feature will be fully retired and will stop functioning across all orgs.
As of Spring ’26, the option to enable S2S is no longer available in new orgs.
While the phased approach provides some flexibility, relying on S2S during the later stages can increase the risk of disruptions. Planning early will help avoid last-minute challenges.
How This Affects Your Existing Setup
Organizations currently using S2S can continue operating without immediate disruption, but only until the final phase. Since the feature will no longer receive support after Summer ’26, any issues or limitations will need to be managed internally.
As the retirement progresses, the risks begin to increase. There will be no enhancements, no bug fixes, and no compatibility updates with newer Salesforce releases. This can lead to potential data sync failures, reduced reliability, and limited visibility across connected orgs.
Because of this, organizations should not treat the February 2027 deadline as a target. Starting early with evaluation and transition planning ensures continuity and avoids last-minute disruptions.
Modern Ways to Replace Salesforce to Salesforce
With the old way being phased out, Salesforce is guiding organizations toward more robust and purpose-built solutions that align with modern business needs. Instead of simple record sharing, these alternatives focus on collaboration, unified data, and scalable integrations.
1. Partner Cloud
Partner Cloud is the primary replacement for S2S in partner collaboration scenarios. It enables organizations to work closely with partners through a dedicated, branded experience with full visibility and control.
Unlike S2S, which only supports basic record sharing, Partner Cloud provides capabilities such as deal registration, co-selling, partner onboarding, and performance tracking.
This makes it the right choice for organizations that rely on partner ecosystems and need structured collaboration rather than simple data synchronization.
2. Data Cloud One
Data Cloud One is designed for organizations operating multiple Salesforce orgs that need a unified view of their data.
Instead of point-to-point sharing, it creates a centralized data layer with identity resolution, allowing businesses to build a single source of truth and enable enterprise-wide reporting.
This is ideal for companies focused on customer 360, data unification, and governance across multiple orgs.
3. MuleSoft Anypoint Platform
MuleSoft Anypoint Platform supports complex integration use cases across multiple systems, including Salesforce orgs, external applications, and legacy systems.
It enables API-led connectivity, making it suitable for organizations that require flexibility, scalability, and control over how data flows between systems.
4. MuleSoft for Flow
MuleSoft for Flow provides a more simplified integration approach within Flow Builder, enabling connections between Salesforce and various SaaS applications.
It can also be used to establish communication between Salesforce orgs in a more accessible way compared to full-scale MuleSoft implementations.
Important Licensing Considerations: While these modern solutions offer significant advantages over the legacy S2S feature, they come with specific licensing requirements. Unlike the native S2S setup, these alternatives are paid.
Steps to Transition Away from S2S
With retirement already underway and better options available, organizations need to take a proactive approach now.
The first step is to assess current usage. Identify where S2S is being used, which objects are shared, and how critical these connections are to your business processes. This helps define the scope of impact.
Next, evaluate the right alternative based on your requirements:
Partner collaborationChoose Partner Cloud. It is best suited for co-selling, deal registration, and managing partner relationships.
Multi-org data sharingGo with Data Cloud One. It is ideal for unifying data across orgs and enabling centralized reporting.
Complex integrationsUse MuleSoft Anypoint Platform. It supports scalable, API-led integrations across multiple systems.
Simpler integrationsUse MuleSoft for Flow. It is suitable for low-code, quick integrations between Salesforce orgs or SaaS applications.
Finally, it is also important to plan the transition early. Working with experienced teams for Salesforce integration services can help avoid rushed implementations and ensure data consistency.
Conclusion
Salesforce-to-Salesforce has served its purpose well. It was simple to set up, easy to use, and effective for basic data sharing between orgs for many years.
But, as business needs evolved, the limitations became more visible. Modern businesses require deeper integration, better visibility, and more control, something S2S was not designed to handle.
The good part is that the alternatives are not just replacements; they are improvements, built for more advanced, scalable, and structured connections between orgs and systems.
As the transition is already underway, will you take a proactive approach or wait for the deadline to arrive?
Further reading
Spring 26 special: Salesforce Error Monitoring with the Error Console
Official document on Salesforce to Salesforce retirement
Learn more about legacy S2S on help.salesforce
FAQs
1. Can existing S2S cconnections continue to work after Spring ’26?
Yes, existing connections will continue to function, but new setups are no longer allowed. Since support ends in Summer ’26, relying solely on the legacy system can lead to increased risk over time.
2. Will data shared through S2S be lost after retirement?
No, data shared through Salesforce to Salesforce (S2S) will not be deleted after its retirement, as it already exists in the respective Salesforce orgs. However, data synchronization between orgs will stop once the feature is fully retired.
3. Is there a direct replacement for S2S?
There is no one-to-one replacement for Salesforce to Salesforce (S2S). Instead, Salesforce provides multiple solutions such as Partner Cloud, Data Cloud One, and MuleSoft, each designed to address specific use cases.
4. Does moving away from S2S require redevelopment?
In most cases, yes. Since the alternatives follow different architectures than legacy S2S, organizations may need to redesign data flows, integrations, and related processes. This can include redefining how data is shared, managed, and governed across systems.