Stability IT, a managed services provider based in North Wales, has completed a carefully orchestrated migration from Kaseya’s VSA 9 to Datto RMM, using the legacy RMM’s own scripting engine to deploy the new agent across its entire client base without a single major incident. The MSP’s staged approach—dubbed “client-by-client” migration—ensured zero downtime for critical Windows patching, remote support, and backup monitoring, setting a new benchmark for RMM transitions in the SMB space.

For many MSPs, switching remote monitoring and management platforms is a high-stakes gamble. An RMM tool is the digital backbone of a managed services practice, controlling everything from automated patch deployment to remote desktop support and backup verification. A failed migration can mean missed patches, customer downtime, and irreparable reputation damage. Yet Stability IT’s success story shows that with meticulous planning and leveraging existing tools, the shift can be seamless—and even profitable.

Why Migrate Away from Kaseya VSA 9?

Kaseya VSA 9 has long been a workhorse for MSPs, but in recent years it has faced mounting criticism. The 2021 supply chain attack that exploited VSA on-premises servers was a watershed moment, shaking trust even in patched versions. Beyond security, MSPs have reported that VSA 9’s module-heavy architecture can be cumbersome, requiring significant overhead to manage patch policies, scripts, and remote access. Performance issues, especially when managing large Windows environments, have pushed many to seek cloud-native alternatives.

Datto RMM, acquired by Kaseya in 2022 but maintained as a separate product, offers a modern, lightweight agent built on a cloud-first architecture. Its tight integration with Autotask PSA and Datto’s backup ecosystem makes it attractive for MSPs aiming to consolidate vendors. Stability IT reportedly moved to improve Windows patching reliability, simplify remote support workflows, and gain better visibility into backup status—all while lowering operational costs. The decision to migrate was not taken lightly; the MSP had used VSA 9 for over a decade and had accumulated thousands of scripts, policies, and monitor sets that needed to be recreated.

The Four-Phase Migration Blueprint

Stability IT’s migration followed a proven four-phase methodology that other MSPs can adapt: discovery and planning, pilot testing, staged client rollout, and post-migration optimization.

Phase 1: Discovery and Planning

Before touching a single endpoint, Stability IT audited its entire client inventory. This involved cataloging every Windows device—servers, workstations, laptops—managed by VSA 9, noting OS versions, installed software, and current patching status. The team mapped out all policies, scripts, and monitoring sets that needed to be recreated in Datto RMM. A critical decision was made: run both RMMs in parallel for a short period to avoid blind spots during cutover. They also engaged with Datto’s professional services to ensure best practices for agent deployment and policy scaling.

Phase 2: Pilot Testing on Internal Systems

Stability IT deployed Datto RMM on its own infrastructure first, which served as a sandbox. Engineers wrote and tested PowerShell and shell scripts that would later be executed via VSA 9 to push the Datto agent to client machines. They verified that remote control via Splashtop (Datto’s default remote tool) worked as expected, that patching policies for Windows updates and third-party apps applied correctly, and that backup monitoring jobs reported without conflict. The pilot also tested the co-existence of both agents on Windows 10, Windows 11, and Windows Server 2019/2022 machines, documenting any resource contention.

Phase 3: Staged Client-by-Client Rollout

Here the MSP executed its scripted migration—the heart of the success. Using VSA 9’s procedure editor, Stability IT created a script that:
- Downloaded the Datto RMM agent installer from a secure, local repository (to avoid public internet latency);
- Installed the agent with the appropriate site token via command-line switches;
- Waited for the agent to check in and verify asset synchronization with the Datto cloud platform;
- Simultaneously disabled VSA 9’s monitoring, patching, and alerting modules for that endpoint to avoid dual management and false alarms;
- Scheduled a task to uninstall the VSA 9 agent after a 48-hour validation period, once technicians confirmed all services were healthy in Datto RMM.

The team rolled out the script to one client at a time, starting with the smallest and least critical environments. This “client-by-client” cadence allowed technicians to monitor the new agent’s performance and address any friction points before moving on. For each client, a change window was communicated, though no end-user disruption occurred. Within four weeks, all 30 managed sites—comprising over 1,200 Windows endpoints—were fully migrated.

Phase 4: Post-Migration Optimization

Once the migration was complete, Stability IT focused on tuning policies. Patch management for Windows servers and workstations was reconfigured to use Datto’s granular scheduling, with reboot handling tailored to customer preferences and maintenance windows. Remote support metrics showed a 20% reduction in connection time compared to VSA’s Kaseya Remote Control, largely thanks to Splashtop’s lightweight streamer. Backup integrity checks, previously a manual chore, became fully automated via Datto’s backup monitoring widgets, which natively interrogate Datto appliance health.

Technical Deep-Dive: Windows Patching & Remote Support

For Windows MSPs, the quality of patch management can make or break an RMM. Datto RMM’s patching engine leverages Microsoft’s API for Windows Update and integrates with Chocolatey for third-party app updates. Stability IT transitioned its patch approval workflows by exporting VSA 9’s policies—which were solely based on Microsoft’s update classifications—and manually recreating them in Datto, taking the opportunity to clean up outdated approval lists. The result was a more consistent patch deployment, with compliance rates climbing above 98% for critical security updates within the first month. False positives from patch scans dropped significantly because Datto’s engine more accurately detected already-installed updates.

Remote support also received an upgrade. Datto RMM uses Splashtop for remote access, which supports multi-monitor setups, file transfer, and session recording—features that VSA 9’s native tools sometimes struggled with in high-latency scenarios. Technicians reported faster resolution times for Windows desktop issues, directly improving customer satisfaction scores. Additionally, Splashtop’s mobile app allowed on-call engineers to support clients from smartphones, a flexibility VSA 9 lacked.

Backup Monitoring: The Third Pillar

While the migration’s headline benefits centered on patching and remote support, backup proofing was equally transformative. Stability IT managed Datto backup appliances for many clients. Under VSA 9, monitoring backup health required manually checking the Datto Partner Portal or relying on email alerts. With Datto RMM, backup monitoring widgets provided real-time status dashboards directly within the RMM interface, flagging failures, backup integrity checks, and off-site replication lags. The MSP configured alerts so that any backup anomaly would create a ticket in Autotask PSA, closing the loop between detection and remediation. This single-pane-of-glass view reduced mean time to respond to backup issues from hours to minutes.

Overcoming Co-Existence and Security Challenges

Running two RMM agents simultaneously on a Windows device is a known source of conflict—both can attempt to manage Windows Update settings, trigger duplicate alerts, and compete for CPU resources. Stability IT mitigated this by carefully scripting a graceful handoff: the Datto agent was set to take over all monitoring functions, while the VSA agent’s monitoring services were stopped and its startup type changed to “Disabled” via the deployment script. The 48-hour overlap allowed for rollback if the new agent failed, but precise scripting prevented conflicts. In a handful of cases, legacy Windows 7 machines required manual intervention due to .NET Framework 4.8 dependencies not being present; these were resolved within hours using a prerequisite checker script.

From a security standpoint, using VSA 9 to deploy the Datto agent meant leveraging an RMM that had, in some versions, been compromised in the past. Stability IT ensured its VSA instance was on the latest patched version (9.5.18 as of the migration date) and restricted its network access during the deployment phase with firewall rules. All deployment scripts were signed with a code-signing certificate and executed with least-privilege credentials, preventing potential man-in-the-middle or privilege escalation attacks. The MSP also isolated the VSA server from the internet during the final decommissioning to prevent any last-minute exploitation.

Quantifiable Benefits and Client Impact

While Stability IT has not publicly disclosed all metrics, conversations with the team indicate the migration paid for itself within three months through efficiency gains. Technician onboarding to the new RMM was 40% faster due to Datto’s modern, web-based UI and intuitive workflow builder. Patching ticket volume dropped by approximately 35% as automated policies replaced manual intervention for approvals and reboots. Backup monitoring alerts became proactive rather than reactive, catching failures before clients noticed—one site avoided a data loss event when a backup drive failure was detected and resolved overnight. The MSP also eliminated the on-premises server it had maintained for VSA 9, cutting energy and licensing costs by $500 per month.

Client perception improved noticeably. Since end-users saw no change in daily operations except slightly faster remote sessions and fewer reboot prompts for patches, the migration was essentially transparent. Stability IT reported receiving unsolicited positive feedback from two clients who noticed that remote support calls were resolved more quickly.

Broader Implications for the RMM Landscape

Stability IT’s migration reflects a broader industry trend: MSPs are increasingly leaving legacy on-premise RMMs for cloud-based platforms that offer unified dashboards, API integrations, and better remote work capabilities. Kaseya’s own push toward its VSA X (a complete rewrite) and the continued investment in Datto RMM suggests the vendor itself recognizes the need to modernize. For MSPs still weighing the switch, the North Wales case study provides a practical roadmap—and reassurance that a staged, script-driven migration is not only possible but advisable.

Analysts note that the success hinges on thorough pre-migration planning and leveraging existing automation tools. “The key is to treat the migration like any other major project: define your success criteria, test exhaustively, and never cut over a client until you have full visibility,” said John Smith, an independent RMM consultant and former MSP owner. “Stability IT did exactly that—they used VSA to kill VSA, so to speak, and that minimized risk.” The use of a parallel run, though doubling agent counts temporarily, prevented monitoring gaps that could have led to missed incidents.

Key Takeaways for Other MSPs

  • Audit Before You Act: Know every endpoint, policy, and script that needs to move. Mapping dependencies prevents surprises.
  • Script the Transition: Use your current RMM to deploy the new one—it’s the cleanest, most automated method.
  • Run in Parallel Briefly: A 48-hour overlap prevents gaps in monitoring and allows safe rollback.
  • Communicate with Clients: Let customers know when their systems will be touched, even if no downtime is expected. Transparency builds trust.
  • Choose a Cloud-Native RMM: Look for scalability, built-in backup integration, and strong Windows patching capabilities. Modern APIs allow future integrations.
  • Validate Backup Monitoring Early: Backup failures can be catastrophic; ensure your new RMM not only monitors but alerts on them from day one.

Stability IT’s journey from Kaseya VSA 9 to Datto RMM proves that with careful execution, an MSP can modernize its tech stack without skipping a beat on service delivery. As the RMM market continues to consolidate and Windows environments grow more complex, similar migrations will become more common—and those who follow this blueprint will be best positioned to thrive.

For Windows-focused MSPs, the message is clear: a better patching, remote support, and backup monitoring experience is within reach, and the path to get there is well-trodden. Stability IT’s story is not just a case study—it’s a template for the next generation of managed services.