How Scalingo makes migrating from Heroku easy

Changing cloud providers can feel daunting. New processes, new workflows, new terminology to learn, everything is new, and that can be a little bit scary. Because when you manage a company and teams, new things are fun, but you also want familiarity and stability to be able to continue to run your business as efficiently as possible. That’s something our engineers learned too, in their professional experience, but also while working on their side projects. That’s why they work hard everyday to reduce friction for people using Scalingo, no matter if they’re deploying a brand new app on our service or migrating from another cloud provider, like Heroku. And Scalingo can be a great alternative if you want to find a new home for your apps: same ease of use, familiar deployment flow, everything needed to keep your work efficient, on an secure European platform.

What is Scalingo?

Like Heroku, Scalingo is a PaaS (Platform-as-a-service): we manage the infrastructure, while you just have to create your apps and deploy them on our service to set them live. No DevOps needed, we take care of everything. You can use Scalingo from your dashboard or using our CLI, if you prefer command line.

On Scalingo, you'll find all the features you loved on Heroku: direct integration with Git, GitHub and GitLab for quick and easy continuous deployment of your apps, Review Apps, autoscaling and more. And, good news: if your app works on Heroku, it will work on Scalingo. Like Heroku, we use Cloud Native Buildpacks to detect and run your app automatically, so you don’t have anything new to learn to deploy your apps efficiently. Learn more in our documentation.

But we don’t stop there: 2026 is a big year for Scalingo, with lots of new features planned. We already talked about Private Networks recently, now available, and we have more to come, because our dedication to improving our platform is stronger than ever.

Why move from Heroku to Scalingo?

Some of our clients already made the move from Heroku to Scalingo. Here’s why they decided to trust Scalingo with their apps:

• Ease of use and data hosted in France

“With Scalingo, we get all the features we loved about Heroku, plus the advantage of keeping our data in France.” Guillaume Wrobel, CTO and Co-founder of Yespark

• Transparent and affordable pricing

“I like the flexibility in all the configuration and the cost control. It saves us money!” Sébastien Saunier, CTO of Le Wagon

• Quick deployment and NoOps

“Our goal is to deploy as fast as possible, and Scalingo is perfect for that.” Guillaume Briday, Lead Developer of Per Angusta

• Helpful and efficient support

“The best: the customer service is a big plus. If I have a question or a problem I want to discuss, Scalingo gives me the answer almost instantly with the embedded chat. I can exchange with real human beings.” Sylvain Gautier, Chief Technical Officer (CTO) and co-founder of Baqio

• Review Apps and other essential features

“The feature outside of flexibility that’s very important to us is the Review Apps because it’s essential to our process. As soon as you work on a feature, you can show it.” Robin Komiwes, Co-founder of Dernier Cri

And since our PaaS is **ISO 27001 and HDS-certified**, with a **SecNumCloud-qualified region** available, our service is suitable for hosting apps and databases with sensitive data.

Migrate to Scalingo now

You want to make the jump? Here’s a small lexicon and some tips to make it extra easy for you:

Dynos

• On Scalingo, what Heroku calls “dynos” is called containers. Things referred to as “dynos” on Heroku can be found as “containers” on Scalingo.

Procfile

• Scalingo also make use of the Procfile, except for the release entry.

Buildpacks

• Most buildpacks work the same way on Heroku and Scalingo, with the same compatibility with dozens of languages and frameworks. We have some buildpacks that are written and maintained on our own. You can check our GitHub page for the full list.

Manifest file

• app.json is called scalingo.json on our platform. Its format is fully compatible with the format used by Heroku, but still has a few specifics, which you can learn more about here.

Config vars

• On Scalingo, you can find them under the name Environment Variables.

If you’re using Heroku currently but want to try Scalingo for yourself, we’re happy to help: contact us and tell us you want to migrate from Heroku to obtain 200 € in credits to try the migration process now. No credit card, no forced commitment: we believe you’ll love Scalingo.

Need a little bit more help? You can find more about the migration process in our documentation, in our written tutorial and our video tutorial. And, of course, our support team is always only one click away on your dashboard.