Migrate your self-hosted DQE server from Heroku-22 to Heroku-26

Support DQE
Support DQE

If you host your own DQE server on Heroku (instead of using DQE's shared server), Heroku is retiring the Heroku-22 stack. This article walks you through migrating your Heroku app to Heroku-26.

Deadline: Heroku-22 reaches end of support and security updates on 30 April 2027. Starting 1 May 2027, new builds on Heroku-22 are blocked. Migrate before that date to avoid any interruption.

Before you start: check your DQE One package version

This migration requires your Salesforce org to have DQE One package version 1.4 or later installed.

  • In Salesforce, go to Setup → Installed Packages and check the version listed next to DQE One.
  • If it's older than 1.4, update the package to the latest version first (from the same Installed Packages page, or via the AppExchange listing) before migrating the Heroku app.

1. Switch your Heroku app to the Heroku-26 stack

Open a terminal with the Heroku CLI installed, make sure you're logged in (heroku login), then set the new stack on your app:

heroku stack:set heroku-26 -a <your-app-name>

2. Deploy an updated build on the new stack

Setting the stack does not rebuild your app by itself. Redeploy it using the same Package update steps as in the DQE One Server installation guide:

  1. Open the folder that was created on your computer during the first installation.
  2. Open a command prompt in that folder.
  3. Run git pull
  4. Run git commit --allow-empty -m "update"
  5. Run git push heroku master

If the update doesn't work

Delete the add-on in the Heroku interface and install it again as a new add-on:

  1. In the Heroku app's Settings → Config Vars, add your API key to the DQE_ONE_SERVEUR_LICENCE variable, and set the version to your version.
  2. Open the newly created folder, open a command prompt in it, and run: git add ., then git commit -am "first deploy", then git push heroku master.

3. Confirm the migration

  1. Run heroku stack -a <your-app-name> — it should now show Heroku-26.
  2. Test the connection from Salesforce — open DQE One Setup → Lookup and run a test search — to confirm your server responds correctly on Heroku-26.

Recommended order

If you run several environments (development, UAT, pre-production, production), migrate and validate them one at a time, in that order, rather than migrating every environment at once — this lets you catch any issue before it reaches production.

Related articles

Related to

Was this article helpful?

0 out of 0 found this helpful