How to Restore a WordPress Site From a Backup (Without Losing New Orders)
Pick the right restore point, restore from a host snapshot, a backup plugin or raw files plus a SQL dump, and keep the orders and comments that arrived since.
Field guides by topic
Moving a site to a new host or domain without losing anything, and making backups you can actually restore when something breaks.
Pick the right restore point, restore from a host snapshot, a backup plugin or raw files plus a SQL dump, and keep the orders and comments that arrived since.
Move WordPress without a migration plugin: dump the database, copy the files, import, run a safe search-replace, test through your hosts file, then switch DNS.
Fix failed WordPress SQL imports: MySQL server has gone away, phpMyAdmin limits, unknown collation utf8mb4_0900_ai_ci, DEFINER errors, row size too large and mojibake.
A full staging push overwrites every order, customer, review and form entry that arrived on live since you cloned it. Here is how to deploy changes and keep that data.
No backup? Check host snapshots, CDN caches, the Wayback Machine and old copies first, then rebuild from feeds and uploads, or rescue a database MySQL will not start.
A registrar transfer moves the registration, not your website or mail. Downtime comes from DNS hosted at the old registrar. Secure the zone first, then transfer.
Traffic fell after the new site launched. First prove the drop is real, not broken tracking, then find which pages and queries lost out and why.
UpdraftPlus backups that never finish, All-in-One WP Migration imports stuck or blocked by upload size, restores that fail halfway. Find the real limit from the log and get a working backup or move.
Search the field manual
Or jump straight to a symptom
Press / to search from any page, Esc to close