Press ESC to close

Salesforce Functions Retirement (History 2019-2023)

Sept 27, 2023 – Salesforce announced the retirement of Salesforce Functions, aka Salesforce Elastic Services –

This article gives a quick snapshot of the history of Salesforce functions(aka Evergreen) and the next steps from here.

What are Salesforce Functions?

Not many got their hands on Salesforce Functions, so its quite possible you missed out on this feature, here < 1 minute info on it:

Salesforce Functions are serverless, scalable code blocks in Apex, Java, Python, NodeJS, etc.

Invoked by Apex or low-code tools likeSalesforce Flow. They auto-scale,bypassing API limits of off-platformsolutions.

Learn more here –

Great demo from our friends at ApexHours

Timeline / History of Salesforce Functions

  1. Announcement (Dreamforce 2019) – Announced as “Evergreen”: Serverless Functions & Compute for Customer 360 Platform
  2. Alpha Release (Q1 2020) – Limited access for testing and feedback.
  3. General Availability (Oct 12, 2021) – Salesforce Functions becomes generally available to all users.
  4. Container-less (Mar 1, 2022) – Run and test Salesforce Functions locally using the Salesforce CLI; no container containers are required.
  5. New Regions & Languages (Jan 4, 2023) –
  6. Buildback Support (Feb 11, 2023) – Added support for custom build packs, they allow you to use other languages, libraries, and frameworks.
  7. Retirement Announcement (Sept 27, 2023) – Salesforce announced the retirement of Salesforce Functions, aka Salesforce Elastic Services.
  8. End of Sale (EOS) Oct 31, 2023 – The last day customers can purchase new Elastic Services subscriptions
  9. End of Renewal (EOR) Jan 31, 2024  – The last day customers can renew their existing Elastic Services subscriptions.
  10. End of Life (EOL) Jan 31, 2025 The last day Salesforce Functions will be available in Salesforce orgs


That could sound scary, depending on how complex your setup and dependency are on Salesforce functions.

Have a look at this official guide to educate yourself on the migration process –

Overall, the migration will require a good understanding of both Salesforce and Heroku platforms and could be a moderate to complex effort, depending on the existing setup. Here are some steps:

  • Understanding the differences between SalesforceFunctions and Heroku apps.
  • Set up Connected Apps.
  • Update + Deploy Apex classes and triggers for function invocation.
  • Deploy Custom metadata types and objects for functional metadata and tracking.


Feel free to drop your thoughts in the comments. Here are some key references:

Leave a Reply

%d bloggers like this: