Skip to documentation
Interneting.orgDocs
Interneting.orgDocs

Documentation

Migrate an existing website

Move an existing application into a new Control-managed Site with a test-before-cutover workflow.

The safest general migration is to build the destination Site first and switch traffic only after it works.

Prepare

Record the current runtime version, application files, database engine, environment/secrets, cron/worker needs, DNS records and certificate requirements. Take a tested backup of the source.

Build the destination

  1. Create a Control Site with the matching supported runtime.
  2. Transfer files by SFTP, Storage or Git deployment.
  3. Create the required database or attach an independent database.
  4. Move database content using the application's/database engine's supported tools.
  5. Re-enter runtime environment values and create workers/jobs as needed.
  6. Test the destination using a staging hostname or controlled DNS/hosts-file method.
  7. Enable HTTPS for the production hostname when DNS is ready.

Keep the source intact until the new Site has passed application-level acceptance.