Clone or move an application

Configuration > Resource Operations provides two different placement actions:

Clone Resource creates another application on a selected server and network destination.
Move Resource changes which project and environment contain the existing application.

Neither action moves an application to another Coolify instance. Follow Migrate an application for that process.

A clone copies the application configuration into a new, stopped application. The source application continues running and is not changed.

Cloning does not copy stored application data

Coolify copies storage definitions, but it does not copy the files inside Docker volumes, bind mounts, or directories through this application workflow. Databases and other external state also remain separate.

Plan how to copy required state before deploying the clone.

The cloned configuration includes application settings, environment variables, preview variables, storage definitions, scheduled tasks, tags, and preview records. Review every copied value before deployment, especially domains, secrets, server paths, and external dependency addresses.

Prepare the destination

Confirm that the destination server is validated, can host resources, and has the required network destination. Build servers cannot be selected because they do not host running resources.

Configure any repository, registry, proxy, DNS, and external-service access required by the application on that server.

Open Clone Resource

Open the application and select Configuration > Resource Operations. Under Clone Resource, choose Select Server.

Select the network destination

Choose Select Network Destination for the selected server, then select Clone Resource.

Coolify creates a stopped application in the current project and environment with a name beginning with clone-of-.

Review the clone

Before deploying, review:

the domain and proxy labels, so the clone does not compete with the source application
production and preview environment variables
source or registry access from the destination server
persistent-storage names and source paths
scheduled tasks, so the clone does not run duplicate recurring work unexpectedly
database, cache, queue, storage, and callback addresses

Copy or restore required persistent data separately. A bind-mount path copied from the source configuration must exist on the destination server with the expected files and permissions.

Deploy and verify the clone

Deploy the cloned application with a temporary domain. Verify the image, health check, logs, storage, dependencies, and critical application flow before assigning production traffic.