Said It Here

How to migrate remote management platforms without rebuilding everything

Forcing a migration between management platforms requires completely rebuilding years of established policies, scripts, automation, and patching across thousands of endpoints. This massive operational friction drains engineering resources and leaves teams exhausted by repeated, vendor-pushed transitions.

What people tried

Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.

  1. 1
    Migrating to alternative RMM vendors like Datto RMM, N-Able, NinjaOne, or Gorelo
  2. 2
    Staying on legacy versions like VSA9 until forced to change by end-of-life dates
  3. 3
    Moving core operations around Intune and keeping basic tools only for remote access
  4. 4
    Checking out alternative tools like NinjaOne or Datto
  5. 5
    Switching to Microsoft Intune
  6. 6
    Staying with the same account manager and sticking with the new version path forward
  7. 7
    Maintain the old tenant while stopping the addition of new devices, pointing all existing devices to the new parent MDM server until they are phased out or retired.
  8. 8
    Buy entirely new devices for the destination tenant.
  9. 9
    Evaluating alternative CRM platforms like Microsoft Dynamics, HubSpot, or Pipedrive
  10. 10
    Staying on the current platform and questioning whether the roadmap justifies the cost

In their words

Unedited, most upvoted first, each linked to the thread it came from.

“My CRO wants me to use Dreamforce to determine if we believe Salesforce’s roadmap enough to stick around or (his preference) switch off the platform for good.”source ↗

“Besides the horrifying costs associated with actually switching vendors, has anyone successfully transitioned their company? What platform did you use and was it actually that much better?”source ↗

flightlesslark · r/salesforce · 35 upvotes

“We put a significant amount of time into migrating, rebuilding policies, scripts, automation, patching, monitoring, reporting, etc.”source ↗

“It’s not just installing a different agent. You’re talking about rebuilding years of policies, automation, scripts, monitoring, patching, documentation, integrations, training your techs, and then dealing with the transition across thousands of endpoints.”source ↗

“What really pisses me off is that we already went through a major transition because VSAX was presented as the direction we should be moving in. Now we’re basically preparing to do it all over again — to another Kaseya-owned product.”source ↗

Putrid_Pay_3930 · r/msp · 21 upvotes

“I'm surprised to discover that Apple does not provide a 'clean' way to migrate devices from one ABM to another through a M&A process.”source ↗

“When I called support, they indicate that devices must be 'manually' moved - meaning we need to de-register and manually add them in the destination tenant.”source ↗

kingjames2727 · r/sysadmin · 21 upvotes

“It looks like VSA9 has less than a year left before EOL.”source ↗

“is there anyone here who can share their experiences with migrating from 9 to 10? I wanted to get an idea of some of the major differences for good or bad from someone that isnt trying to sell the tool to me.”source ↗

Sufficient_Event_991 · r/sysadmin · 2 upvotes

Where this came up

r/mspr/salesforcer/sysadminit managementsoftware migration

People with this problem also raised