WZ-IT moves Heroku applications to Coolify, Docker, Kubernetes or another suitable target platform. Web and worker processes, buildpacks, config vars, databases, scheduler, add-ons, domains and operating capabilities are planned together.
Companies worldwide trust WZ-IT
Heroku abstracts processes, builds, databases and add-ons. The exit maps every capability to a traceable target before dynos or data are retired.
Apps, pipelines, dynos, Procfile, buildpacks, config vars, add-ons, scheduler, domains and data are captured completely.
Web, worker, release tasks, Postgres, Redis and external add-ons are designed as containers, services or retained external services.
Test deployment, data export, validation, maintenance window, DNS, smoke tests and rollback point are coordinated.
Technical guide to Procfile, dynos, add-ons, Postgres and cutover during a Heroku exit.
A simple web-dyno application moves differently from a platform with several workers, release tasks, databases and specialist add-ons.
Move Heroku buildpacks, `heroku.yml`, container registry, runtime versions and build configuration reproducibly to the target.
Map web, worker, clock and release processes to separate applications, containers or jobs with suitable start commands.
Export configuration, separate environments, rotate sensitive values and reconnect services on the target.
Assess version, extensions, roles, size and load and move data with an appropriate dump, replication or synchronisation method.
Replace, self-host or deliberately retain Redis, logging, monitoring, email, search and other add-ons.
Configure scheduled jobs, queues, worker scaling, retry behaviour and time zones explicitly on the target.
Rebuild Git deployment, review apps, staging, production, TLS, DNS and approvals around the team's workflow.
Define logs, metrics, availability, backups, updates and incident ownership before production changes over.
Effort factors
Heroku remains available as a rollback option until technical acceptance and the planned changeover.
Capture apps, processes, builds, variables, add-ons, data, domains and pipelines.
Build containers, processes, data services, networking, TLS, backups and monitoring.
Deploy code, move a test copy of data and validate web, worker, job and integration paths.
Coordinate the write window, move final data, switch traffic and maintain the rollback point.
Entry price
€1,990 excluding VAT is the entry price for one clearly bounded Heroku application. The binding proposal depends on processes, add-ons, data, target architecture and cutover requirements.
Individually assessed Heroku migration
from €1,990
excl. VAT, one-time
For the controlled move of a bounded Heroku application to a prepared target environment.
Factors that determine price
The entry price is not a blanket package. With several apps, unknown add-ons or an open target, the PaaS Exit Review from €1,490 excluding VAT may be the right first step.
Depending on platform depth, the Heroku exit begins with a review or moves directly to migration and a managed target platform.
Document and assess dynos, add-ons, data, target options and cutover before implementation.
View reviewContinue web, worker and database services through Git on managed infrastructure.
Explore Coolifyfrom €699.90 excl. VAT / monthOutsource dependencies, CVEs, defects, reviews and releases for the migrated application.
View software supportRequest a Heroku migration
Describe the apps, processes, add-ons, data and target preference. We assess whether a direct migration or an exit review should come first.
Dynos, Procfile, buildpacks, add-ons, Postgres and target operations
A Heroku migration starts at EUR 1,990 excluding VAT. The entry price is not a fixed blanket scope. Apps, dyno types, buildpacks, add-ons, data, target architecture and cutover determine the specific proposal.
The start commands in the Procfile are an important basis. Web, worker, clock and release processes are still configured deliberately as separate applications, services or jobs on the target. With several processes, an unreviewed one-to-one import is not appropriate.
For suitable databases, Heroku PGBackups or PostgreSQL dump and restore can be used. For larger or write-intensive databases, we assess alternative synchronisation and cutover methods as well as versions, roles and extensions.
Each add-on is classified by function and data ownership. Some services can become self-hosted open-source components, while others remain external or move to an alternative managed service. Credentials and endpoints are reset during the change.
Yes. They are configured as separate processes or scheduled jobs on the target. Start commands, concurrency, time zone, retry behaviour, secrets, logging and monitoring must be retained or deliberately changed.
Yes. With Coolify or a suitable CI/CD path, a Git push can continue to trigger automated builds and deployments. Staging, production, approvals, health checks and rollback are configured around the team's workflow.
Yes. WZ-IT can operate infrastructure, deployment platform, data services, monitoring, backups, updates and incident response. Software maintenance and development remain a separately agreed application scope.
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Cloud exit, Proxmox and sovereign operations with concrete results instead of architecture slides.
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.