Clone or move a Service
Open a Service and select Configuration > Resource Operations. This page provides two different placement actions:
- Clone Resource creates another Service on a selected server and network destination.
- Move Resource changes which project and environment contain the existing Service.
Neither action moves a Service to another Coolify instance.
A clone creates another Service from the saved configuration. The source Service remains in its current destination and is not replaced.
Treat the clone as a new stack. Do not assume Docker volume contents, bind-mounted files, database records, or data in external services have moved to the destination. Plan a separate, verified transfer or restore for every stateful component.
The Service clone can copy stack configuration such as the Compose definition, environment variables, scheduled tasks, and tags. Review generated domains, credentials, storage definitions, server paths, and automation before deployment.
- Confirm that the target server is validated, can host resources, and has the required network destination. Build servers cannot host the Service.
- Configure any registry, proxy, DNS, firewall, and external-service access required on the target server.
- Under Clone Resource, choose Select Server and Select Network Destination.
- Select Clone Resource.
- Open the new Service and review its source and deployable Compose, environment variables, domains, storage, scheduled tasks, and tags.
- Restore or transfer required data into the new volumes and server paths.
- Deploy with temporary domains or isolated external dependencies.
- Verify every component before moving production traffic.
A bind source copied from the original Compose definition must exist on the destination server with the expected content and permissions. A database component must be restored with an engine-compatible procedure rather than by copying only its connection variables.