Short answer: Back up your WordPress database, wp-content folder, root files, .htaccess, wp-config.php, and uploads. Verify backups by restoring on a staging environment before migration. Use plugins or manual methods, but always keep a local copy.
Key takeaways
- Always back up database and files separately.
- Include .htaccess, wp-config.php, and uploads.
- Verify backups by restoring to a staging site.
- Store backups off-server (cloud + local).
- Test plugins and themes after migration.
- Document your current settings for easy rollback.
What you will find here
You’re about to move your WordPress site. New host, new domain, or just a fresh server. Either way, one thing is non-negotiable: a full backup. I’ve seen too many migrations go sideways because someone thought their host’s automatic backup was enough. It’s not. Let me walk you through the exact checklist I use every time I migrate a site. No fluff, just steps that protect your data.
What Should You Back Up Before Migration?
The short answer: everything. But let’s be specific. Your WordPress site has two core components — the database and the files. Miss either one, and you’re rebuilding from scratch. Here’s what a complete backup includes:
- Database: All your posts, pages, comments, user data, plugin settings, and site options.
- wp-content folder: Themes, plugins, uploads (images, PDFs, videos), and any custom code.
- Root files: .htaccess, wp-config.php, index.php, and any other files in your public_html folder.
- Additional directories: If you have any non-WordPress folders or custom scripts, grab those too.
I always treat the database backup as the most critical piece. Without it, your content is gone. But the files are just as important — themes and plugins aren’t always in the WordPress repository, and uploads aren’t stored in the database.
How to Back Up Your Database
Your database holds everything that makes your site unique. To back it up, you have a few options:
Option 1: Use a Plugin
Plugins like UpdraftPlus, BackupBuddy, or WPvivid can handle both database and file backups. They’re great for beginners. Go to the plugin’s settings, select “Database Only” (or full backup if you want), and trigger the backup. Download the resulting file to your computer and upload it to cloud storage like Google Drive or Dropbox.
Option 2: Manual via phpMyAdmin
Log into your hosting cPanel, open phpMyAdmin, select your WordPress database, and choose “Export.” Select “Quick” export as SQL and save the file. This gives you a raw database dump. It’s fast and reliable, but you need to know your database name and credentials (they’re in wp-config.php).
How to Back Up WordPress Files
Files are easier to handle. You need to copy everything from your site’s root directory (usually public_html or www). Here are the ways to do it:
Use a Plugin
Many backup plugins can zip your entire file structure and email you a link or let you download it directly. Make sure the plugin settings include wp-content and all root files.
Manual via FTP or cPanel
Connect via FTP (FileZilla or your client of choice) to your server. Navigate to the root WordPress folder. Select all files and folders, then download them to your local machine. This can take a while, especially if you have a lot of media files. Alternatively, use cPanel’s File Manager to zip the entire folder and download the zip file.
What to Back Up Beyond the Basics
Don’t stop at database and files. Some other things you’ll regret missing:
- .htaccess: Custom rewrite rules, security headers, and caching directives. If you lose this, your site might break or expose security gaps.
- wp-config.php: Contains database connection details, security keys, and custom settings. Always back this up separately — it’s not in the database.
- Uploads folder: Media library items. These are often the largest files. If you have a lot, consider using a plugin that handles large backups incrementally.
- Plugin/theme customization files: If you’ve edited theme files (child themes) or plugin files directly, copy those changes too. A simple backup of the entire wp-content folder covers this.
Step-by-Step Backup Verification Process
Backing up is only half the job. The other half is verifying that your backup works. Here’s the process I follow:
- Create a staging site on your new server or a local environment (like Local by Flywheel or DesktopServer).
- Restore your backup to the staging site — import the database SQL and upload the files.
- Check a few key pages: Home, a blog post, your contact page, and any custom post types. Make sure content, images, and links work.
- Log in to wp-admin and verify that plugins, themes, and settings are intact.
- Test forms and ecommerce functionality (if applicable). A broken form or checkout can kill your conversion.
If the staging site works, you can proceed with migration confidently. Keep that backup safe until the migration is complete and you’ve verified the live site.
Common Backup Mistakes and How to Avoid Them
Even experienced developers slip up. Here are the most common mistakes I see:
- Relying on host backups alone: Host backups might be overwritten daily. If you realize you need last week’s data, it’s gone. Always keep your own off-server copy.
- Forgetting to back up the uploads folder: Media files are not in the database. If you skip them, your images will be missing post-migration.
- Not testing the backup: A backup file that’s corrupted or incomplete is useless. Always restore to a test environment.
- Using only one backup method: I use a plugin and a manual backup. If one fails, the other saves me.
For a deeper dive on the actual backup process, check out How to Back Up a WordPress Site Before Migration.
Comparison of Backup Methods
| Method | Pros | Cons |
|---|---|---|
| Plugin (e.g., UpdraftPlus) | Easy, automated, handles large files well | Plugin conflicts, subscription costs for advanced features |
| Manual via phpMyAdmin + FTP | No plugin overhead, full control, free | Time-consuming, requires technical skill, large downloads |
| Host-provided backups | Convenient, often free | Retention limits, no control, backup may not be restorable easily |
Final Checklist Before You Hit Migrate
Use this checklist right before migration:
- Database backup downloaded and stored off-server
- Full file backup (including wp-content, root files) downloaded and verified
- .htaccess and wp-config.php backed up separately
- Staging restore test completed successfully
- Current plugin and theme versions noted (for troubleshooting)
- WP-Cron jobs and scheduled tasks documented (if any)
Once you’ve checked every item, you’re ready. Migration is stressful, but a thorough backup removes most of the risk. Don’t skip steps. Your future self will thank you.
Frequently asked questions
What is the most important thing to back up before a WordPress migration?
The database is the most critical component. It contains all your content, user data, plugin settings, and site configuration. Without a database backup, you lose everything except the raw files. Always download a SQL export from phpMyAdmin or use a plugin to create a database-only backup.
Can I use a single plugin for both backup and migration?
Yes, many plugins like All-in-One WP Migration, UpdraftPlus, and BackupBuddy handle both backup and migration. They package your entire site into one file and provide a restore feature on the new server. Just make sure you also keep a separate backup file stored locally or in the cloud.
How do I verify that my backup is valid?
The best way is to restore the backup on a staging site or local environment. If the site works correctly with all content, images, and functionality, the backup is valid. Also check the file sizes and compare with your live site. If the backup file is much smaller than expected, it may be incomplete.
Do I need to back up my WordPress theme and plugins separately?
Not separately if you back up the entire wp-content folder. That folder contains all themes, plugins, and uploads. However, if you’ve made custom modifications to theme files, back up those explicitly. Some developers also keep a list of installed plugins and their versions in case they need to reinstall from the repository.
How many backup copies should I keep?
Keep at least two: one off-server (cloud storage) and one local (external drive or your computer). Some professionals use the 3-2-1 rule: three copies, two different media types, one off-site. For most site owners, a cloud backup and a local download are enough for peace of mind.