What this covers
Good migration notes reduce delays and prevent support from guessing about DNS, email, databases, or ownership.
Before you start
Prepare safe access paths, not passwords in public notes. Confirm who owns the domain, who can approve downtime, and which services must remain online.
How to do it
- Write down the current host, panel type, domain, and service owner.
- List websites, databases, mailboxes, aliases, DNS records, SSL state, and backups.
- Mark what must not change, especially MX records and active production DNS.
- Share screenshots or exported DNS records where useful, without secrets.
- Submit the request and wait for support to confirm the migration path.
What our team checks
Support reviews completeness, missing access, DNS/email risk, data size, expected downtime, backup state, and rollback expectations.
Next step
Create a migration support request with one domain/service per request when possible.