Short answer: To back up a WordPress site before migration, you need two things: your database (via phpMyAdmin or a plugin) and your files (via FTP or a backup plugin). A full backup includes the wp-content folder and the database. Use a plugin like UpdraftPlus for simplicity, or do it manually for control.
Key takeaways
- Back up both database and files separately.
- Manual backups via phpMyAdmin and FTP are reliable.
- Backup plugins like UpdraftPlus automate the process.
- Always verify your backup before starting migration.
- Store backups off-site (cloud or local drive).
- Test restore on a staging site if possible.
What you will find here
You’re about to move your WordPress site to a new host or domain. Smart. But if you skip the backup, you’re gambling with everything you’ve built. A single misstep during migration can wipe out your content, break your design, or lose years of SEO work. I’ve seen it happen. A full backup is the only safety net that matters. Here’s how to back up your WordPress site before migration — the right way, every time.
Why a Backup Is Non-Negotiable Before Migration
Migration involves moving files and database records from one server to another. Many things can go wrong: a dropped table during export, a corrupted file transfer, or a plugin conflict on the new environment. A backup lets you revert to the exact state before things went sideways. Without it, you’re rebuilding from scratch. That’s not a risk worth taking.
Your backup must include two components: the database and the files. The database holds posts, pages, users, comments, and settings. The files include your themes, plugins, uploads, and the WordPress core. If either piece is missing, your site won’t work after migration.
Method 1: Manual Backup (Full Control)
If you prefer granular control or don’t trust plugins, manual backup is your route. It requires a bit more work but gives you complete ownership of the process.
Backing Up the Database via phpMyAdmin
Log into your hosting control panel (cPanel, Plesk, etc.) and open phpMyAdmin. Select your WordPress database from the list. Then click the Export tab. Choose the Quick export method and select SQL format. Click Go. This downloads a .sql file containing your entire database. Save it somewhere safe.
Backing Up Files via FTP
Use an FTP client like FileZilla to connect to your server. Navigate to the root directory where WordPress is installed (usually public_html). Download the entire folder to your local machine. This includes wp-content, wp-admin, wp-includes, and core files. The wp-content folder alone holds your themes, plugins, and uploads — it’s the largest part. Give the download time to complete; large sites can take hours.
Once you have both the .sql file and the full file folder, your manual backup is done. Store them in a folder with the site name and date.
Method 2: Plugin-Based Backup (Easy & Automated)
Plugins simplify everything. They handle database and file export together, and many can store backups in the cloud. The most popular is UpdraftPlus, but others like BlogVault and BackWPup also work well.
Using UpdraftPlus for a Full Backup
Install and activate UpdraftPlus. Go to Settings > UpdraftPlus Backups. Click Backup Now. Choose to include both database and files. Click Backup Now again. The plugin exports your site and stores it in the folder you configured (default is /wp-content/updraft). You can also set it to send a copy to Dropbox, Google Drive, or email. After completion, download the backup components from the Existing Backups tab.
Using All-in-One WP Migration
This plugin creates a single file containing everything — database, files, and media. Run the export from the plugin menu, download the .wpress file. It’s dead simple, but the free version caps exports at 512 MB. For larger sites you’ll need the paid extension or manual file adjustments. Not ideal for big media libraries.
| Method | Pros | Cons |
|---|---|---|
| Manual | Full control, no plugin dependency | Time-consuming, technical skill needed |
| UpdraftPlus | Automated, cloud storage options | Requires plugin setup, adds bloat |
| All-in-One WP Migration | One-click, simple restore | File size limits, slower for large sites |
3 Steps to Verify Your Backup
A backup that can’t be restored is useless. Before migration, test your backup. Here’s how:
- Check file integrity. Open the .sql file in a text editor. Look for table names like wp_posts. If you see garbled text or nothing, the export failed. Ensure the downloaded file folder isn’t empty and contains subfolders.
- Restore on a staging environment. Set up a local WordPress install using Local or DesktopServer. Replace its database with your .sql file and its files with your backup. If the site loads properly, your backup is good.
- Check critical data. Browse a few posts, check user accounts, and verify plugin settings. A quick functional test saves headaches later.
Common Backup Mistakes and How to Avoid Them
I’ve seen people skip the database because they think files are enough. Others download the wrong database from phpMyAdmin. Both are catastrophic. Here’s what to watch for:
- Incomplete database export. Always confirm the .sql file size matches your database size. A tiny file often means missing tables.
- Wrong file permissions. After FTP download, some folders might be empty if your client skipped hidden files. Use the Force showing hidden files option.
- Backing up cache files. Exclude cache folders to keep the backup lean. They’ll regenerate on the new server.
- Relying solely on host backups. Many hosts offer backups, but they may be infrequent or inaccessible. Maintain your own copy.
Where to Store Your Backup
Your backup is only as good as where you keep it. The local machine is a start, but hard drives fail. Follow the 3-2-1 rule: three copies, two different media, one off-site. For example: one copy on your computer, one on an external drive, one in cloud storage (Google Drive, Dropbox, S3). Or use a backup plugin that automatically sends to cloud.
Next Step: Migrate With Confidence
With your verified backup in hand, you’re ready to migrate. Whether you use a migration plugin or manual steps, you can undo any mistake. Don’t rush the backup. Spend the time to do it thoroughly — it’s the cheapest insurance you’ll ever buy. And keep that backup file even after migration completes. You never know when you’ll need to roll back.
Frequently asked questions
What is the best plugin to back up WordPress before migration?
The best plugin depends on your needs. UpdraftPlus is popular for its simplicity and cloud storage options. All-in-One WP Migration creates a single file that’s easy to restore. For larger sites, BlogVault works well. All are reliable, but always test the backup before relying on it.
Can I backup only the database and skip the files?
No. The database alone won’t restore your site’s appearance or functionality. You need the files — themes, plugins, uploads. Without them, you’ll have a bare database with nothing to display it. Always backup both components.
How long does a full WordPress backup take?
It varies by site size. A small site with a few posts and no media might take 5 minutes. A large site with gigabytes of images can take an hour or more via FTP. Plugin backups are usually faster. Plan for the worst case and don’t rush.
Do I need to backup my database if I use a staging site?
Yes. Your staging site is a copy, but it often has different URLs and can diverge over time. Always backup your live database before migration to ensure you have the current production data.
Can I backup a WordPress site without a plugin?
Absolutely. Use phpMyAdmin to export the database and an FTP client to download all files. This manual method gives you full control and doesn’t depend on any plugin. It’s the most reliable approach for experienced users.
4 thoughts on “How to Back Up a WordPress Site Before Migration – Step by Step”