Dokploy / Dokploy/dokploy

Ability to seamlessly migrate from Coolify to Dockploy

Open
#3,098 5 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

I currently have a home server running Coolify. I'd like to switch to Dockploy.

As things currently stand, to do so I will have to take all my apps/services offline and remove them from Coolify - removing the docker containers, uninstall coolify, install Dockploy then re-deploy my apps and services using Dockploy and restore any data I had in them

This is a huge job - and I only have one server with a handful of apps. (Home Assistant, Duplicati, zigbee2mqtt, etc. plus a couple of websites).

For others that are already using Coolify to orchestrate multiple servers this could be a non-starter - preventing them from migrating to Dockploy and limiting Dockploy's growth and success.

I suspect the same could be said for people using other similar tools like Caprover and Dokku too.

Describe the solution you'd like

When installing the Dockploy UI on a server that is currently running the Coolify UI, the installer should identify all applications/services/containers managed by that instance of Coolify that are not part of Coolify itself, and automatically migrate them in full over to Dockploy.

It should identify the domains and Let's Encrypt configuration used in Coolify and migrate that over too.

Basically, make it a seamless migration from Coolify to Dockploy without taking down existing services/containers.

Describe alternatives you've considered

No idea if there even are any - couldn't find anything.

Additional context

No response

Will you send a PR to implement it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Dockploy's installation flow and the parts that discover or manage applications, services, containers, domains, and Let's Encrypt configuration. Compare those entry points with the metadata and runtime resources created by Coolify, then define a migration path that preserves existing services and data without downtime; completion should include coverage for the listed migration requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.