Migrate from Coolify / Dokploy

Your existing Docker stack.
A new home.

Move workloads running on Coolify or Dokploy through OpenShip’s existing Server or Docker import. Connect the source server, scan its containers, and review services, data and domains before changing anything.

What comes with you

Review your application, its configuration and its data in one import.

From connection to cutover

Start in New project → Import existing project. Review before anything moves.

  1. Choose Server or Docker

    Open New project → Import existing project → Server or Docker. Both platforms use this shared Docker discovery flow; no separate platform token is needed.

  2. Connect the source server

    Choose a connected server in Desktop or self-hosted OpenShip, or add an external migration source over SSH in Cloud. Leave its applications and proxy running for discovery.

  3. Review services and storage

    Scan the source and select the application workloads. Review images, variables, volumes and domains, then choose an eligible destination and the data strategy.

  4. Verify before cutover

    Check application health, stored data and routing at the destination. Confirm the appropriate cutover only after verification; retire the old platform separately.

Keep the data strategy explicit

Plan the transfer around the data your application needs to keep.

Coolify and Dokploy migrations use the same Docker import as an existing server. On the same server, reuse in place can keep the current application containers and volumes. A copy or cross-server move stops the source workloads while supported persistent data transfers.

Cross-server moves can transfer locally built Docker images through the shared image-save and image-load pipeline. Review destination disk space and keep compatible application versions and data formats: migration does not upgrade databases or reproduce every setting of the old control plane.

Discovery leaves the existing proxy running and reports routes that need review. Edge takeover and source retirement are explicit decisions. Keep backups and verify application data, HTTPS and background jobs before completing the move.

Talk through your migration

Before you move

Access, compatibility and the final switch.

Is there a separate Coolify or Dokploy connector?

No. Select Server or Docker in Import existing project. OpenShip discovers Docker workloads on the source server through its existing connection and uses the shared migration review, destination picker and transfer pipeline.

What access do I need?

Connect the source server over SSH with the permissions needed to inspect Docker and perform the reviewed migration. OpenShip also checks your access to the source and destination. You do not need a Coolify or Dokploy API token.

Will everything move without changes?

Review the scan and its notices before importing. Unsupported mounts, proxy-specific routing and services managed outside Docker can need preparation. Select application workloads rather than the old platform’s control plane or proxy. Both registry images and transferable locally built Docker images use the shared migration pipeline.

Will OpenShip delete my old platform?

Importing does not uninstall Coolify or Dokploy. Review any explicit source cutover or edge takeover before confirming it. Verify the migrated application and backups, then retire the old control plane and resources yourself.

Explore all migration options

Put it to work.

Start on OpenShip Cloud or deploy on your own infrastructure.