What this means
What this means
A migration is not just file copy. It includes ownership checks, source access, DNS, mail records, SSL, content freeze, verification, and rollback planning.
Before you start
Before you start
Collect the current provider, control panel, WordPress/admin access path, domain registrar, DNS host, mailbox list, database notes, backups, traffic sensitivity, and preferred cutover window.
Step-by-step guidance
Step-by-step guidance
- Identify exactly what is moving: website files, WordPress, databases, mailboxes, DNS, domain, VPS, or app.
- Create a current backup at the source before support starts review.
- List existing DNS records, email records, redirects, cron jobs, and application dependencies.
- Choose a low-risk cutover window and define who approves go/no-go.
- Keep the old provider active until CM Cloud confirms the migrated service is verified.
What CM Cloud support will review
What CM Cloud support will review
Support checks ownership, source access, data size, DNS/email risk, rollback option, SSL readiness, and whether migration can be done metadata-only or needs operator execution.
What is not automated yet
What is not automated yet
This article does not copy files, import databases, change DNS, transfer domains, provision services, or send credentials.
Safety note
Safety note
Reading this article does not capture payment, provision infrastructure, register or transfer domains, change DNS, write Cloudflare or WHMCS, call providers, start workers, create retries, or enable live execution.
Safe next action
Safe next action
Open a migration request and include source provider, domain, service type, mailbox count, backup status, and desired cutover window.