Migrate from Laravel Forge to Tenkai
Move a Laravel site from Laravel Forge to Tenkai with its environment, queue workers, scheduler and database, step by step.
Last verified on 2 November 2026 against Laravel Forge's documentation. Report a mistake.
Your Laravel site keeps its code, its .env and its database. It runs as a container on a cluster of servers you own. Its queue workers and its scheduler become resources of their own. Tenkai backs up your database and installs your servers' updates when you ask.
What each part becomes
| On Laravel Forge | On Tenkai |
|---|---|
| Site | Web application |
| Deploy script | A Dockerfile and pre-deploy commands |
| Environment | Variables |
| Queue worker background process | Worker |
| Laravel Scheduler | Scheduled job |
| MySQL, PostgreSQL | MySQL, PostgreSQL |
| Redis | Redis® or Valkey |
| Domains and Let's Encrypt certificates | Custom domains |
| Zero-downtime deployments | Blue-green deployments |
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 Forge server keeps serving until you switch. Your CI builds the image of your app, so the cluster needs no Git builds.
Move your site
- Build the image in your CI. Follow the PHP guide: trust the proxy headers in
bootstrap/app.php, then add its Dockerfile,docker/start.shand.dockerignore. For MySQL, replacepdo_pgsqlwithpdo_mysqlin that Dockerfile. Then add the workflow that publishes an image to GHCR on each push. - Create the web application. Add a web application, choose Container image and enter your image, such as
ghcr.io/acme/app:main. - Copy the environment. Copy the
.envof the site's Settings → Environment and paste it in the project's Variables with Edit as .env…. Leave out theDB_andREDIS_connection lines, because a binding gives them, andLOG_CHANNEL, so your logs reach the Logs tab. - Stop the writes. Run
php artisan downon the Forge server and turn its scheduler off. Let the queue empty withphp artisan queue:work --stop-when-empty --force, then stop the queue workers. - Copy the database. Over SSH on the Forge server, run
mysqldump -u forge -p --routines forge > forge.sql, orpg_dump -Fc --no-owner forge > forge.dumpfor PostgreSQL. Upload the file to your storage bucket, add a MySQL or a PostgreSQL and choose From dump under Initial data. - Bind the databases. Bind the database to the web application and name its variable
DB_URL, orDATABASE_URLin an app created before Laravel 11. For Redis, add a Redis®, bind it and name its variableREDIS_URL. The new store starts empty, so sessions and other Redis data start over. - Add the migrations, the worker and the scheduler.
php artisan migrate --forcebecomes a pre-deploy command. Each queue worker becomes a worker from the same image, with its command as the entrypoint, such asphp artisan queue:work. The scheduler becomes a scheduled job with the schedule* * * * *and the entrypointphp artisan schedule:run. Bind the databases to the worker and the scheduled job. - Deploy and point your domain. Deploy the web application, then the worker and the scheduled job, and check the default address. Add each deploy hook to your workflow, as deploy from GitHub Actions explains. Then add your domain and point its DNS record to the one Tenkai shows.
Files your site keeps
A Forge site writes its uploads to storage/app. On Tenkai, keep them in a hosted bucket with Laravel's s3 disk, and serve them with Storage::temporaryUrl(). Copy every disk of config/filesystems.php, not only public, with aws s3 sync and the values that env prints in the terminal of an application bound to the bucket.
Sources
We read these pages on 2 November 2026.
- Laravel Forge, Deployments and Environment variables
- Laravel Forge, Queues and Scheduler
- Laravel Forge, Databases and Domains
- Laravel, Task scheduling
Redis is a registered trademark of Redis Ltd. Any rights therein are reserved to Redis Ltd.
Something wrong in this guide?
Laravel Forge 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.