Migration limitations

Migration helps reconstruct supported Sites and services on another Control server. It is not a complete clone of an arbitrary source server.

What you choose

Discovery lists what Control can recognise, but nothing is selected solely because it was discovered. Review the Site, database, mail, job, application and file scope before starting an import.

What may need attention

• External DNS — change records at the real DNS provider when you choose to move traffic.
• Certificates and access credentials — source DNS/provider credentials, SFTP keys, Git credentials and backup-destination credentials may need configuring again.
• Applications — supported container applications are recreated on the destination and their selected persistent data is restored. Arbitrary host-specific containers are not cloned.
• Python jobs — a copied Python environment may need rebuilding for the destination.
• Mail — mailboxes and DNS may require a separate stage.
• Unusual file locations — files outside expected website directories are presented for review, not automatically discarded.

Space and interrupted transfers

Allow enough free disk space for the source export, destination restore and temporary transfer files. When a Control-to-Control transfer is interrupted, retry the affected Site rather than resetting successfully completed Sites.

Source and cutover

The source remains available unless you separately decide to retire it. A successful import does not change public DNS, activate a new public certificate or move traffic on its own. Keeping the destination as a backup is a valid use of Migration.