Your Backup Plugin Was Sold or Renamed: A Vendor-Change Checklist
You open the plugins screen and the backup plugin you have trusted for years has a new name. Or an email arrives saying the product now belongs to another company. Nothing is broken. Backups still run. Yet something in your stomach says to look closer, and that instinct is right.
Quick answer: When a backup plugin is sold or renamed, do not panic and do not ignore it. Spend one hour on seven checks: your licence and renewal terms, the archive format, a fresh test restore, where your backup files are stored, the support channel, the update behaviour, and your exit plan. If a backup cannot be restored after the change, you did not have a backup.
This guide is a checklist, not news coverage. It works for any plugin, whichever way the change happened.
Why does a rename or sale matter for a backup plugin?
A backup plugin is unlike most plugins. A contact form that breaks is annoying. A backup plugin that breaks silently can leave you without a safety net for months, and you only find out on the day you need it.
Names and owners change for ordinary reasons: a company merges products, a developer sells to a larger firm, a brand is retired. One well-known example is the move of a long-running premium plugin to a new product name, covered in a plain explanation of what happened when BackupBuddy became Solid Backups. Read it as an illustration of the pattern, not as a verdict on any vendor. Most such changes go smoothly. The few that do not tend to hurt in the same handful of places, which is what the checklist covers.
What should you check first after a change is announced?
Start with what you can see today, before you change a single setting.
- Note the plugin version installed and the date of your last successful backup.
- Download one recent backup file and keep it somewhere off the server.
- Take a screenshot of your current schedule and storage settings.
This takes ten minutes and gives you a known-good starting point. If an update later resets a setting, you will know what it used to be.
The seven checks, in one table
#CheckWhat to look atRed flag1Licence and renewalDoes your licence carry over? Is the renewal price or term changing?Updates stop at expiry with no warning2Archive formatCan the new version read old archives?Old backups need an old plugin version to restore3Test restoreRestore a recent backup to a staging siteRestore fails or is missing files4Storage locationWhere do the files go, and who holds the keys?Backups stored only on the same server5Support channelWhere do you ask for help now?Old forum or email address goes quiet6Update behaviourDoes auto-update change settings or schedules?Schedule reset to default after an update7Exit planCan you move to another tool without losing history?Backups only open in the plugin that made them
Work down the rows in order. The first three decide whether you still have working backups. The last four decide whether you will keep having them.
Will your old backups still restore?
This is the check that matters most, and the one people skip because it feels like extra work. A backup plugin stores your site in its own archive layout. When the vendor changes, the layout can change too.
Do the test on a staging copy, never on the live site. Restore your most recent archive and then your oldest archive. If the oldest fails, you have learned how far back you can truly go, which may be shorter than your retention setting says.
Look at both parts of the site. The WordPress developer handbook describes a complete backup as covering both your files and your database, so a restore test should confirm that posts, settings and uploaded media all came back. Open a few pages, log in, and check one image you uploaded years ago.
A restore test has a simple pass mark. Write it down before you start so you cannot talk yourself into a pass afterwards. For example: the home page loads, the admin login works, the newest post is present, a media file from the oldest folder opens, and the database shows the same number of posts as the live site. Five yes answers is a pass. Anything else is a task to fix this week.
If you do not have a staging area, many hosts offer a one-click staging copy, and a local development tool works too. What matters is that the test never touches the live site. Time the whole exercise and write the minutes down. That number is the real answer to how long recovery takes, and it is far more useful than any promise on a sales page.
Where do your backup files live now?
After a sale, the storage story can quietly change. Some plugins offered their own storage space; some only sent files to a place you connected. Confirm which one applies to you.
Ask three questions. Is the destination still connected after the update? Do the files sit somewhere other than your web server? Can you reach them without logging in to the plugin? A copy that lives on the same server as the website is lost together with the website. An offsite copy you cannot open without the plugin is only half a safety net.
Does the support channel still work?
Support is easy to overlook until you need it at a bad hour. After a change, check that the support page, email address and documentation still point somewhere live. Send a harmless question and note how long the reply takes.
Also check the plugin listing on WordPress.org if it has one. The directory has its own plugin guidelines that every hosted plugin must follow, so a listing that disappears or changes name is something you can read about and plan for rather than guess.
How do you stop an update from changing your settings?
Do not leave automatic updates on for a backup plugin straight after a vendor change. Update it manually, once, on a staging copy first. Then compare your saved screenshot with the new settings screen.
Check the schedule, the retention number, the storage destination and any notification email. These four are the settings most often reset. If one has changed, fix it, then run a manual backup and confirm that a new archive appears. Only then switch automatic updates back on, if you want them at all.
What is a good exit plan for a backup tool?
You do not have to leave. You should know how you would. An exit plan is a short written note that answers three things.
- How do I get every backup out of the plugin and into a plain, standard format such as a zip of files and an SQL file?
- Which other tool could I use to run the next backup tomorrow?
- How long would the switch take?
One option is an offsite service that does not live inside WordPress, so a plugin change cannot touch it. BackupYourSite is an example of that design. It connects to your server over SSH from the outside, so nothing is installed on the site and nothing is written to the server's disk. It streams the files and the database to independent, encrypted offsite storage, checks the archive and the database dump before calling a run successful, and removes old copies only after a fully clean run. You can run it beside your existing plugin during a transition, and a 30-day free trial for one website and 1 GB is enough to test that approach.
What should you do about licences and renewal dates?
A licence is the quietest part of a vendor change. Look for the date your licence ends and what happens then. With many premium plugins, an expired licence does not stop backups running, but it stops updates and support. For a plugin that guards your site, going without updates is a risk in itself.
Write down three facts: the renewal date, the renewal price as stated today, and whether the licence covers one site or several. Ask the vendor in writing whether the existing terms are honoured after the change. A short reply you can keep is worth more than a verbal promise on a chat window.
What if you manage backups for clients?
If the site belongs to someone else, you carry the risk and they carry the loss. Tell them in a sentence or two what changed and what you checked. You do not need a long report. Say the date, the restore test result and any follow-up task.
Keep a simple log for each site: plugin name and version, last restore test, storage location, next review date. When a client asks months later whether backups were checked after the change, the log answers in seconds.
Which mistakes make a vendor change hurt?
- Updating on the live site first, with no archive saved off the server.
- Trusting the green "backup complete" message without a restore test.
- Assuming storage settings survived the update.
- Letting the licence lapse because the renewal email now comes from a different address, which may land in spam.
- Deleting old archives to save space before the new version has proved it can restore them.
Every one of these is avoidable with the checklist above.
How do you decide whether to stay or switch?
Use a plain rule. Stay if all of these are true: the licence carries over, an old archive restores on staging, backups are stored off your server, and support answers within a few days. Switch, or add a second tool, if any one of the first three fails.
If you stay, add a calendar reminder for six months ahead to repeat the restore test. Vendor changes do not end on the day of the announcement. Product rebuilds, new owners and new pricing often arrive in stages.
If you are running a second backup alongside the first for a while, that is not waste. It is cheap insurance during a period when the ground is moving.
Conclusion
A sale or rename of your backup plugin is a reason to check, not a reason to flee. Save a recent backup off the server, restore it to staging, confirm where files are stored, and write down your exit route. An hour spent now is far cheaper than discovering a broken archive in the middle of an incident.
Repeat the restore test twice a year, and the next vendor change will be a short note in your calendar, not a worry.
FAQ
Should I switch backup plugins as soon as one is sold?
No. Run the seven checks first. If an old archive restores on staging and your files are stored offsite, there is rarely a rush.
Will my existing backups work after a rename?
Usually yes, but confirm it. Restore your newest and oldest archives to a staging site and see what comes back.
Do I need a second backup tool during a transition?
It is a good idea. A second, independent backup removes the risk of one vendor's change leaving you uncovered.
Where should backup files be stored?
Away from the web server, in storage you can reach without the plugin. A copy on the same server fails along with the site.
How often should I test a restore?
At least twice a year, and any time the plugin changes name, owner or major version.
