LanguageGB
WordPress

WordPress migration

A WordPress migration should be reviewed before moving files, database, DNS, or email.

What this means

What this means

Migration can involve content, database, plugins, theme, media, SSL, DNS, and email records.

Before you start

Before you start

Gather current host access, WordPress admin access, plugin list, theme name, domain, and backup status.

Step-by-step guidance

Step-by-step guidance

  1. Create a current backup at the source host.
  2. List critical plugins and forms.
  3. Confirm DNS and email records.
  4. Share launch timing and rollback expectations.
  5. Wait for support review before cutover.

What CM Cloud support will review

What CM Cloud support will review

Support reviews source access, plugin risk, database size, DNS/email impact, SSL, and rollback plan.

What is not automated yet

What is not automated yet

Requesting migration help does not copy files, change DNS, publish content, or provision hosting automatically.

Safety note

Safety note

Reading this article does not trigger payment, provisioning, DNS, registrar, Cloudflare, WHMCS, or provider actions.

Safe next action

Safe next action

Submit a migration review with host, domain, plugin, and timing details.

Contact Support