Salesforce introduces External Client Apps (ECA) - here's what you need to know
Salesforce is modernising the way external applications access the platform. The introduction of External Client Apps (ECA) will step by step replace the current Connected Apps model.
From the Spring ’26 release, you can no longer create new Connected Apps by default. Existing Connected Apps will continue to work, but Salesforce is explicitly positioning ECAs as the new standard for external integrations.
What does this mean for you? And should you do anything right now?
What exactly is changing?
With the arrival of External Client Apps, Salesforce is introducing a new mechanism for managing external applications that need access to Salesforce, for example via OAuth. The change is not just cosmetic. Salesforce wants this to improve its security architecture, gain more control over distribution and lifecycle management, while working towards the eventual end-of-life of Connected Apps.
A key tipping point is the Spring ’26 release. From then on, the creation of new Connected Apps is disabled by default in Salesforce-orgs. Existing Connected Apps remain fully functional. Connected Apps that are part of a managed package will also continue to be supported. However, for new situations, External Client Apps will become the norm.
What does this mean for your organisation?
For existing integrations, nothing will change in the short term. Everything will just keep working as you are used to. Technically, although Connected Apps will be positioned as “legacy”, they will not disappear immediately.
The real impact is in future developments. You can no longer set up new integrations or external applications via Connected Apps. For that, you have to use the External Client Apps model from now on. This also means that internal documentation, integration standards and development guidelines must be adapted accordingly.
How do you prepare?
A good first step is to map all existing Connected Apps and their integrations. Next, it is important to look ahead: are there any new integrations planned that are still based on the old model? If so, this is the time to adjust those plans.
It is also wise to delve into the External Client Apps model and its differences from Connected Apps, both functionally and in terms of security and management. Based on this, you can adjust your internal guidelines and clearly establish that ECAs are the new standard. You then use Connected Apps only for existing situations or when they are part of a managed package.
Finally, communication is key. Make sure developers, integration partners and Salesforce administrators are aware of this change so that new solutions are immediately set up according to the right architecture.
Conclusion
With External Client Apps, Salesforce takes a clear step towards a more secure and manageable integration model. For your current integrations, you don't need to worry. For future developments, however, it is important to make the right choices now.
By switching to the new model in good time, you ensure that your Salesforce environment is ready for the future - and avoid surprises at the Spring ’26 release.
