Summary
The upgrade changes only the packaging model of the Elements managed package.
Nothing in your org changes as a result: no metadata, dependencies, functionality, data, or configuration is affected.
You stay on your current package version (6.24).
You run the upgrade yourself: sandbox first, then production, using the links we provide.
Please complete the upgrade by 31 August 2026.
What is changing
The Elements managed package currently uses Salesforce's first-generation packaging model. We are moving it to the second-generation model.
After the upgrade, the package appears as a second-generation package in Setup → Installed Packages. Future updates and fixes are delivered through the second-generation model.
The package version does not change during this upgrade — you remain on 6.24.
What is not changing
The upgrade does not:
Remove any metadata.
Remove any dependencies.
Change any functionality — the package works exactly as it does today.
Change your data, configuration, or permissions.
Change the package namespace or component API names, so your integrations and any references to package components continue to work.
The only difference is the packaging model underneath. There is no functional change for your users.
Why we are making this change
Second-generation packaging gives us access to Salesforce capabilities that are not available on the first-generation model. Upgrading now is what allows us to deliver upcoming improvements, including:
More secure authentication for background jobs (using Salesforce Named Credentials). This resolves an issue where orgs with enforced session settings could see jobs not run or data not process. This fix is delivered in a later version (6.25) that requires the second-generation package.
Alignment with Salesforce's move from Connected Apps to External Client Apps, which Salesforce requires and which is only supported on second-generation packages.
The upgrade itself introduces no visible change. It is the foundation for the improvements above.
Before you begin
You need a Salesforce System Administrator with permission to install and upgrade managed packages.
Have the upgrade links ready:
Sandbox upgrade link: [SANDBOX LINK]
Production upgrade link: [PRODUCTION LINK]
How to upgrade
Please follow these steps in order. Do not upgrade production before validating in a sandbox.
Step 1: Upgrade a sandbox
Open the sandbox upgrade link above while logged in to the sandbox you want to use.
Choose your install option [e.g. Install for Admins Only / Install for All Users — set per your org's needs] and run the upgrade.
Wait for the upgrade to complete. The screen shows a standard package installation and completes normally.
Step 2: Validate in the sandbox
Confirm the upgrade completed without errors.
Confirm the package works as expected — check the workflows, jobs, and data processing you rely on.
Confirm the version still shows as 6.24 in Setup → Installed Packages.
Only continue once your sandbox is validated.
Step 3: Upgrade production
Open the production upgrade link above while logged in to your production org.
Choose the same install option you validated in the sandbox and run the upgrade.
Confirm the upgrade completed and the package works as expected.
Timeline
Now – 31 August 2026: please upgrade your sandbox and then your production org using the links above.
From 1 September 2026: if your production org has not been upgraded, we will begin upgrading remaining orgs on your behalf in a phased manner. We still recommend upgrading yourself first, so you can validate in a sandbox on your own schedule.
Support for the first-generation package is ending
Once this migration begins, we can no longer publish updates or fixes on the first-generation package. To continue receiving support, fixes, and new features, your org needs to be on the second-generation package.
If you report an issue while still on the first-generation package, the resolution will require upgrading to the second-generation package first.
Is the upgrade reversible?
No. Once your org is upgraded to the second-generation package, it cannot be reverted to the first-generation package, and all future updates are delivered on the second-generation model. This is why we ask you to validate in a sandbox before upgrading production.
Frequently asked questions
Will I lose any data or configuration? No. Nothing in your org changes except the packaging model.
Do I need to reinstall the package? No. This is an in-place upgrade. You keep the same version (6.24).
Does the version number change? No. You stay on 6.24. The next version (6.25) will be released later and adds the improvements described above.
Will my integrations or customizations break? No. The namespace and component API names are unchanged, so references and integrations continue to work.
Do I have to upgrade? Yes. Continued support, fixes, and new features require the second-generation package. If you do not upgrade during the window above, we will upgrade your org on your behalf from September.
Need help?
If you have questions or run into any errors during the upgrade, contact us at support@elements.cloud before upgrading your production org.