WordPress backup and migration: how to never lose your site (and move it safely) in 2026

Disclosure: some links in this guide are affiliate links. If you buy through them, Floux may earn a commission at no extra cost to you. We only recommend tools we believe are a good fit for beginners.

One bad update, a hacked plugin or a wrong click can wipe out months of work in seconds. This WordPress backup and migration guide shows you, in plain steps, how to protect your site, store copies somewhere safe, restore them when something breaks and move your website to a new host or domain without panic.

Why backups matter

Most website disasters are not dramatic. They are ordinary:

• **Updates:** a plugin or theme update conflicts with something else and a page stops loading.
• **Hacks:** an outdated plugin or weak password lets someone inject spam or malware.
• **Mistakes:** you delete the wrong page, overwrite a layout or break a setting.
• **Hosting problems:** a server fails, an account is suspended or a payment is missed.

In every case, a recent backup turns a crisis into a short delay. Without one, you may be rebuilding from memory. That is why a simple WordPress backup and migration routine is worth setting up on day one.

The 3-2-1 backup rule, explained simply

The 3-2-1 rule is an easy way to make sure one problem cannot destroy every copy of your website:

• **3 copies** of your site: the live site plus two backups.
• **2 different places or types of storage**, for example your hosting account and a cloud drive.
• **1 copy off-site**, meaning not on the same server as your website.

A practical beginner setup looks like this: your live site, the backups your host keeps, and automatic backups sent to Google Drive, Dropbox or a similar cloud service.

What to back up: files and the database

A WordPress site has two parts, and you need both:

• **Files:** your themes, plugins, uploaded images and documents (mostly in the wp-content folder), plus the wp-config.php file that connects WordPress to the database.
• **Database:** your pages, posts, menus, settings, users, comments and, if you run a WooCommerce store, your orders and customers.

A backup of only the files will not bring back your content, and a backup of only the database will not bring back your images. Always back up both. The WordPress.org documentation explains how these parts fit together if you want more detail.

How often should you back up?

• **A brochure site that rarely changes:** weekly is usually enough.
• **A blog that publishes often:** daily, or after every new post.
• **An online store:** daily at minimum, because orders arrive all the time.
• **Before every update or big change:** always, no matter how often your schedule runs.

Keep several older copies too. If a problem goes unnoticed for a week, yesterday's backup may already contain it. Good WordPress backup and migration habits are about history, not just the latest copy.

Where to store your backups

Store at least one copy off-site in a cloud service such as Google Drive, Dropbox, OneDrive or Amazon S3. Backups that live only on the same server as your website disappear if that server fails or your account is compromised. Host backups are a useful extra layer, but do not rely on them alone, and check how long your host keeps them.

WordPress backup and migration with WPvivid: step by step

WPvivid is a backup plugin with a free version that covers most of what beginners need for WordPress backup and migration, plus a paid Pro version with extra features. Here is the basic workflow.

Step 1: Install WPvivid

In your dashboard, go to Plugins, then Add New, and search for "WPvivid Backup". Install and activate it. A new WPvivid Backup item appears in the left menu.

Step 2: Run your first manual backup

Open the Backup & Restore tab. Choose to back up the database and files together, then click Backup Now. A progress bar appears, and when it finishes the new backup shows in the list below with its date and size.

Step 3: Connect cloud storage

Open the Remote Storage tab, choose a service such as Google Drive or Dropbox and follow the prompt to authorise it. From now on you can send backups there instead of keeping them only on your server.

Step 4: Schedule automatic backups

In the Schedule tab, switch on scheduled backups, pick a frequency that matches your site (weekly, daily) and choose to send them to your remote storage. Then, in the Settings tab, set how many backups to keep so old ones are cleaned up automatically.

Step 5: Restore a backup

If something breaks, open the backup list, find a copy from before the problem and click Restore. WPvivid replaces the broken files and database with that version. Clear any caching afterwards and check the site in a private browser window.

Step 6: Migrate to a new host or domain

Install a fresh WordPress site on the new hosting, for example Hostinger if you are moving to a beginner-friendly host, and install WPvivid there too. On the new site, generate a migration key; on the old site, paste it into the Auto-Migration tab and start the transfer. Alternatively, upload a backup to the new site and restore it. WPvivid updates the old domain in the database during migration, but you should still check for leftovers.

Step 7: Test your restores

A backup you have never restored is a hope, not a plan. Every few months, restore a recent backup to a staging site or a local copy on your computer and click through it. If it works, you know your safety net is real.

What to do before every update

• Take a fresh backup of files and database.
• Read the changelog for big updates of your theme, page builder or WooCommerce.
• Update one thing at a time, then check the homepage, a contact form and checkout if you have one.
• If something breaks, restore the backup first and investigate calmly later.

Our WordPress maintenance tasks checklist puts this into a monthly routine.

WordPress backup and migration checklist for moving a site

• **DNS:** point your domain to the new host and allow time for the change to spread. Keep the old hosting active for a few days.
• **SSL:** install a free SSL certificate on the new host and make sure every page loads over HTTPS.
• **Permalinks:** go to Settings, then Permalinks, and click Save to refresh your URL structure.
• **Search and replace:** if the domain changed, search the database for the old address and fix any leftover links or images.
• **Page builder:** if your site uses a builder such as Divi, open a few pages in the editor and clear its cache so layouts display correctly.
• **Forms and emails:** submit every form and confirm the messages arrive.
• **Redirects and Search Console:** if the domain changed, redirect old URLs to new ones and tell Google Search Console about the move.

Frequently asked questions

Is my hosting company's backup enough?

It is a good extra layer, but not enough on its own. If your hosting account has a problem, those backups may be unavailable. Keep your own off-site copies too.

Is WPvivid free?

WPvivid has a free version that includes manual and scheduled backups, cloud storage, restores and migration. A paid Pro version adds advanced features. Check the current details on their website.

Will migrating my site hurt my SEO?

Not if it is done carefully. Keep the same URLs, use HTTPS, redirect any changed addresses and check for broken links. A domain change needs extra care with redirects.

How long does a WordPress migration take?

With a tested WordPress backup and migration plugin, a small site can often be moved in under an hour, plus time for DNS changes to spread. Large stores take longer, so plan the move for a quiet time.

WordPress backup and migration is one of those jobs nobody thinks about until it is urgent, so set it up today while everything works. If you would rather have experts handle it, our website maintenance and support plans cover backups and updates, or get a free quote for a professional build.