Backup Manager
Back Up WordPress with FTP or SFTP Without Missing Files
Copy WordPress files safely with SFTP, include hidden and custom paths, reconcile transfer errors, and pair the result with a consistent database export.
Main Menu
A backup is only worth what you can restore from it. Most WordPress sites have something that calls itself a backup — a host snapshot, a plugin running nightly, a folder someone downloaded once — and almost none of them have been tested. The gap between having a copy and being able to put a site back is where the real risk sits.
These guides cover both halves. On the backup side: what actually needs copying, how files and the database differ and why taking one without the other leaves you stranded, where copies should live so a hosting failure cannot take the original and the backup together, and how often is often enough for a site that changes daily versus one that changes twice a year.
On the recovery side: restoring when the dashboard still works, and restoring when it does not. Migrations belong here too, because moving a site is a restore onto different hardware, with the same failure modes plus DNS.
There is also a set of articles on what goes wrong mid-operation — a backup that stalls at ninety percent, an archive too large for the transfer, a disk that fills before the job finishes, a restore that leaves half the tables in place. These are ordinary and recoverable, but only if you know which stage failed.
If you are new to this, start with the complete backup and restore guide, then read the article on verifying a backup. Verification is the step most people skip.
Copy WordPress files safely with SFTP, include hidden and custom paths, reconcile transfer errors, and pair the result with a consistent database export.
Store WordPress backups in an organization-managed Microsoft 365 location, verify the cloud object, and test recovery after the uploading account is unavailable.
Send WordPress backups to an organization-controlled Google Drive destination, confirm the remote object, and test access without the source site.
Store WordPress backups beyond the hosting account’s failure boundary, with independent access, protected history, and a restore path you have tested.
Choose WordPress backup frequency from acceptable data loss, real change rates, job duration, and proven recovery—not a one-size-fits-all timetable.
Create a recoverable WooCommerce backup while orders, payments, stock updates, and webhooks continue to change the store.
Verify a WordPress backup with integrity checks and an isolated restore that proves the site, data, media, and critical workflows work together.
Change WordPress URLs after migration without corrupting serialized data, missing hidden references, or creating redirect and cookie loops.
Use a before-and-after WordPress migration checklist that assigns ownership, closes the data gap, verifies cutover, and preserves rollback.
Back up a large WordPress site by planning capacity, separating components, controlling database consistency, and proving the packages can be restored.