1. Home
  2. Blog
  3. Backup and Restore

Switch WordPress Backup Plugins Without a Gap in Coverage

Backup and Restore

October 16, 2026

Switching backup plugins has one real risk, and it is not the new plugin. It is the gap. Someone deactivates the old plugin on Monday, plans to set up the new one “this week”, and on Thursday a bad update takes the site down with no backup newer than last month.

When you switch WordPress backup plugins, the plan matters more than the tools. This post is a switch plan for moving to Snapshotify from any other WordPress backup plugin, built so that at every point you have at least one working, recent, off-site backup. It also covers the things that look like problems during a switch but are not.

Rule one: run both for a while

You do not have to choose a cutover day. The Snapshotify FAQ answers this directly: yes, you can run it alongside another backup plugin. It also skips other backup plugins’ directories, so you will not end up backing up your backups.

That makes the safe plan simple. Install Snapshotify, get it fully working and proven, and only then retire the old plugin. Until that point, the old one keeps doing its job.

Step 1: install and take a full backup by hand

Install Snapshotify free from WordPress.org, then go to Snapshotify > Backups and select Create Backup.

  • Backup Title: name it for the reason. “First Snapshotify backup, before switching” tells you months later exactly what this is.
  • Full-Site Backup: leave it on. It is a preset meaning “exclude nothing”, which is what you want for a first backup and for anything you might restore from.
  • Backup Location: local for now, or a connected cloud provider on Pro.

Select Start Backup. You can close the tab while it runs. Snapshotify does the work in short ticks that save progress after each one, so the job continues without the page open. That same design is why it works on shared hosting.

Step 2: verify it, properly

The Snapshotify quickstart puts it bluntly: an unverified backup is a hope, not a backup. Check three things:

  1. The row. It should show a size, a date, its contents and its location. A size of zero or a missing contents badge means something went wrong.
  2. The activity log. It records each stage of the job, and any warning that did not stop it.
  3. The archive. Download it and confirm it opens as a ZIP. Inside you should see database.sql, manifest.json and your files.

If a working backup genuinely matters (and during a switch it does), go one step further and restore it onto a staging site once. The docs call this the only complete verification.

Two things that look wrong but are not

The archive is much smaller than your old plugin’s

This catches almost everyone who switches. The Snapshotify docs say archives are often two to four times smaller than another plugin’s for the same site, and that this is not data loss. Snapshotify compresses the archive and leaves out things you do not need: caches, node_modules, .git, log files, other backup plugins’ folders and regenerable Elementor CSS.

wp-config.php is not in the archive

That is deliberate. It holds your database credentials and salts, and a restore keeps the target site’s own file. That is exactly what makes restoring onto a different server or database work. Server-specific files such as .user.ini, php.ini and drop-ins like object-cache.php are left out for the same reason.

Step 3: get copies off the server

A backup stored on the same server as the site does not survive the failure that destroys the server. You have two options:

  • Free: download archives manually. The archive is a plain ZIP.
  • Pro: connect Google Drive, OneDrive or Dropbox, and uploads happen automatically.

Snapshotify uses limited access on each provider. On Google Drive it can only see files the app itself created, so your existing Drive is invisible to it. OneDrive and Dropbox use a dedicated app folder. The consequence the docs flag: do not reorganize that folder by hand, because archives you move become invisible to the plugin.

If an upload fails, the backup completes as a local backup and the reason is written to its activity log. A row showing Local on a cloud-configured site is telling you an upload failed.

Step 4: put it on a schedule

Scheduling is Pro, and the docs call it most of the reason to have Pro. In Settings > General, turn on Scheduled Backups and choose daily, weekly or monthly. Match the frequency to how much work you would mind losing: a store taking daily orders should back up daily, a brochure site that changes twice a year does not need it.

Pro scheduled backups also drive themselves to completion inside the cron request, which makes them reliable on hosts where the site cannot make requests to itself.

Step 5: set retention you can live with

Auto-Remove Backups keeps the newest few and deletes the rest. The default Keep Latest Backups value is 3. During a switch, that is too few. The docs suggest 7 for daily backups (a week of history), 4 for weekly (a month) and 6 for monthly (half a year), and warn that deletion is permanent.

Step 6: turn on failure emails

Under Settings > Notifications, enable notifications and keep backup failed on at minimum. Send them to an address a person reads. A scheduled backup that quietly fails every week is worse than no schedule, because you believe you are covered.

Step 7: retire the old plugin, but keep its archives

Once Snapshotify has run on schedule long enough to build real history (a week of daily backups, or a month of weekly ones), you can deactivate the old plugin.

Keep its archives, though, and keep a way to open them. The Snapshotify docs describe Upload Backup as taking a Snapshotify archive from elsewhere (another site, or a copy you downloaded before rebuilding a server), so do not count on it to restore another plugin’s backup format. Until Snapshotify’s own history reaches back as far as you need, the old archives are your only route to older versions of the site. Delete them once they are older than anything you would ever restore.

Before you switch: two checks

Multisite. Snapshotify does not support multisite, and it refuses rather than producing an archive that looks fine and is not. If your site is a network, this plan is not for it.

Your licence. If a Pro licence ever lapses, nothing is deleted. Existing backups stay in the list and can still be restored and downloaded. What stops is scheduling, retention and cloud uploads.

The switch at a glance

StepWhereVersion
Full manual backupBackups > Create BackupFree
Verify and downloadBackups list, activity logFree
Off-site copiesSettings > StoragePro (manual download is free)
ScheduleSettings > GeneralPro
RetentionSettings > GeneralPro
Failure emailsSettings > NotificationsFree

For the scheduling side in more depth, see scheduling automatic WordPress backups to cloud storage. Snapshotify Pro comes with every other DaftPlug plugin under one membership; see pricing.