Switching from BackupBliss

Switching from BackupBliss

BackupBliss is the company behind the Backup Migration WordPress plugin — and, despite the similar name, it is not the same plugin as BackupRidge. Most people looking for a BackupBliss alternative got here one of two ways: their site passed Backup Migration's 4 GB free backup cap, or they wanted the safety features it keeps in Premium (automatic backups before updates, email notifications, encryption). This guide maps your existing Backup Migration setup onto BackupRidge and walks through a safe switch — alongside your current install, with nothing deleted until you have a verified backup in hand.

A few practical differences up front: BackupRidge has no size cap on backup, restore, or migration at any tier, a free pre-update snapshot with one-click rollback, free email notifications, and as many simultaneous destinations as you want per job. Backups are standard ZIP archives you can open with any unzip tool, stored in a bucket or server you own.

Mapping Your Backup Migration Setup

Automatic backups → scheduled backups. Backup Migration's “automatic backups” setting (daily, weekly, or monthly, keep the last N) corresponds to a BackupRidge scheduled backup with the same interval and a retention count. Its include/exclude folder options map to BackupRidge's backup scope and exclusion settings.

“Where shall the backups be stored?” → destinations. BackupRidge free includes Amazon S3, Cloudflare R2, FTP, SFTP, and local folder storage — and you can send one backup to several destinations at once, free. To be fair on the comparison: Backup Migration's pricing page lists Google Drive, OneDrive, and Dropbox as free, and on BackupRidge those three are Pro providers. Its wordpress.org listing also names Amazon S3, Wasabi, and pCloud as destinations, although the pricing page places pCloud in Premium and does not mention S3 or Wasabi — if you use one of those, check the current plugin. Amazon S3 maps one-to-one to BackupRidge's free S3 destination, and Wasabi works through the same S3-compatible endpoint setting. If one of the three OAuth clouds is your only destination, that mapping needs BackupRidge Pro, or a switch to a free destination such as S3-compatible storage (Cloudflare R2 has a free tier that comfortably covers most sites). FTP and SFTP map one-to-one, free on both sides.

BackupBliss Storage → your own bucket. There is no BackupRidge equivalent of their 1 GB included cloud. The nearest free mapping is an S3 or R2 bucket you own — a few minutes to set up, no per-GB plugin fee, and the archives are yours regardless of which plugin you run next year.

Super-quick migration → migration receive, or Import Backup. Backup Migration's site-to-site migration is free within the 4 GB cap. On BackupRidge, receiving a migration is free at any size and pushing one is Pro; the free route for moving a site is to back it up, then bring the archive into the destination with Dashboard → Import Backup and restore it — see Moving to a New Host. URLs are rewritten automatically during the restore.

Staging sites. Backup Migration creates staging sites for free (on your server or TasteWP). BackupRidge has no free staging; a staging clone is a Pro migration-push feature. If free staging is central to your workflow, keep Backup Migration for that job — the two plugins coexist — and use BackupRidge for the backups.

Step-by-Step Migration

You do not need to remove Backup Migration first. Run both side by side until you trust the new setup:

1. Install BackupRidge alongside Backup Migration. Install and activate from the WordPress plugin directory — see Getting Started. Leave Backup Migration active for now. Pre-update snapshots switch on from this moment.

2. Recreate your schedule and destinations. Set the backup scope and schedule to match your Backup Migration automatic-backup settings, then add the equivalent destinations from the mapping above.

3. Run and verify a first full backup. Trigger a manual backup and let it finish — if your site is over 4 GB, this is the moment you find out the cap is gone. Then actually check it: download the archive and open it — it is a standard ZIP, so your database dump and files are right there. Pro adds automated backup verification, and the free plugin includes restore, so you can prove the round trip on a staging site before you rely on it.

4. Deactivate Backup Migration. Once a verified BackupRidge backup exists at your destination, deactivate (and later remove) Backup Migration.

Keep Your Old Backup Migration Archives

Do not delete your existing Backup Migration archives when you switch. BackupRidge cannot restore them directly — it restores its own backups and imports All-in-One WP Migration .wpress files, but does not read Backup Migration's ZIP layout (Backup Migration says the same about other plugins' archives in its own FAQ). They are ZIP files, so they stay openable with any archive tool, and Backup Migration itself can restore them if you ever reinstall it. Keep them at their destination until your BackupRidge retention has cycled enough new backups to cover your recovery window. If they live in BackupBliss Storage, download a copy first — that space is tied to your BackupBliss account, not to you.

What You Get on Cheap Hosting

BackupRidge's core design goal is that backups finish on cheap, slow shared hosting: work is resumable across PHP time limits, upload part sizes are auto-tuned to measured host throughput, large archives are split into parts automatically, and every destination reports success or failure separately — a backup that uploaded to one destination but failed on another says exactly that.

On safety: the snapshot before every plugin, theme, and core update — with one-click rollback — is free and on by default, and email notifications are free too. Every release is documented in the changelog, and every restore we have done is in the public restore log.

Still deciding whether to switch at all? The BackupRidge vs BackupBliss comparison covers the decision side by side, including where Backup Migration genuinely wins.

Switching from a different plugin? See the guides for BackWPup and All-in-One WP Migration.