How to Backup Your WordPress Site Before Migration

Every website migration starts with a single non-negotiable step: a full backup. If something goes wrong during the move, your backup is your lifeline. Without a complete and verifiable backup, you risk losing everything—content, designs, customer data, SEO rankings. This guide shows you exactly how to backup your WordPress site before migration, using plugins or manual methods. Follow these steps to keep your site safe.

What needs to be in a WordPress backup?

A WordPress site is made of two parts: files and a database. You must back up both. The files include your core WordPress installation, themes, plugins, uploads (images, PDFs, etc.), and any custom code. The database stores all your posts, pages, user accounts, comments, settings, and widget configurations. If you only back up files, you lose all your content. If you only back up the database, you lose your design and functionality.

Files vs. Database – what’s the difference?

Component	What it contains	Backup method
WordPress files	wp-content (themes, plugins, uploads), wp-config.php, core files	FTP download or plugin file backup
Database	All content, settings, users, comments, etc.	PHPMyAdmin export or plugin DB backup

Choose a backup method: Plugin vs. Manual

You have two main paths: use a dedicated WordPress backup plugin, or do a manual backup via FTP and PHPMyAdmin. The plugin route is faster and less error-prone. The manual route gives you full control but requires more technical skill. Below are the steps for both.

Method 1: Using a backup plugin (recommended)

Backup plugins automate the entire process. They zip your files, export your database, and can store the backup on cloud services like Google Drive, Dropbox, or Amazon S3. Many also allow you to schedule regular backups, which is great for ongoing safety.

1. Install and activate a backup plugin – popular options include UpdraftPlus, BackWPup, and BackupBuddy. From your WordPress admin, go to Plugins > Add New, search for your plugin, install, and activate.
2. Configure backup settings – After activation, go to the plugin’s settings page. Choose what to backup: usually you should select both files and database. Set your destination – remote storage is best. For a one-time pre-migration backup, you can use the manual backup option.
3. Run the backup – Most plugins have a “Backup Now” button. Click it. The plugin will process your site and create a complete backup archive. This may take a few minutes depending on your site size.
4. Verify the backup – After completion, download a copy of the backup file to your local computer. Check the file size is reasonable (not zero). Many plugins also let you test the backup by restoring to a staging site.
5. Store offsite – If you didn’t set remote storage, manually upload the backup to cloud storage (Google Drive, Dropbox) or an external hard drive. Never keep the only copy on your server.

Method 2: Manual backup via FTP and PHPMyAdmin

If you prefer not to use a plugin, or if your site is too large for plugin limits, do it manually. You need an FTP client (like FileZilla) and access to PHPMyAdmin (usually in cPanel).

Backup files using FTP

1. Connect to your server via FTP using your hosting credentials.
2. Navigate to the root WordPress folder (usually public_html or /).
3. Select all files and folders. Right-click and choose “Download”. This may take a while for large sites.
4. Wait for the transfer to complete. You now have a local copy of all your files.

Backup database using PHPMyAdmin

1. Log into your hosting control panel (cPanel) and open PHPMyAdmin.
2. Select your WordPress database from the list on the left. Look for tables with your wp_ prefix.
3. Click the “Export” tab. Choose the “Custom” export method.
4. In the “Format-specific options”, select “Add DROP TABLE / VIEW / PROCEDURE / FUNCTION / EVENT statement” to ensure a clean restore.
5. Scroll down and click “Go”. You’ll download a .sql file. Save it safely.

How to verify your backup is usable

A backup you can’t restore is worthless. To verify, create a staging environment (using a plugin like WP Staging or manually with a subdomain). Then attempt to restore your backup into that staging site. If the site loads correctly with all content and images, your backup is good. This test also confirms you know the restore process for when you need it.

What about your host’s backups?

Many web hosts provide automatic backups. Do not rely on them alone for migration. Host backups are often stored on the same server. If your server fails during migration, those backups may be lost. Always create your own independent backup and store it offsite.

Common backup mistakes to avoid

• Forgetting the database – Some file-only backups miss the database. Make sure both are included.
• Not testing the backup – A backup that wasn’t tested is a gamble.
• Leaving backup on the server – If your server goes down, your backup goes with it.
• Using an outdated backup – Always create a fresh backup immediately before migration, not one from weeks ago.

How to handle large sites during backup

Large WordPress sites with many images or database records can cause backup plugins to time out or run out of memory. If that happens, switch to manual backup via command line. Use wp db export with WP-CLI to export the database, and tar -czf to compress your files. Most hosts provide WP-CLI access. If not, consider using a plugin that supports split archives, like BackupBuddy’s “Multi-Archive” setting.

Deciding between full backup vs. just files/database

For migration, always back up everything. But for routine safety, you might back up only the database (if your files don’t change often) or only files (if you can rebuild content). For migration, you need both because the target environment may differ in paths, PHP version, or server settings. A partial backup can lead to broken links or missing uploads after restore.

Final checklist before migration

Before you start the actual migration process, run through this checklist:

• Complete backup saved offsite (both files and database).
• Backup verified by a test restore on a staging site.
• Current versions of all themes and plugins noted (you may need them).
• Login credentials for both old and new host ready.
• Domain DNS settings understood (TTL changed to 300 seconds, 24 hours before).

With a solid backup in hand, you can migrate your WordPress site with confidence. If anything goes wrong, you’re one restore away from where you started.

Frequently asked questions

Do I need to back up both files and database?

Yes. Your WordPress site consists of files (themes, plugins, uploads) and a database (content, settings). If you only back up one, you cannot restore the full site. Always back up both to ensure a complete recovery.

Can I rely on my web host’s automatic backups?

Not for migration. Host backups are often stored on the same server as your site. If the server fails during migration, those backups may be inaccessible. Create your own independent backup and store it offsite, like on Google Drive or Dropbox.

How long does a WordPress backup take?

It depends on your site size and method. A small site (under 1 GB) with a plugin can be backed up in under 5 minutes. Large sites with many images may take 15 to 30 minutes via FTP. Always plan extra time.

What backup plugin do you recommend?

Popular and reliable options include UpdraftPlus (free with premium add-ons), BackWPup (free), and BackupBuddy (premium). Each offers scheduled backups, cloud storage, and easy restore. Choose one that fits your budget and technical comfort.

How do I test if my backup is working?

Create a staging environment on your current host or locally using tools like LocalWP. Then restore your backup into that staging site. If the site loads correctly with all content, images, and functionality, your backup is valid. Always test before migration.