Hello everyone, this changelog will be about new features that make it easy for you to migrate from Heroku to Railway.

Railway now detects if there is a Procfile at the root of your repo. Then we map each Heroku process within the Procfile into a service. We even carry over the name of the process from the Procfile to your new project. That easy! We also made a bunch of resources to try to convince you to move your project over. Let us know if it’s successfully convincing.

Migrating from Heroku to Railway blog post

Differences between Heroku and Railway docs

Convert Heroku app.json to Railway template

 where you can come and ask any questions you have.

We’ve made it super easy to import your config secrets from any existing Heroku apps. On the service variables page open up the command palette (⌘+K) and “Import variables from Heroku”. The first time you do this you will need to connect your Heroku account. When importing, if a variable already exists for your service then it won’t be added. So you don’t have to worry about overwriting anything.

If you already have a repo that contains a Heroku 

 with the click of a button. Just head to 

, enter your GitHub repo, and we will autofill the template form with everything that maps over to Railway. You can create the template and save to your account in 1-click.

https://res.cloudinary.com/railway/image/upload/v1661559456/docs/migrate_eafabg.png

Changelog #0096