Vercel to Coolify or controllable infrastructure
Port Next.js or other web applications with builds, functions, images, caches, cron, domains, and preview and production configuration.
Railway to own infrastructure
Move services, variables, databases, volumes, build and start commands to Docker, Coolify or a managed target environment.
Render to Coolify or Docker
Move web services, workers, cron jobs, persistent disks, databases and Blueprint configuration into reproducible target operations.
Fly.io to own infrastructure
Remap machines, images, secrets, volumes, networking and region logic, and connected databases for the target architecture.
Heroku to Coolify or container operations
Move Procfile, dynos, buildpacks, config vars, add-ons, workers, scheduler and Heroku Postgres to suitable runtime and data services.
Netlify to Coolify or static hosting
Export, replace or reconnect builds, deploy previews, functions, forms, redirects, headers and environment variables according to actual use.
Data, storage and background processes
Migrate databases, uploads, object storage, queues, workers and scheduled jobs separately and validate them against the application.
CI/CD, staging and production
Rebuild Git integration, builds, health checks, deployments, separated variables and optional preview or staging environments.
Domains and external integrations
Prepare DNS, TLS, redirects, webhooks, OAuth callbacks, email and third-party APIs for the new endpoint.
Monitoring and operations handover
Define logs, availability, resources, backups, updates and ownership for operations after cutover.
PaaS migration and cloud exit for production applications
WZ-IT moves applications from Vercel, Railway, Render, Fly.io, Heroku, Netlify and other platforms to Coolify, Docker, Kubernetes or another suitable target architecture. German, European and customer-owned infrastructure are possible operating locations.
Starting point
When a PaaS or cloud exit is appropriate
- An application needs to move from Vercel, Railway, Render, Fly.io, Heroku or Netlify to controllable infrastructure
- Coolify or Docker should replace the current Git-based deployment process
- Hosting cost, data location or platform dependency needs reassessment
- Staging and production should be operated separately and traceably
- WZ-IT or a co-managed model with the development team should operate the application after migration
Controlled platform change
Retain deployment convenience while replacing platform dependencies deliberately
The target setup should continue to support Git, automated builds and separate environments. That requires mapping every platform capability to a sustainable target architecture instead of moving only the application and domain.
Complete inventory
Code, framework, build, functions, environment variables, databases, storage, jobs, domains and external services are captured.Suitable target platform
Coolify, Docker, managed infrastructure or another target architecture is selected around the application and operating needs.Planned cutover
Test deployment, data transfer, functional validation, DNS switch and rollback checkpoint are defined before production moves.
Technical guides for Vercel, Heroku, Netlify, Railway, Render, Fly.io, target platforms and cutover.
Open the PaaS migration knowledge baseMigration paths
Replace Vercel, Railway, Render, Fly.io, Heroku and Netlify with control
The technical path differs by source. WZ-IT maps the platform capabilities in use individually instead of promising a blanket one-to-one move.
Effort factors
The specific scope depends on how deeply platform capabilities are used
- Serverless or edge functions that need adapting to a different runtime
- Large or write-intensive databases with a short permitted outage
- Persistent volumes, object storage and platform data without a direct export path
- Several applications, regions, domains or interdependent services
- Application defects, missing tests or architecture changes required before migration
- High availability, extensive preview environments or special compliance requirements
Process
Inventory the source, reproduce the target, rehearse the move and cut over with control
The current platform remains in production until the application, data paths and acceptance criteria have been validated on the target environment.
- 01
Capture the source
Document repository, services, variables, data, domains, integrations and the current deployment process.
- 02
Prepare the target
Provide infrastructure, runtime, build, data services, network, backups and monitoring.
- 03
Rehearse the migration
Transfer application and data in a test run, validate user paths and resolve deviations.
- 04
Cut over and hand off
Move final data, switch the domain, complete acceptance and document the operating handover.
What we need for the initial assessment
- Current platform and desired target
- Repository, framework and build method
- Functions, workers, cron jobs and platform services in use
- Database, storage and approximate transfer volume
- Domains, integrations and required environments
- Maintenance window and desired operations after the move
Starting price
PaaS and cloud-exit migration from €1,990 excl. VAT
€1,990 excluding VAT is the starting price for a clearly bounded migration project. A binding proposal is prepared only after assessing the source, target, platform capabilities, data and cutover requirements.
The starting price does not define a blanket service package. Before commissioning, you receive a documented scope, the planned target environment and a concrete project price.
All prices are net and exclude statutory VAT. The offers are addressed to businesses.
Individually scoped PaaS migration
For moving a clearly bounded application or platform path to a prepared target environment in a controlled process.
Factors that determine price
- Number and coupling of applications and services
- Serverless, edge, cache and platform capabilities in use
- Database, storage and transfer volume
- Required code and architecture changes
- Staging, preview, availability and cutover requirements
- Required operations after migration
Related paths
Plan the target platform, application and operations together
After migration, WZ-IT can continue operating the deployment platform, the application or its underlying infrastructure within the appropriate scope. Where the target is still unclear, the path starts with a separate PaaS Exit Review.
Coolify managed hosting
Have Coolify operated with Git integration, deployments, databases, backups, updates and monitoring.
View CoolifySoftware maintenance
Maintain dependencies, CVEs, defects, reviews and releases for the migrated application on an ongoing basis.
View software supportSupabase migration
For migrations that also involve Supabase Cloud, Firebase, auth, storage or functions.
View Supabase migrationFrequently asked questions about PaaS and cloud exit
Vercel, Heroku, Coolify, Railway, Render, Fly.io, Netlify, data and operations
- PaaS and cloud-exit migration starts at €1,990 excluding VAT. The starting price is not a blanket fixed scope. The binding price depends on applications, platform capabilities, data, required code changes, target environment and cutover requirements.
- Next.js supports self-hosting in principle. Before migration, we assess the Vercel-specific functions, edge runtimes, image optimisation, caches, cron jobs, integrations and environment variables the application actually uses. Those capabilities must be reproduced or adapted on the target platform.
- No. Coolify is one possible platform for builds, deployments and application services. Hetzner is one possible infrastructure provider. Coolify can run on German, European or customer-owned infrastructure; Docker, Kubernetes or operations without an additional PaaS layer are also possible.
- Yes, those environments can be rebuilt on the target platform. Branches, builds, domains, variables, data access and release processes are planned separately. The exact scope depends on the current workflow and required isolation.
- Yes, when they are part of the agreed scope. Databases, volumes, uploads and object storage are moved separately from the application and then validated. Export path, data volume, write rate and permitted downtime determine the approach.
- That depends on data volume, write activity, DNS, dependencies and target architecture. After the technical assessment, we plan the test deployment, final data sync, cutover and rollback checkpoint. Very low or zero downtime can increase effort substantially.
- Yes. The target process can continue to use Git pushes, automated builds and controlled deployments. We can also separate staging and production and add reviews, approvals, health checks and rollback.
- Yes. Depending on the target, we can operate Linux servers, Coolify or another platform, backups, monitoring and updates. Software maintenance, CVE assessment, releases and technical development of the application are agreed as a separate application scope.
Reviews & projects
Migrations with measurable business impact
Cloud exit, Proxmox and sovereign operations with concrete results instead of architecture slides.
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT
Read client reviews
- Cut cloud cost - up to −81%
- Build a high-availability Proxmox cluster
- Virtualize with Managed Proxmox
- Secure your Proxmox & backup setup
- Modernize your infrastructure - sovereign
- Plan a sovereign open-source stack
- Integrate a local AI solution
- Modernize your legacy software
- Design an open-source AI architecture
- Get collaboration fully managed
- Ship your prototype to production
- Connect sites and clusters securely
Request a migration
Which platform does your application need to leave?
Tell us the source, application, platform capabilities in use and desired target. We will assess the scope and respond with the appropriate migration path.
