Migrate from Dokploy to Tenkai
Move your Dokploy applications, environment variables, schedules and databases to a Tenkai cluster, step by step.
Last verified on 2 November 2026 against Dokploy's documentation. Report a mistake.
Your Dokploy 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 Dokploy | On Tenkai |
|---|---|
| Application with a domain | Web application |
| Application without a domain | Worker |
| Build types | Image built in your CI |
| Docker image source | Container image |
| Static build type | Static site |
| Compose service | One resource for each service |
| Environment settings | Variables |
| Run Command | Entrypoint |
| Schedules | Scheduled jobs |
| Volume mount | Kept directory |
| Postgres, MySQL | PostgreSQL, MySQL |
| Redis | Redis® or Valkey |
| Templates | 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 Dokploy 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 Dokploy's Docker Context Path 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 container port your Dokploy domain points to. When Advanced → Run Command holds a command, enter it as the Entrypoint. - Copy the environment variables. Copy the lines of the application's Environment tab and paste them in the project's Variables with Edit as .env…. Leave out
PORTand the database URLs, because Tenkai sets them. Replace a reference such as${{project.API_KEY}}with its value, and write${{DB_HOST}}as${DB_HOST}. - Stop the writes. Stop the applications and schedules. Let your workers empty the queue, then stop them too.
- Copy the database. Set a free External Port on the database and copy the external connection URL. Add a PostgreSQL or a MySQL, choose From database under Initial data and paste the URL. Remove the external port once the copy ends.
- Bind the databases. Bind the database to the web application, so it receives
DATABASE_URL. For Redis, 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 migrations and the schedules. An application without a domain becomes a worker from the same image, with its start command as the entrypoint. Your migrations become a pre-deploy command. Each job of the Schedules tab becomes a scheduled job with the same cron expression in UTC and its command in
sh -c '…'. 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 Dokploy, add it in Tenkai and point its DNS record to the one Tenkai shows.
Volumes
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.
Compose services and templates
Each service of a Compose service becomes its own resource, such as a web application, a worker or a managed service, and bindings connect them. An app that the marketplace offers, such as WordPress or n8n, installs from there.
Sources
We read these pages on 2 November 2026, with Dokploy v0.30.10.
- Dokploy, Applications, Build type and Advanced
- Dokploy, Docker Compose
- Dokploy, Databases and Connection
- Dokploy, Schedule jobs and Domains
Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd.
Something wrong in this guide?
Dokploy 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.