Import a Control Site

Transfer selected Sites from another Control server or import a supported saved Site bundle.

Transfer from another Control server

1. Keep the source and destination Control servers on a current compatible release.
2. On the source open Access → API Tokens and create a one-time Migration token.
3. On the destination open Migration → Add Source → Control, enter the exact source Control address and paste the token.
4. Discover Sites and select the ones you want to copy.
5. Start the transfer. Each Site is transferred and checked independently; closing the browser does not cancel the server-side operation.
6. If a Site transfer fails, use the available retry action. Completed Sites do not need to be copied again.

The pairing token is only for enrollment. After pairing succeeds, the original token is consumed and later inventory/transfers use the established pairing.

Sites with multiple applications

A current Control-to-Control transfer carries the Site's complete managed-application set and mount paths. For example, a root application and a second application under /mc remain part of the same transferred Site rather than being split into unrelated Sites.

Keep the source as a backup

A completed transfer does not automatically change DNS or retire the source. You can retain the new Control server as a backup destination and leave public traffic on the original server. Cutover is only needed if you decide to move traffic.

Import a saved Site

Use Sites → Import Site for a supported .control-site bundle. Supply the bundle, transfer secret and destination hostname. Follow any prompts for settings that cannot be transferred.

Before using a restored Site

Review its application data, connected databases, scheduled jobs and any external credentials it needs. The destination receives its own Site identity; DNS/provider, SFTP, Git and backup credentials may need to be configured separately.