Migrate from Heroku
Most Heroku apps move by connecting the same GitHub repo and recreating add-ons on the phase. StackBlaze reads a Procfile during detect (web: and worker:). There is no Heroku config JSON importer and no stackblaze CLI.
Step by step
Export config as a .env file
On Heroku, export config vars to a .env (or copy them). In StackBlaze, open the app Variables tab and use Drop or select a .env file. JSON paste is not supported.
Connect the GitHub repo
On the phase, + Service → Git repository. If the repo has a Procfile, web: becomes a public app and worker: becomes a worker app (no public URL). Review Build method before you commit.
Replace Heroku add-ons
Heroku Postgres → Databases → PostgreSQL. Heroku Redis → Valkey (REDIS_URL). Heroku Scheduler → Jobs on the app. Attach add-ons so connection values inject.
Point the custom domain
Add the hostname under Settings → Domains. Create the CNAME and TXT records the dialog shows. Cut over DNS after the new app is healthy on its *.stackblaze.app URL.
What we do not map
release: as a platform Job, one-off dynos, and Heroku Scheduler as its own service type are not a 1:1 importer. Use Jobs or a worker app.