Skip to documentation
Interneting.orgDocs
Interneting.orgDocs

Documentation

Migration

Copy selected Sites from another server; cutover is optional.

Use Server → Migration to discover and copy selected websites and services from another server. You decide which resources to transfer and whether to change public traffic.

Choose a migration guide

Migrate an existing websitePrepare and move a website into a Control Site.Move from another control panelDiscover and import selected resources from a supported source such as Plesk.Control-to-Control transferCopy Sites from another Control server or saved Site export.What Migration does and does not copyReview credentials, external services and cutover choices.

Typical workflow

  1. Select Add Source and connect a supported source or saved export.
  2. Choose Discover to review available Sites and related services.
  3. Select exactly which resources you want to transfer.
  4. Review any destination conflicts and the import plan.
  5. Start the import and follow each Site's result.
  6. Retry individual failures when offered, without repeating successful Sites.

Cutover is optional

Imported Sites can remain on the destination while the original server continues to serve public traffic. Only use Cutover when you intend to update DNS, enable public HTTPS and switch visitors to the destination.

Mail and other external services

Some mail, DNS, certificates and provider connections need additional steps. The migration screen identifies what Control can do automatically and what you must configure.

Connect another Control server

Keep both Control servers on a current compatible release before starting a new pairing. On the source Control, create a one-use Migration API token under Access. On the destination select Server → Migration → Add Source, enter the source Control address, and paste the token. After successful pairing, the original token is consumed and later migration operations use the established pairing.

A Site is transferred as a Site, including its selected files, database data, scheduled jobs and managed application information. Sites with more than one managed application keep their application mount layout during current Control-to-Control transfer. Pairing does not change live DNS.