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.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Migrating to alternative RMM vendors like Datto RMM, N-Able, NinjaOne, or GoreloDid this help you?
- 2Staying on legacy versions like VSA9 until forced to change by end-of-life datesDid this help you?
- 3Moving core operations around Intune and keeping basic tools only for remote accessDid this help you?
- 4Checking out alternative tools like NinjaOne or DattoDid this help you?
- 5Switching to Microsoft IntuneDid this help you?
- 6Staying with the same account manager and sticking with the new version path forwardDid this help you?
- 7Maintain 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.Did this help you?
- 8Buy entirely new devices for the destination tenant.Did this help you?
- 9Evaluating alternative CRM platforms like Microsoft Dynamics, HubSpot, or PipedriveDid this help you?
- 10Staying on the current platform and questioning whether the roadmap justifies the costDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, 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 ↗
“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 ↗
“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 ↗
“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 ↗
Where this came up
People with this problem also raised
- 14Why is it so hard to export and switch accounting software?
- 8How to migrate company email from Google Workspace to Microsoft 365
- 8Migrating a child Active Directory into a parent domain
- 10How to migrate scary legacy software nobody wants to touch
- 3How to manage software updates across multiple client accounts
- 3How to move an online community without losing members