Most MSPs don't change backup vendors for fun. Usually something changes: a renewal lands higher than expected, support stops feeling like support, or a feature you rely on gets bundled into a plan you don't want.

When that happens, you start comparing options. Maybe you're searching for Acronis alternatives, Datto alternatives, or Axcient alternatives, and the product pages look fine. The hard part is the move itself.

I've run an MSP since 2010, and I've seen what makes a backup move go smoothly and what makes it drag. Backup history almost never transfers cleanly from one vendor to another. Agents have to be redeployed. Retention has to be rebuilt. And for a while, you're paying for two platforms so your clients stay covered. That overlap is why good MSPs delay the switch even when they've already picked the next tool.

This is the checklist I'd hand another owner before the first client moves. It isn't a pitch. It's the work that keeps a migration boring, which is exactly what you want.

1. Inventory what you actually protect

Start with a spreadsheet, not a sales call. For every client, write down:

  • Workstations and servers (counts and OS)
  • Microsoft 365 tenants and roughly how many mailboxes / OneDrive / SharePoint sites you protect
  • Virtual machines and whether you back them up at the guest or the host
  • Local or NAS copies, if you keep any
  • Current retention (daily, weekly, monthly, yearly — and how far back)
  • Restore types you've actually used in the last year: file, image / bare metal, mailbox, full site
  • Special cases: SQL, line-of-business apps, clients with compliance rules

Then add the contract facts: renewal date, notice period, minimums, and whether canceling needs a portal ticket or a signed letter. You're making sure the new platform is priced and tested against the fleet you really have, not the one you remember.

2. Decide what happens to old restore points

When you leave a backup vendor, the restore points you already have usually stay with that vendor until the account ends or the retention ages out. They don't import into the new platform.

Before you cancel anything, answer three questions in writing:

  1. How far back does each client need to be able to restore today?
  2. How long will you keep the old platform running so those points stay reachable?
  3. Who on your team can still log in and run a restore from the old console during that window?

Until the new platform has enough of its own history to cover your retention promise, the old one is still part of your backup stack. Plan for that on purpose.

3. Run both platforms in parallel

A clean Friday-night cutover looks tidy on a project plan and rough in real life. The safer pattern is:

  1. Deploy the new backup agent to a small pilot group (one easy client, one messy one).
  2. Let the first full backups finish and confirm jobs are green.
  3. Keep the old backups running on those same devices.
  4. Only after the new history covers your minimum retention window do you stop the old jobs — and even then, leave the old restore points available until they age out or the contract ends.

Yes, that means a period of double cost. Budget for it. Ask any vendor you're evaluating what they do to soften that overlap.

On our side, Migration Rescue (code RAMPUP) is built for that window: 30 days free, then 50% off for 60 days, plus white-glove migration help. Details are on the switching page. Use whichever vendor's overlap offer matches your timeline — the checklist stays the same either way.

4. Test restores before you move production

Green backup jobs are not a restore test. Before you expand past the pilot, run the restore types you sell:

  • A file-level restore a client would actually request
  • An image or bare-metal restore on a spare or lab machine, if that's part of your offering
  • A Microsoft 365 mailbox or OneDrive restore, if you protect M365
  • A timed restore so you know whether the SLA you quote is still honest

Write down how long each took and what broke. Fix the broken parts on the pilot clients. Only then widen the rollout. The goal is knowing the failure modes while the blast radius is still small.

5. Tell clients what changes — and what doesn't

Most clients don't care which backup console you use. They care that yesterday's files come back, and that your name is still on the ticket. A short note is enough:

  • You're upgrading the backup platform behind the scenes
  • Their retention and restore process stay the same (or call out the one thing that changes)
  • Who to contact if they need a restore during the transition
  • That they may see a new backup agent or a one-time reboot, if that's true for your stack

Skip the vendor comparison in the client email. They hired you, not your supplier.

6. Time the move around renewals

The cheapest day to leave is rarely the day you get mad. Check the contract end date, required notice, whether the term auto-renews, whether storage or seats are prepaid, and whether any appliances or seed drives are still on the books.

If a renewal is 60 days out, start the pilot now so the new history is deep enough by the time notice is due. If you're stuck in a longer term, you can still stand up the new platform, build history, and stop the old jobs later — just don't cancel early and orphan restore points you still need.

Move low-risk clients first. Save the ones with tight compliance windows, huge file servers, or frequent restore requests for when your team has done the dance a few times.

7. Where Magnus Box fits

If you're reading this while comparing platforms, here's the short version of how we run things — the same facts that are on our site.

Magnus Box is white-label cloud backup sold only through MSPs. I've run an MSP since 2010, and Magnus Box is bootstrapped, with real support. The partner account is $45/mo and includes branding, support, and the first 3 licenses. After that it's $7 per workstation (1 TB into your pool) and $17 per server (3 TB), storage pooled across clients, month to month. The trial is 14 days with no credit card.

If you're moving off another vendor, RAMPUP / Migration Rescue covers the overlap: 30 days free, then 50% off for 60 days, plus white-glove help with the migration plan. Start on the test drive, or read the switching guide.

We also publish plain alternative pages if you're specifically comparing Acronis, Datto, Axcient, or Cove. Those pages are for product fit. This post is for the move.

Keep the migration boring

Write down the fleet. Protect the old restore points. Run both platforms until the new history is real. Test restores on a pilot. Tell clients only what they need. Time the cancel around the contract, not the frustration.

Do that, and switching backup vendors stops being a project that haunts the next quarter. It becomes a checklist you work through once, then don't think about again.

If you want help walking a real client list through it, call us at (888) 933-2975, 9am to 9pm Eastern, Monday to Friday — or start the 14-day trial and bring the inventory sheet with you.