Stability IT, a managed service provider based in Prestatyn, North Wales, has successfully migrated its remote monitoring and management (RMM) operations from Kaseya VSA 9 to Datto RMM. What makes their approach noteworthy is the meticulous execution—scripting the new agent deployment through the very platform they were leaving, and rolling out the migration in carefully managed client batches. This strategy eliminated the downtime and data gaps that often plague RMM transitions, offering a repeatable model for other MSPs eyeing a similar move.
For many service providers, the thought of switching RMM platforms is daunting. Years of accumulated configurations, patch management policies, monitoring templates, and agent footprints create a web of dependencies that is difficult to untangle. Yet Stability IT not only untangled it—they did so with precision, leveraging their existing Kaseya VSA instance as the engine to deploy Datto RMM agents, monitor the transition, and eventually sunset the old platform.
Why Leave Kaseya VSA 9?
While Stability IT did not publicly cite a single breaking point, the broader MSP community has been reevaluating its relationship with Kaseya since the July 2021 REvil ransomware attack that exploited VSA on-premises servers. That incident compromised up to 1,500 downstream businesses and shook confidence in the platform’s security architecture. Although Kaseya has since invested heavily in hardening VSA—rewriting the agent and moving to a fully SaaS-based VSA 10—many MSPs began exploring alternatives. Datto RMM, with its cloud-native design, strong security posture, and tight integration with Autotask PSA, emerged as a leading contender.
Stability IT’s decision likely followed a similar calculus: the need for a modern, secure, and more agile RMM that could scale with their growing client base. Datto RMM’s intuitive interface, rapid deployment via web-based agents, and robust automation capabilities made it an attractive target platform.
The Migration Strategy: Turning VSA Against Itself
The most ingenious aspect of Stability IT’s migration was using Kaseya VSA to deploy the Datto RMM agent. Typically, MSPs either manually install new agents or use a third-party deployment tool during migrations. By scripting the installation through VSA’s existing procedure engine, Stability IT achieved several advantages:
- Consistent, silent deployment across thousands of endpoints without interrupting end users.
- Centralized control and monitoring from the very console they were deprecating, giving them real-time visibility into installation success rates.
- Immediate rollback capability—if a newly deployed Datto agent caused issues, they could quickly revert using VSA procedures.
- Low overhead, as no additional deployment infrastructure was required.
This approach required careful planning. The team first built a Datto RMM site, configured core policies, and set up automated monitoring templates. Then they created a VSA script that would download and execute the Datto agent installer with the correct site token and silent switches. The script also logged the outcome, enabling the team to track progress across machines.
Phased Rollout: Batching for Safety and Control
Instead of a big-bang migration, Stability IT organized clients into batches based on risk profile, size, and technical complexity. Highly sensitive or complex environments were migrated only after the process had proven itself on less critical systems. Each batch was monitored for several days to ensure stability, patching compliance, and monitoring data continuity before the next group was added.
This phased approach also allowed the team to refine their Datto RMM policies gradually. For example, they discovered that some legacy Windows Server 2012 instances required a specific .NET Framework version before the Datto agent would function correctly. By catching this early, they pre-emptively added a prerequisite check to their deployment script for subsequent batches, avoiding delays.
Benefits Realized Post-Migration
Once the migration was complete and the Kaseya VSA server was powered down, Stability IT reported measurable improvements:
- Faster reporting and alerting thanks to Datto RMM’s cloud-based data processing.
- Simplified policy management—inheritable policies reduced administrative overhead compared to VSA’s more fragmented procedure model.
- Better integration with Autotask PSA, enabling ticket creation from alerts with richer context and less manual mapping.
- Enhanced remote control performance, especially for low-bandwidth connections.
Moreover, the team found that Datto RMM’s modern web interface reduced onboarding time for new technicians. The platform’s drag-and-drop automation editor, ComStore scripts, and out-of-the-box monitoring templates meant less time writing custom monitors and more time addressing proactive maintenance.
Lessons for MSPs Considering a Similar Move
Stability IT’s migration offers several key takeaways:
- Use your current RMM to deploy the new one. This might seem counterintuitive, but it provides a controlled, low-friction pathway.
- Phase the rollout and group clients thoughtfully. Avoid migrating all clients at once; instead, categorize by risk and technical debt.
- Invest time in policy mapping before the first agent install. The more work done on the Datto RMM side in advance, the smoother the switch.
- Monitor both platforms in parallel for a short overlap period. This ensures no gap in coverage and allows for side-by-side alert comparison.
- Document every step and build rollback procedures. Even the best plan can hit a snag, so be ready to revert.
For MSPs still running Kaseya VSA 9 on-premises, the end-of-support clock is ticking. Kaseya has stated that VSA 9 will reach its end of life in the coming years, pushing users toward the SaaS-based VSA 10 or other solutions. A migration like Stability IT’s can serve as a practical template—whether the destination is Datto RMM, NinjaOne, or another platform.
The Bigger Picture: RMM Market Consolidation and Evolution
The managed services industry is witnessing a wave of consolidation. Kaseya itself acquired Datto in 2022, creating a massive portfolio that includes VSA, Datto RMM, IT Glue, and Autotask. This blurring of boundaries means MSPs must carefully evaluate each tool’s roadmap. While some fear that Datto RMM might eventually be merged into VSA, others view Datto’s strong product identity and engineering culture as a reason to trust its continued development.
Stability IT’s choice, made under such market dynamics, underscores a pragmatic truth: the best RMM is the one that empowers technicians to work efficiently and securely. For them, Datto RMM checked all the boxes—cloud reliability, deep PSA integration, and a straightforward migration path—while VSA 9 represented yesterday’s architecture.
Conclusion
Stability IT’s journey from Kaseya VSA 9 to Datto RMM stands as a masterclass in controlled, scripted migration. By turning their legacy RMM into a deployment engine and adopting a phased strategy, they avoided the pitfalls that derail many such projects. MSPs of all sizes can draw inspiration from their methodical approach, which ultimately led to a more resilient and efficient operations stack.
As the RMM landscape continues to shift, one thing remains constant: the need for meticulous execution when the stakes involve every endpoint under management. Stability IT proved that with the right plan, even a complex migration can be, in the end, a success story worth sharing.