Clone, export and import Sites

Use Site portability to clone a Site or move it between Control servers. For multiple Sites, start with Control-to-Control migration.

Clone Site

Create a separate local copy of a Site for testing or staging. The clone has its own Site identity; check its hostname and application configuration before use.

Export Site

Export creates an encrypted .control-site bundle. Choose a transfer secret and keep it separately from the downloaded bundle. Portable exports are temporary transfer artifacts rather than a replacement for normal backups.

The bundle includes Site files/data, database contents, runtime settings, background work and managed application information. Sites with multiple managed applications keep their application mount layout in current exports.

Import Site

On the destination select Sites → Import Site, choose the supported .control-site bundle, enter its transfer secret and select the destination hostname.

What to configure after importing

The destination receives its own Site identity and credentials. DNS/provider credentials, SFTP keys, Git credentials, backup destination credentials, deployment history and active TLS certificates are not automatically carried over. HTTPS starts off until the destination hostname is ready.

Import does not automatically retire the original Site. You can keep the destination as a backup, or separately complete DNS and HTTPS cutover if you're moving visitors.