Migrating from Heroku Add-on to Direct Integration

If you’ve been using Judoscale via the Heroku add-on, you can migrate to our direct integration to get more control over your team settings and billing.

Why migrate?

Direct team plans are slightly cheaper than their counterpart add-on plans, and their limits are shared across all your apps.

Other than billing and authentication (you’ll be guided through Heroku OAuth), everything else works exactly the same.

How much pause time should I expect?

Autoscaling pauses when you remove the Heroku add-on, and resumes after you verify metrics on the direct team.

In most migrations, the pause is about 1-2 minutes. The main variable is app boot time after setting JUDOSCALE_URL and restarting.

What is Migrated?

For each add-on app selected during the migration, the following will be copied:

• App info
• Process types info
  • Autoscaling metrics & settings
  • Schedules (if any)

Judoscale will not migrate historical processes data:

• Dyno Usage
• Metrics
• Scale Events

Processes will be setup with the exact same settings, but will start with autoscaling disabled, and the migration will guide you to enable autoscaling again after uninstalling the add-on for each app.

You’ll also be able to choose which team members to migrate to your new direct team.

Migration Steps

1. Create a new team

Click Add team in the teams sidebar and select Heroku. Click Authenticate with Heroku and authorize Judoscale when you’re directed to the Heroku OAuth page. You might be asked to sign into Heroku first.

2. Start the Migration

After authenticating with your Heroku account, you’ll see your existing teams listed. Judoscale will detect any teams that are also linked via the add-on, and show the “Migrate add-on team” option.

Click it to begin, and Judoscale will create your new Heroku direct team, associating it with the add-on team you’re migrating from.

3. Select Apps and Team Members

Choose which apps to migrate from your add-on team. Apps with autoscaling enabled are pre-selected. At least one app must be selected to continue.

You’ll also select which team members to add to the new team. Members who have previously logged in at least once will be pre-selected. You can unselect all and invite new members later if you prefer.

4. Configure Each App

The add-on added the JUDOSCALE_URL environment variable automatically, but removing the add-on will also remove that env var. We’ll need to setup a new one to report metrics for autoscaling.

For each app, you’ll need to:

1. Remove the Heroku add-on:

   heroku addons:destroy judoscale --app your-app-name

1. Set the new environment variable:

   heroku config:set JUDOSCALE_URL=https://adapter.judoscale.com/... --app your-app-name

The exact commands with your app name and the new JUDOSCALE_URL are shown on the migration page.

5. Verify Metrics and Enable Autoscaling

After configuring the environment variable, review the list of processes that are going to be enabled, which by default are the same processes that were autoscaling in your add-on setup, and click “Verify and enable autoscaling”.

Judoscale will confirm it’s receiving metrics from your app using the new configuration. Once verified, autoscaling is automatically enabled for the selected processes.

6. Complete Setup

Repeat steps 3-4 for each app you selected. After all apps are migrated, you’ll be directed to the subscription page to set up billing for unlimited autoscaling. (your new direct team just started on the free “white” plan.)

Choose a plan that covers your current autoscaling needs across your whole team. You can also go to your team dashboard to review your apps and tweak any settings that were migrated.

That’s it! Your apps, processes, and autoscaling settings are now on your new Heroku direct team.

If you have any questions or run into any issues, reach out to us at [email protected].