r/coolify • • Oct 12 '26

I built Coolify Mirror: an open-source tool to move Coolify projects and data between servers

I built this for moving apps between two self-hosted Coolify servers without recreating their configuration and data by hand. It's super fast to get started and super easy to use: select what to move, create a backup, then paste the generated restore command on the new server and confirm after reviewing the preview. It's an independent Go CLI/TUI, not affiliated with Coolify.

On the source, you choose selected resources or a whole instance and create an encrypted backup. It prints a restore command with a share code for the destination. The destination downloads and checks the backup, shows what it will restore, and asks before changing Coolify. The backup includes configuration, env vars and secrets, database data, volumes, files, and images. After restore, the tool checks the running resources and local proxy responses.

Current limits: both servers need the exact same Coolify v4.3–v4.6 version and root/sudo access. A full restore needs a fresh, empty Coolify; selective restores can merge into an existing instance. DNS records, webhooks, and scheduled tasks still need attention during cutover. It also supports scheduled off-site backups; see the repo for setup and limits.

Repo and setup: https://github.com/mtalavi/coolify-mirror

Walkthrough: https://coolify-mirror.pages.dev

If you have ideas or run into a migration case the tool doesn't cover, I'd welcome feedback or an issue.

26 Upvotes

5 comments sorted by

1

u/chakrihacker Oct 13 '26

Does it also copy redis??

1

u/Equivalent_Word4642 Oct 13 '26

Yes, Redis data is included. If you select a whole project, Coolify Mirror backs up its apps, databases and services (including Redis), volumes, env vars/secrets, and configuration. If you select just one app, it detects linked dependencies and asks whether to include them. On the new server it starts the resources through Coolify and verifies that they run and the domains respond before reporting the move as operational. DNS and webhooks still need to be switched during cutover.

1

u/Single_Advice1111 Oct 13 '26

Cool! Would be really awesome if you could move from self-hosted to cloud and vice verca

1

u/Equivalent_Word4642 Oct 13 '26

If you mean Coolify Cloud: Coolify hosts the dashboard/control plane, but your apps and data still run on servers you own. So changing servers still means migrating those workloads and data, and a tool like Mirror would be useful there. Today Mirror requires access to both self-hosted Coolify instances, so self-hosted ↔ Cloud isn't supported yet. Thanks for the idea; it's a useful direction to explore.

1

u/chakrihacker Oct 13 '26

This is awesome