Treat a migration as a controlled change. Keep the old service active until the new copy, DNS, HTTPS, forms, and email have been verified.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Inventory the current service: Record domains, DNS, databases, runtimes, cron jobs, mailboxes, redirects, SSL, and storage usage.
- Prepare the destination: Match required software versions, create databases and users, and confirm capacity.
- Copy and configure: Transfer files and databases securely, update connection settings, permissions, and application URLs.
- Test before DNS: Use a staging URL or local hosts-file override. Check logins, search, forms, uploads, and background jobs.
- Cut over: Reduce TTL in advance when possible, perform a final data sync, change DNS, and issue SSL.
- Monitor and retire: Watch logs and transactions through the cache window. Cancel the old service only after a verified backup and full acceptance.
Important notes
- Dynamic sites may require a maintenance window or final database sync to prevent lost changes.
- Email migration and website migration are separate workstreams unless explicitly included.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
