Migrate from Coolify to Tenkai
Move your Coolify applications, environment variables, scheduled tasks and databases to a Tenkai cluster, step by step.
Last verified on 2 November 2026 against Coolify's documentation. Report a mistake.
Your Coolify applications keep their repository, their variables and their database data. They run on a Tenkai cluster that joins your servers into one. Your CI builds their image.
What each part becomes
| On Coolify | On Tenkai |
|---|---|
| Application with a domain | Web application |
| Application without a domain | Worker |
| Build packs | Image built in your CI |
| Docker Image | Container image |
| Static build pack | Static site |
| Docker Compose | One resource for each service |
| Environment variables | Variables |
| Pre-deployment command | Pre-deploy commands |
| Scheduled tasks | Scheduled jobs |
| Persistent storage | Kept directory |
| PostgreSQL, MySQL | PostgreSQL, MySQL |
| Redis, KeyDB, Dragonfly | Redis® or Valkey |
| One-click services | Marketplace |
| Domains | Custom domains |
Before you start
You need a cluster with a project on it, as projects and clusters explains. Start it on a new server, so your Coolify server keeps serving until you switch. Your CI builds the image of your app, so the cluster needs no Git builds.
Move your applications
- Build the image in your CI. A Dockerfile application keeps its Dockerfile. An application built with Railpack or Nixpacks takes the Dockerfile of its framework's guide, such as Rails, Django, Node.js, Next.js or PHP. Then add the workflow that publishes an image to GHCR on each push, with Coolify's base directory as its
context. - Create the web application. Add a web application, choose Container image and enter your image, such as
ghcr.io/acme/app:main. Set its runtime port to the port your image listens on, the one Coolify routed your domain to. - Copy the environment variables. Open the application's Environment Variables, choose Developer view and paste the lines in the project's Variables with Edit as .env…. Leave out
PORTand the database URLs, because Tenkai sets them. A value that reads{{project.API_KEY}}stays as written, so paste the value it resolves to. - Stop the writes. Stop the applications and scheduled tasks. Let your workers empty the queue, then stop them too.
- Copy the database. In the database's Public access, choose Public through TCP proxy with a free port and copy the public URL. Add a PostgreSQL or a MySQL, choose From database under Initial data and paste the URL. Close the public port once the copy ends.
- Bind the databases. Bind the database to the web application, so it receives
DATABASE_URL. For Redis, KeyDB or Dragonfly, add a Redis® and bind it, so the app receivesREDIS_URL. The new store starts empty, so sessions and other Redis data start over. - Add the workers, the commands and the scheduled tasks. An application without a domain becomes a worker from the same image, with its start command as the entrypoint. The pre-deployment command becomes a pre-deploy command. Each scheduled task becomes a scheduled job with its command in
sh -c '…', as Coolify runs it. Bind the databases to each of them. - Deploy and point your domain. Deploy the web application, then the workers and scheduled jobs, and check the default address. Add each deploy hook to your workflow, as deploy from GitHub Actions explains. Then remove the domain in Coolify, add it in Tenkai and point its DNS record to the one Tenkai shows.
Persistent storage
A volume mount becomes a kept directory at the same path. Deploy the application once, then bring the files over. Put an archive of them at an HTTPS address and download it into the directory from the application's terminal.
Docker Compose and one-click services
Each service of a Compose application becomes its own resource, such as a web application, a worker or a managed service, and bindings connect them. A one-click service that the marketplace offers, such as WordPress or n8n, installs from there.
Sources
We read these pages on 2 November 2026, with Coolify v4.6.0.
- Coolify, Builds and Dockerfile
- Coolify, Environment variables
- Coolify, Databases and PostgreSQL
- Coolify, Scheduled tasks and Persistent storage
- Coolify, Domains
Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd.
Something wrong in this guide?
Coolify and Tenkai both change, so a step can go out of date. If a command fails or a step does not match what you see, tell us at [email protected]. Once you have an account, you can also choose “Report a bug” in your user menu, as the account guide explains. We fix the guide and reply to you.