Stability IT’s Staged VSA 9 to Datto RMM Migration: Patch, Remote, Backup Proof

ChatGPT · Jun 20, 2026

Stability IT, a managed service provider in Prestatyn, North Wales, moved from Kaseya VSA 9 to Datto RMM by scripting the Datto agent deployment through VSA itself, migrating clients in batches, and running both platforms side by side for several weeks. The headline is not merely that the migration worked; it is that the migration became a proof point for a broader operational bet. Stability IT’s story is a case study in what happens when an MSP stops treating remote access, patching, backup, endpoint security, and documentation as separate islands. The result was less drama, better compliance visibility, faster support, and a clearer commercial model.

The Real Migration Was Away From Tool Sprawl

Most MSP platform stories are dressed up as product switches, but the more interesting ones are usually about operational philosophy. Stability IT did not simply replace one console with another. It moved from a history of stitched-together tools toward a model where the core work of managed services could be run from a smaller number of connected systems.
That distinction matters because tool sprawl is not just an annoyance for technicians. It becomes a tax on every ticket, every compliance conversation, every client onboarding, and every renewal cycle. A technician who has to check one console for remote access, another for patching, another for endpoint security, another for backup, and another for documentation is not working in a modern stack; they are acting as the integration layer.
Stability IT’s path reflects a familiar MSP progression. The company began with remote support as the immediate need, using ConnectWise ScreenConnect for access into client machines. That solved the narrow problem of getting onto endpoints, but it did not solve the larger problem of managing them.
The business then adopted VSA 9 as a fuller RMM platform, gaining automation, monitoring, patching, and remote support in one place. That was already a substantial step forward from the ScreenConnect-plus-WSUS-plus-PRTG world. But as the client base grew, the limits of that arrangement became clearer: the company needed not merely an RMM, but a management plane that technicians trusted enough to use all day.
That is where Datto RMM entered the story. Stability IT tested it with a single client, let technicians work in it alongside VSA, and listened to the feedback. According to managing director Mark Davies, the reaction was immediate: staff wanted to know why all clients were not already on the newer platform.

Stability IT Let Technicians Vote With Their Workflow

There is a reason successful migrations often start with one client rather than a spreadsheet. A pilot exposes what vendor demos cannot: how a product behaves under ordinary pressure, with real endpoints, real tickets, and real technicians trying to finish work before the next call arrives.
Stability IT’s pilot worked because it was not framed as a ceremonial trial. The company gave technicians a direct comparison between VSA 9 and Datto RMM and allowed the day-to-day experience to matter. Faster navigation, a more modern interface, stronger remote access, and better integration potential were not cosmetic details; they were the difference between friction and flow.
That is often where MSP platform decisions become emotional, even when they are justified in hard numbers. Technicians develop strong opinions about tools because the tools mediate nearly every client interaction. A sluggish remote session, a confusing device view, or a patching workflow that requires too many manual checks does not remain a back-office inconvenience. It leaks into client experience.
Davies’ reported comment that “things were just quicker” is simple, but it captures the actual stakes. Speed in an MSP is not only about shaving seconds from a remote connection. It is about reducing uncertainty. The faster a technician can see the endpoint, trust the data, connect to the user, apply the fix, and document the result, the less operational noise accumulates across the day.
The migration therefore became less a risky platform change than a controlled expansion of something the team had already validated. That sequencing is why the move appears to have avoided the common failure mode of MSP migrations: imposing a new platform on technicians before proving that it improves their work.

VSA Became the Bridge Instead of the Anchor

The most elegant part of Stability IT’s migration is that the old platform helped deploy the new one. Rather than touching every endpoint manually or treating the transition as a forklift move, the team used VSA 9 to push out the Datto RMM agent across client environments.
That move turned a potential migration liability into an asset. VSA already had presence across the estate, and Stability IT used that reach to script the rollout. Clients were moved in batches, with another client environment arriving in Datto RMM each morning. Once a client was confirmed on the new platform, it was removed from VSA.
This is how infrastructure migrations should look when they are designed around operational continuity. There was no grand cutover weekend, no big-bang switch, and no need to ask technicians to pretend that a half-complete migration was already finished. For a few weeks, both systems existed in parallel, and technicians worked from whichever platform held the relevant client.
That overlap period is easy to underestimate. It gives an MSP room to catch exceptions, compare results, and prevent client-facing disruption. It also acknowledges the reality that managed service providers rarely have the luxury of stopping normal work while rebuilding their tooling underneath it.
Davies said the move from VSA 9 to Datto RMM was smoother than the earlier shift from ScreenConnect. That makes sense. By then, Stability IT already understood the operating model of a full RMM. The team was not learning centralized endpoint management for the first time; it was moving between related platforms inside the Kaseya portfolio, with surrounding products such as Datto AV, Datto EDR, Endpoint Backup, and IT Glue already part of the company’s orbit.
The lesson is not that every MSP should stay inside a single vendor ecosystem at all costs. The lesson is that migration risk falls sharply when the starting point, destination, deployment method, and technician workflow are all considered together. Stability IT’s move was smooth because it was staged as an operational process, not a procurement event.

Patching Was the Pain Point That Made Consolidation Concrete

Remote access may define the technician experience, but patching often defines the MSP’s credibility. It is the work clients rarely notice when it succeeds and immediately question when it fails. For Stability IT, patching before Datto RMM was the operational headache that made the case for centralization impossible to ignore.
The old model relied on Windows Server Update Services at client sites. WSUS can be perfectly serviceable in the right environment, especially for organizations with dedicated infrastructure and disciplined administration. But for an MSP managing many small and mid-market clients, requiring a server at every site creates a distributed maintenance burden that scales badly.
Each WSUS instance had to be configured, maintained, and monitored separately. When it worked, it worked. When it failed, Stability IT could spend days troubleshooting. The more troubling problem, according to Davies, was that the team might not know the state of patching until someone logged into the WSUS server and discovered that it was not working.
That is the nightmare version of compliance: not failure, but invisible failure. A failed patch process can be remediated once it is known. A patch process that silently drifts out of health creates false confidence, and false confidence is dangerous for both security and client trust.
Datto RMM changed that by pulling patching into a single dashboard across clients. Policies could be managed centrally. Compliance could be viewed at a glance. The company no longer needed an on-site patching server at each client merely to maintain basic Windows update discipline.
The reported result is striking: Stability IT now maintains more than 97 percent patch compliance across more than 1,800 endpoints. The remaining roughly 3 percent are not invisible stragglers, but clients with specific policies preventing automatic Windows updates. Even those are monitored, which is the real operational win. The company knows where the exceptions are.

Compliance Turns Visibility Into a Commercial Requirement

Patch compliance is not merely a security hygiene metric for Stability IT’s market. For clients pursuing Cyber Essentials certification in the United Kingdom, the ability to patch within required windows and demonstrate control over endpoints is commercially meaningful.
Cyber Essentials has increasingly emphasized timely remediation of high-risk and critical updates, with a 14-day window sitting at the center of the patching conversation. For an MSP, that kind of requirement changes the value of an RMM dashboard. It is no longer just a technical convenience; it becomes part of the evidence chain that clients need to satisfy insurers, customers, suppliers, and assessors.
This is where centralized tooling moves from “nice to have” to strategic. An MSP can promise patching discipline with almost any stack. The harder part is proving that discipline across a mixed client base, including servers, workstations, machines that are offline, devices with exceptions, and environments where business applications may object to updates.
Stability IT’s old WSUS model made that harder because the truth lived separately at each site. Datto RMM makes the truth easier to see because policy state, endpoint state, and exception state are closer to the same pane of glass. That does not eliminate the human work of patch governance, but it reduces the number of places where drift can hide.
For Windows administrators, this is the part of the case study that should resonate most. Patch management failures are often blamed on users, maintenance windows, or temperamental endpoints. But many failures are really visibility failures. If the management layer cannot quickly distinguish between patched, pending, failed, excluded, and unmanaged devices, the MSP is operating on hope.
The phrase 97 percent patch compliance sounds like a marketing stat. In practice, its value depends on whether the remaining 3 percent are understood. Stability IT’s claim is more persuasive because the exception category is described: some clients have policies that prevent automatic Windows updates, and those systems are still monitored. That is what mature compliance looks like. Not perfection, but controlled imperfection.

Remote Access Is Where Platform Strategy Meets Human Patience

For Stability IT, almost all support work is remote. That makes the remote access layer more than a feature. It is the front door to the client relationship.
If remote access is slow, unreliable, or awkward, every other operational improvement becomes harder to appreciate. A technician may have perfect patch data and clean documentation, but if the remote session fails while a user is waiting on the phone, the client experiences the service as broken. Remote control tools therefore carry an outsized emotional weight in MSP environments.
Datto RMM’s Web Remote appears to have become Stability IT’s default remote access method, helped by recent improvements and the surrounding Agent Browser workflow. The Agent Browser matters because it allows technicians to perform tasks on a machine without necessarily taking over the user’s active session. That distinction can reduce disruption, especially for quick checks, background work, or administrative tasks that do not require a full interactive remote control session.
The consent workflow also matters. When a technician connects, the client sees a prompt identifying the technician by name and must approve the session. This is not just a security nicety. In an era of support scams and social engineering, visible technician identity gives end users a simple trust cue: the person on the phone matches the person requesting access.
Davies described the process in practical terms: the client confirms they are speaking with the right person, approves the prompt, and the technician is in. That kind of mundane smoothness is exactly what remote support should feel like. The best remote access experience is not spectacular; it is uneventful.
Stability IT reports more than 50 percent faster remote support, with most support calls resolved in under 10 minutes and a target of first-contact resolution within 15 minutes. Those numbers should be read as a combined effect of tooling, process, and technician familiarity rather than as a magic property of any single button. Still, the operational point stands: when the remote session starts quickly and the technician trusts the console, support velocity improves.

The Security Story Is Also a Workflow Story

The broader Kaseya stack enters the case study through security, backup, and documentation. Stability IT had been using Bitdefender for antivirus, Veeam for workstation backup scenarios, and IT Glue for documentation. After the Datto RMM move, the company began consolidating more of those functions into Kaseya 365 Endpoint.
The antivirus and EDR migration followed a pragmatic path. Stability IT trialed Datto AV and EDR internally, confirmed that the tools met its standards, and then migrated clients as Bitdefender renewals came up. That renewal-based cadence is important because it avoids turning consolidation into unnecessary disruption. The company reports that about 90 percent of clients are now on Datto EDR, with the remainder still in progress.
Endpoint backup appears to have produced a more dramatic operational change. Previously, backing up workstations with Veeam required attention to physical backup infrastructure at the client site, available storage, and whether the machine could reach the local server. That model made sense for certain server-centric backup architectures, but it left workstation coverage constrained by logistics and perceived value.
Kaseya 365 Endpoint Backup changed the economics by making endpoint backup part of the subscription model and manageable through Datto RMM. Davies described it as a “game changer” because clients expect to pay for server backup but often do not think in the same way about workstations. When backup becomes easier to package and manage, the MSP can cover devices it previously might not have bothered to protect.
That is not merely an upsell story. Workstations increasingly hold business-critical data, browser profiles, local caches, application state, and user-created files that may not always be cleanly redirected to cloud storage. A backup model that extends more naturally to endpoints can close a real resilience gap.
IT Glue integration rounds out the workflow picture. The ability to inject passwords directly into RMM remote control sessions sounds small until you multiply it across dozens of daily connections. Every avoided copy-paste, every reduced context switch, and every cleaner credential workflow matters in an MSP where the ticket queue never stops moving.

The Margin Gain Explains Why Bundles Keep Winning

Kaseya 365 Endpoint’s commercial pitch is straightforward: bundle endpoint management, security, backup, and automation into a per-endpoint subscription. Stability IT’s reported numbers show why that pitch is attractive to MSPs even when individual point tools may still have strong defenders.
The company says it has achieved an 8 percent increase in managed services margins since consolidating. The mechanism is not mysterious. If a bundled license covers products the MSP was already buying separately, then additional included services can become either margin, upsell opportunity, or both.
Davies put it plainly: the license cost is largely covered by one of the products the company would have paid for anyway. That gives Stability IT room to sell additional services, improve profitability, and reduce the administrative burden of managing multiple vendor subscriptions and renewal cycles.
This is the business logic behind platform consolidation across the MSP market. Vendors sell it as simplicity. Technicians feel it as workflow reduction. Owners see it as margin expansion. Clients experience it, ideally, as more consistent service without needing to understand the stack underneath.
But the bundled model deserves scrutiny, too. Consolidation can create dependency. An MSP that standardizes heavily on one vendor gains integration but may lose negotiating leverage and optionality. If service quality declines, pricing changes, or a product module lags a specialist competitor, the cost of unwinding the bundle can be substantial.
That is why Stability IT’s staged approach matters. The company did not appear to move everything blindly because it was available in the bundle. It trialed Datto RMM with a client, tested AV and EDR internally, migrated around renewal cycles, and used technician feedback as an input. The strongest argument for consolidation is not that fewer vendors are always better. It is that fewer vendors are better when the integrated workflow demonstrably improves the operation.
The 8 percent margin increase is therefore not just a financial statistic. It is evidence that the operational consolidation had commercial consequences. In the MSP business, those two things are inseparable. A tool that saves technician time but destroys margin is hard to sustain; a tool that improves margin but frustrates technicians eventually damages service quality. Stability IT’s case is compelling because both sides moved in the right direction.

Windows Admins Should Notice the Direction of Travel

For Windows-focused readers, the Stability IT story is interesting because it captures a broader shift in endpoint management. The old world relied heavily on site-bound infrastructure, local servers, and separate tools stitched together by administrator habit. The newer model is cloud-managed, policy-driven, and integrated with security and backup by default.
That shift is not absolute. WSUS, traditional backup servers, and specialist remote access tools still have roles. Many organizations have constraints that make cloud-first management complicated, especially where legacy applications, regulated environments, or strict data residency requirements are involved.
But the center of gravity is moving. MSPs supporting small and mid-market clients increasingly need fleet-level visibility more than site-level ritual. They need to know which endpoints are compliant, which are drifting, which are protected by EDR, which are backed up, and which can be accessed without a technician losing five minutes to connection drama.
Datto RMM, in this story, is the operational hub. Kaseya 365 Endpoint is the commercial wrapper. IT Glue, Datto AV, Datto EDR, and Endpoint Backup are the surrounding services that make the hub more valuable. The product names matter less than the architecture: one agent-driven management layer, one policy model, fewer disconnected portals, and more automation.
That architecture maps closely to how MSP work is actually performed. A client calls. A ticket opens. The technician needs context, access, credentials, device health, patch state, security status, and sometimes backup posture. The closer those facts are to one workflow, the less the MSP depends on individual heroics.
This is the unglamorous promise of modern RMM: not that it replaces expertise, but that it lets expertise travel faster. A skilled technician should be spending time diagnosing and deciding, not hunting across portals to establish whether the endpoint is even in a known state.

The Useful Lesson Is the Migration Pattern, Not the Vendor Logo

It would be easy to read Stability IT’s story as a simple endorsement of Datto RMM over VSA 9, or Kaseya’s broader platform over a collection of rival tools. That is the surface-level reading. The deeper lesson is about migration design.
The company made the move work by reducing uncertainty at each step. It tested Datto RMM with one client. It let technicians compare the platforms in live use. It used the existing RMM to deploy the new agent. It moved clients in batches. It ran both platforms in parallel. It removed clients from VSA only after confirming them in Datto RMM.
That sequence is a model other MSPs could adapt regardless of vendor. The specific tools will vary, but the pattern is broadly applicable: validate with real users, automate deployment through the existing management plane, avoid big-bang cutovers, preserve operational overlap, and retire the old system only when the new one is confirmed.
The other lesson is that the “smooth migration” was not only technical. Stability IT already had organizational familiarity with RMM concepts and Kaseya-adjacent products. That reduced training load and made the new platform feel like an evolution rather than a total reinvention.
Too many IT migrations fail because leaders focus on the destination state and underinvest in the transition state. Stability IT appears to have done the opposite. It treated the transition state as a first-class project phase, allowing technicians to work in both worlds while the client base moved across gradually.
That is especially important in MSP environments, where every migration has two audiences. The internal audience needs confidence that the new system is better. The external audience — clients — ideally should barely notice the move at all. Stability IT’s claim of no disruption suggests the migration met the higher standard: operational change without client drama.

The Numbers Tell a Coherent Story

Stability IT’s case study is unusually concrete because the claimed improvements reinforce one another. Better remote access explains faster ticket resolution. Centralized patch management explains stronger compliance visibility. Bundled endpoint services explain margin improvement. The migration method explains why the transition did not become a client-facing incident.
The most useful details are not the broad claims of modernization, but the operational specifics:

Stability IT used VSA 9 itself to deploy the Datto RMM agent, turning the legacy platform into the migration vehicle rather than treating it as an obstacle.
The company moved clients in batches and ran VSA 9 and Datto RMM side by side for several weeks, allowing technicians to keep working while the estate transitioned.
Patch compliance reportedly rose to more than 97 percent across more than 1,800 endpoints, with the remaining exceptions still visible in monitoring mode.
Remote support became more than 50 percent faster, with most calls reportedly resolved in under 10 minutes against a 15-minute first-contact resolution target.
The broader consolidation into Kaseya 365 Endpoint reportedly increased managed services margins by 8 percent while reducing reliance on separate point products.

Those figures should not be treated as universal guarantees for every MSP considering a similar move. They are the outcome of Stability IT’s environment, process maturity, client mix, and commercial model. But they are coherent, and that coherence is what makes the story credible.
A faster remote tool alone would not explain an 8 percent margin lift. A bundled license alone would not explain better patch visibility. A smooth agent deployment alone would not explain technician enthusiasm. Together, the pieces describe an MSP that used a platform migration to simplify the operating system of the business.
Stability IT’s move from VSA 9 to Datto RMM is ultimately a reminder that the best infrastructure migrations are almost boring from the client’s point of view and transformative from the operator’s point of view. The company did not chase novelty for its own sake; it used a controlled migration to collapse complexity, expose patching truth, speed up remote work, and make bundled endpoint services commercially useful. For MSPs staring at their own sprawl of remote tools, patch servers, backup consoles, AV portals, and documentation workflows, the forward path is not necessarily to copy Stability IT’s stack exactly. It is to copy the discipline: pilot honestly, migrate deliberately, measure what improves, and make the management plane simple enough that technicians can trust it under pressure.

References

Primary source: Kaseya
Published: 2026-06-20T02:40:11.640407

How Stability IT Improved Operations with Datto RMM

Learn how Stability IT consolidated tools, reached 97% patch compliance, resolved support calls faster and increased MSP profitability.

www.kaseya.com
Related coverage: rmm.datto.com

The Datto RMM Agent and Agent Browser

An overview of the Datto RMM Agent and Agent Browser.

rmm.datto.com
Related coverage: edr.datto.com

Kaseya 365 Endpoint: Getting started with Datto EDR and Datto AV
Related coverage: helpdesk.kaseya.com

https://helpdesk.kaseya.com/hc/en-gb/articles/44059919330065-General-Network-Discovery-Info
Related coverage: help.one.kaseya.com

About Kaseya 365 Endpoint
Related coverage: help.bms.kaseya.com

BMS-Datto RMM integration

Related coverage: datto.com

datto-rmm-logo (2)

PDF document

www.datto.com

ChatGPT · Jun 22, 2026

Stability IT, a managed service provider in Prestatyn, North Wales, moved from Kaseya VSA 9 to Datto RMM by scripting the new agent deployment through VSA itself, migrating clients in batches, and running both platforms briefly until each customer was confirmed on the new system. The result, according to Kaseya’s case study, was not a dramatic weekend cutover but a controlled operational handoff. That distinction matters because RMM migrations usually fail less from technology than from disorder. Stability IT’s story is really about what happens when an MSP treats tool consolidation as a business redesign rather than a procurement exercise.

Stability IT Did Not Just Replace an RMM

The easy reading of the case is that Stability IT swapped one Kaseya remote monitoring and management platform for another. That is true as far as it goes, but it misses the operational point. The company was moving from a stack that had grown in layers toward a platform model where remote access, patching, security, backup, and documentation increasingly orbit the same control plane.
Stability IT supports roughly 80 clients and around 2,000 endpoints with a team of about 20 technicians. Nearly all of its work is remote, which means the RMM is not back-office plumbing. It is the daily workbench, the customer experience, and the difference between a 10-minute fix and a ticket that drags through the afternoon.
The company’s earlier setup reflected the way many MSP stacks evolve. ScreenConnect handled remote support, WSUS handled patching, PRTG handled monitoring, and other products filled in the remaining gaps. Each tool did a job, but the work of stitching them together fell on technicians.
That fragmentation is tolerable when an MSP is smaller. At scale, it becomes a tax on every ticket, every compliance check, and every new customer onboarding. Stability IT’s migration shows why many providers are now less interested in best-of-breed purity and more interested in reducing the number of places where operational truth can hide.

The Old Stack Was Functional Until It Became Friction

ScreenConnect gave Stability IT remote control, but not the broader automation and endpoint governance the business needed as it expanded. WSUS could patch Windows machines, but only through a site-by-site model that required infrastructure at each customer location. PRTG could monitor networks, but it did not solve the bigger question of how technicians should manage endpoints as a unified fleet.
That kind of stack is familiar to Windows admins because it mirrors the old enterprise rhythm. Build a server. Configure a role. Monitor the monitor. Then discover, often too late, that the thing meant to enforce consistency has quietly drifted out of compliance.
The pain point was not that WSUS never worked. It was that Stability IT could not always know quickly when it had stopped working. Mark Davies, the company’s managing director, described cases where the team would only discover a client’s patching state after logging into the WSUS server and finding a problem.
For MSPs, that uncertainty is more dangerous than a visible failure. A failed patch job with an alert can be worked. A failed patching process that remains invisible becomes a compliance risk, a security exposure, and eventually a credibility problem with customers who assume their provider already knows.

VSA 9 Was the Bridge, Not the Destination

The move from ScreenConnect and disconnected tooling into VSA 9 was Stability IT’s first real consolidation step. VSA 9 brought patching, monitoring, automation, and remote support into one RMM environment. For a company that had been operating without a full RMM, that was a meaningful upgrade.
But the case study frames VSA 9 less as a mistake than as a stage in maturity. Stability IT had to learn what it wanted from a full endpoint management platform before it could judge the next one. Once technicians were accustomed to automation, integrated monitoring, and centralized patching, their expectations changed.
That is where Datto RMM entered the story. Kaseya worked with Stability IT on a pilot migration for one client, giving technicians a chance to compare the two platforms directly rather than absorb a top-down tool mandate. The internal reaction, according to Davies, was immediate: technicians wanted to know why all clients were not already on Datto RMM.
This is a detail worth lingering on. In MSP operations, technician acceptance is not a soft metric. If the people handling tickets believe a platform is faster, clearer, and less obstructive, that affects ticket velocity, morale, escalation rates, and customer satisfaction.

The Migration Worked Because It Refused to Be Heroic

Most failed migrations have a mythology problem. Someone wants a clean break, a big-bang weekend, a heroic all-hands effort that proves the team can muscle through complexity. Stability IT chose the opposite.
The company used VSA 9 to deploy the Datto RMM agent across customer environments. It scripted the rollout, moved clients in batches, and confirmed each migration before removing that client from VSA. For several weeks, technicians could work in either system depending on where a customer still lived.
That temporary dual-platform period was not inefficiency. It was risk control. Instead of demanding that every endpoint, technician, and workflow cross the bridge at once, Stability IT let the migration proceed in daily increments.
Davies’ account of the process is almost boring, which is exactly the point. The team would arrive in the morning and find that another client had moved over. Kaseya provided hands-on support for the first client, then Stability IT took over the rest independently.
This is the kind of migration pattern IT leaders should prefer: scripted, reversible in practice, observable, and free from theatrical deadlines. A smooth migration is rarely smooth because the tool is magical. It is smooth because the operating model assumes something will need checking.

Patching Became a Dashboard Problem Instead of a Server Problem

The strongest operational claim in the case study is patching. Stability IT moved from a WSUS model requiring a server at each client site to Datto RMM’s centralized patch policy and compliance view. Kaseya says the company now maintains more than 97 percent patch compliance across more than 1,800 endpoints.
The remaining roughly 3 percent are not described as unknown failures. They are customers with policies that prevent automatic Windows updates, monitored so Stability IT can still see where they stand. That distinction matters because mature patch management is not merely about pushing updates; it is about knowing which exceptions are intentional.
For Windows environments, patching is where abstract security promises become operational reality. A dashboard does not eliminate the complexity of Microsoft updates, application compatibility, maintenance windows, reboots, or customer-specific constraints. But it does change the provider’s posture from hunting for status to managing visible exceptions.
That shift is especially important for customers pursuing Cyber Essentials certification, where patching timelines can become part of the compliance conversation. If a server must be patched within 14 days, the MSP needs evidence, not optimism. Central visibility gives technicians and account managers a shared basis for that conversation.
There is also a labor argument here. Every hour spent nursing a WSUS server at one customer is an hour not spent improving automation across all customers. The more Stability IT could turn patching into a policy-and-exception workflow, the more its technicians could operate like fleet managers instead of site custodians.

Remote Access Is Where Technicians Decide Whether a Platform Is Real

Remote access is often treated as a feature inside an RMM comparison matrix. For an all-remote support organization, it is closer to the steering wheel. If it is slow, unreliable, or awkward, every other feature inherits the frustration.
Stability IT reports more than 50 percent faster remote support, with most support calls now resolved in under 10 minutes and a target of first-contact resolution within 15 minutes. Those numbers come from the vendor case study, so they should be read as customer-reported outcomes in a marketing context. Still, they align with the operational logic of reducing friction in the technician’s primary workspace.
Datto RMM’s Web Remote is now Stability IT’s default remote access method, according to Davies. The Agent Browser also lets technicians perform tasks on a machine without taking over the user’s session. That is a small-sounding distinction with large practical consequences.
Anyone who has supported end users remotely knows the cost of interruption. Taking over a session can halt a customer’s work, create awkward pauses, and turn a background fix into a foreground event. If technicians can inspect, run tasks, or gather information without fully commandeering the desktop, support becomes less invasive.
The consent workflow also plays into trust. When a technician connects, the user sees a prompt identifying the technician by name and must approve the session. In a world of remote support scams and credential theft, explicit identity and consent are not just user-experience niceties. They are part of the security theater that actually deserves to exist.

The Kaseya Portfolio Is the Strategy and the Trade-Off

Stability IT’s migration is also a case study in Kaseya’s broader portfolio strategy. Datto RMM became the core, but the company also uses or is moving customers toward Datto AV, Datto EDR, Kaseya 365 Endpoint Backup, IT Glue, and MyGlue integrations. The operational pitch is simple: fewer portals, fewer renewal cycles, fewer awkward seams.
The appeal is obvious for MSPs. If one subscription covers endpoint management, security, backup, and automation, the provider can simplify procurement and potentially improve margin without changing customer pricing. Stability IT says it has seen an 8 percent margin increase on managed services since consolidating onto Kaseya 365 Endpoint.
That commercial result is not incidental. MSPs sell standardization as much as they sell support. The more uniform the underlying stack, the easier it becomes to train technicians, automate common tasks, price services, and onboard new clients.
But there is a real trade-off. Consolidation concentrates dependency. If an MSP builds heavily around one vendor’s platform, it gains integration and leverage but reduces the practical freedom to swap out individual layers later. The operational win can become a strategic lock-in if the vendor’s roadmap, pricing, or support quality diverges from the MSP’s needs.
That does not make Stability IT’s decision wrong. It makes it a decision with a shape. The company appears to have judged that the gains from integration, technician productivity, and margin outweighed the risks of deeper dependence on Kaseya’s ecosystem.

Backup Moved From Infrastructure Chore to Sellable Service

Endpoint backup is one of the more revealing parts of the story because it shows how tool consolidation changes not just operations but packaging. Stability IT previously used Veeam in a model that required attention to available space on a physical server at the client site and whether a workstation could reach that local infrastructure. That is a lot of conditional effort for machines that many customers do not even think to protect.
Kaseya 365 Endpoint Backup changed the economics. With backup included in the broader subscription and managed through Datto RMM, Stability IT could protect workstations it previously would not have bothered with and charge customers for storage on top. Davies called it a “game changer” because it made workstation backup easier to offer as an additional built-in service.
This is the MSP flywheel in miniature. A capability that is too awkward to deploy becomes a niche service or an exception. A capability that is easy to deploy becomes a standard offer. Once it is standard, it becomes easier to explain, price, monitor, and renew.
There is a customer education angle too. Many small and mid-market clients understand server backup because servers feel important. Workstations are often treated as disposable until a lost laptop, failed SSD, or ransomware incident proves otherwise. Bundled endpoint backup gives the MSP a way to turn that latent risk into a practical service conversation.
The more interesting point is that backup did not win here as a standalone product. It won because it became adjacent to the tool technicians already use. In MSP operations, adjacency is power.

Documentation Became Part of the Ticket Flow

The IT Glue and MyGlue integrations are less dramatic than patch compliance or margin expansion, but they may matter just as much day to day. Stability IT technicians can inject passwords directly into RMM remote control sessions from IT Glue. That is the kind of small workflow improvement that rarely headlines a case study but quietly compounds across hundreds of tickets.
Documentation has always been one of the MSP industry’s chronic weak spots. Everyone agrees it matters. Everyone promises to maintain it. Then the ticket queue spikes, a senior technician solves a problem from memory, and the knowledge base falls out of date again.
Integrating documentation into the technician’s workflow does not solve the cultural problem by itself. But it reduces the distance between knowing and doing. If the remote session, credentials, client context, and endpoint state are closer together, technicians are less tempted to improvise outside the system.
There is also a security implication. Password handling is safer when credentials do not have to be copied, pasted, messaged, or verbally relayed through ad hoc channels. The fewer manual moves a technician makes with privileged information, the fewer opportunities there are for leakage or error.
In that sense, Stability IT’s consolidation story is not only about speed. It is about reducing the number of informal practices that grow around fragmented tools.

The Numbers Are Marketing, but the Operational Pattern Is Credible

A vendor case study is not an independent audit. The 97 percent patch compliance figure, the 50 percent faster remote support claim, and the 8 percent margin increase all come from a customer success narrative published by Kaseya. Readers should treat them as reported outcomes, not universal benchmarks.
Yet the pattern behind the numbers is credible because it matches what MSPs routinely experience. Centralized patch policy tends to outperform scattered WSUS oversight when the provider has many clients. Faster remote access tends to improve ticket resolution when remote support is the default operating mode. Bundled licensing can improve margin when it replaces several overlapping subscriptions.
The more important lesson is not that Datto RMM will reproduce Stability IT’s metrics for every MSP. It is that operational simplification creates measurable surfaces. Once patching, remote support, backup, security, and documentation move closer together, the MSP can start managing performance as a system.
This is where the story moves beyond Kaseya. The MSP market is under pressure from customer security expectations, compliance frameworks, technician shortages, and margin compression. Tool sprawl makes all of those problems worse because it forces providers to spend scarce labor reconciling systems instead of improving service.
Stability IT’s move is therefore less a one-off success story than an example of where the industry is heading. The winning MSP stack is increasingly the one that lets a smaller team manage more endpoints with fewer blind spots.

The Lesson for Windows Shops Is Hidden in the Cutover

The most concrete lesson for Windows-focused MSPs and internal IT teams is not “buy Datto RMM.” It is that migration design matters as much as platform selection. Stability IT lowered risk by piloting one client, listening to technician feedback, scripting deployment through the incumbent tool, and overlapping old and new systems until each customer was confirmed.
That sequence is transferable. Whether the destination is Datto RMM, another RMM, Intune-centered management, or a hybrid endpoint platform, the core migration pattern remains useful. Start with a controlled pilot. Build deployment automation. Preserve visibility during the transition. Remove the old agent only after the new one is operational.
The use of VSA 9 to deploy the Datto RMM agent is particularly elegant. The old system became the delivery mechanism for the new one. That reduces manual endpoint handling and turns a potentially chaotic uninstall-reinstall process into a managed rollout.
It also sends a message to technicians. A migration that respects their workflow is more likely to earn their trust. A migration that dumps them into a new console on Monday morning and calls it transformation is just another management decision they have to survive.

Stability IT’s Migration Playbook Has a Few Sharp Edges

Stability IT’s case is strongest when read as a practical operating model rather than a product endorsement. The details that matter are concrete, repeatable, and mostly unglamorous. They show how an MSP can turn consolidation from a sales slogan into a sequence of controlled changes.

Stability IT used its existing VSA 9 deployment to script the Datto RMM agent rollout, turning the old platform into the migration vehicle rather than treating it as dead weight.
The company moved clients in batches and kept technicians working across both systems for several weeks, reducing the risk of a disruptive cutover.
Centralized patch management replaced site-by-site WSUS oversight, giving the team a single view of compliance across more than 1,800 endpoints.
Remote support improved because technicians gained faster access, a browser-based workflow, and tools that could perform tasks without taking over the user’s session.
Kaseya 365 Endpoint changed the commercial model by bundling capabilities Stability IT had previously bought separately, contributing to a reported 8 percent managed-services margin increase.
The deeper Kaseya integration simplified daily operations, but it also increased the importance of vendor trust, roadmap alignment, and exit planning.

The sharp edge is that consolidation should not be confused with passivity. A unified platform still needs governance, testing, exception handling, and commercial discipline. The MSP that treats bundling as a substitute for operational design will simply recreate sprawl inside a bigger box.
Stability IT’s move from VSA 9 to Datto RMM lands because it was not framed as a leap of faith. It was a staged migration from fragmented work toward a more centralized operating model, with technicians validating the tool before the whole customer base moved. For Windows admins and MSPs watching their own stacks accrete portals, agents, and renewal dates, the forward signal is clear: the next productivity gain may not come from adding another tool, but from finally making the existing ones stop arguing with each other.

References

Primary source: Kaseya
Published: 2026-06-22T10:52:07.866506

How Stability IT Improved Operations with Datto RMM

Learn how Stability IT consolidated tools, reached 97% patch compliance, resolved support calls faster and increased MSP profitability.

www.kaseya.com
Related coverage: help.vsa10.kaseya.com

Migrating from VSA 9

A phase-by-phase guide to ensuring a smooth and successful transition from VSA 9 to VSA 10.

help.vsa10.kaseya.com
Related coverage: help.vsa9.kaseya.com

Home Page
Related coverage: helpdesk.kaseya.com

9.5.22 Feature Release - 1st March 2025 – Kaseya

The VSA 9.5.22 feature release (build 9.5.22.7018) includes enhancements and fixes described in the following sections. For minimum...

helpdesk.kaseya.com
Related coverage: datto.com

Data Integrity Services Ramps Up Cloud and Security Services | Datto

Data Integrity Services, Inc. is a Florida-based managed service provider (MSP) with a strong focus on cybersecurity and cloud services.

www.datto.com
Related coverage: help.kaseya.com

https://help.kaseya.com/webhelp/EN/RN/9040000/ReleaseNotes_R94_Beta3.pdf

Navigation section

Stability IT’s Staged VSA 9 to Datto RMM Migration: Patch, Remote, Backup Proof

VSA 9 Was the Bridge Away From a More Fragmented Past​

Patching Was the Real Business Case Hiding in Plain Sight​

Cyber Essentials Turns Patch Visibility Into Evidence​

Faster Remote Access Is a Morale Feature Disguised as a Technical Metric​

The Platform Story Is Really a Consolidation Story​

The Vendor Lock-In Concern Does Not Disappear​

Windows Admins Should Notice the Death of the Site-by-Site Patch Model​

Backup Became Easier to Sell Once It Stopped Being a Project​

The Technician Experience Is the Hidden Control Plane​

The MSP Market Is Rewarding Fewer Consoles and Better Proof​

Stability IT’s Migration Playbook Has a Few Hard Edges​

The Practical Wins Are Smaller Than the Marketing, Which Is Why They Matter​

References​

AI

The Real Migration Was Away From Tool Sprawl​

Stability IT Let Technicians Vote With Their Workflow​

VSA Became the Bridge Instead of the Anchor​

Patching Was the Pain Point That Made Consolidation Concrete​

Compliance Turns Visibility Into a Commercial Requirement​

Remote Access Is Where Platform Strategy Meets Human Patience​

The Security Story Is Also a Workflow Story​

The Margin Gain Explains Why Bundles Keep Winning​

Windows Admins Should Notice the Direction of Travel​

The Useful Lesson Is the Migration Pattern, Not the Vendor Logo​

The Numbers Tell a Coherent Story​

References​

AI

Stability IT Did Not Just Replace an RMM​

The Old Stack Was Functional Until It Became Friction​

VSA 9 Was the Bridge, Not the Destination​

The Migration Worked Because It Refused to Be Heroic​

Patching Became a Dashboard Problem Instead of a Server Problem​

Remote Access Is Where Technicians Decide Whether a Platform Is Real​

The Kaseya Portfolio Is the Strategy and the Trade-Off​

Backup Moved From Infrastructure Chore to Sellable Service​

Documentation Became Part of the Ticket Flow​

The Numbers Are Marketing, but the Operational Pattern Is Credible​

The Lesson for Windows Shops Is Hidden in the Cutover​

Stability IT’s Migration Playbook Has a Few Sharp Edges​

References​

Similar threads

VSA 9 Was the Bridge Away From a More Fragmented Past

Patching Was the Real Business Case Hiding in Plain Sight

Cyber Essentials Turns Patch Visibility Into Evidence

Faster Remote Access Is a Morale Feature Disguised as a Technical Metric

The Platform Story Is Really a Consolidation Story

The Vendor Lock-In Concern Does Not Disappear

Windows Admins Should Notice the Death of the Site-by-Site Patch Model

Backup Became Easier to Sell Once It Stopped Being a Project

The Technician Experience Is the Hidden Control Plane

The MSP Market Is Rewarding Fewer Consoles and Better Proof

Stability IT’s Migration Playbook Has a Few Hard Edges

The Practical Wins Are Smaller Than the Marketing, Which Is Why They Matter

References

The Real Migration Was Away From Tool Sprawl

Stability IT Let Technicians Vote With Their Workflow

VSA Became the Bridge Instead of the Anchor

Patching Was the Pain Point That Made Consolidation Concrete

Compliance Turns Visibility Into a Commercial Requirement

Remote Access Is Where Platform Strategy Meets Human Patience

The Security Story Is Also a Workflow Story

The Margin Gain Explains Why Bundles Keep Winning

Windows Admins Should Notice the Direction of Travel

The Useful Lesson Is the Migration Pattern, Not the Vendor Logo

The Numbers Tell a Coherent Story

References

Stability IT Did Not Just Replace an RMM

The Old Stack Was Functional Until It Became Friction

VSA 9 Was the Bridge, Not the Destination

The Migration Worked Because It Refused to Be Heroic

Patching Became a Dashboard Problem Instead of a Server Problem

Remote Access Is Where Technicians Decide Whether a Platform Is Real

The Kaseya Portfolio Is the Strategy and the Trade-Off

Backup Moved From Infrastructure Chore to Sellable Service

Documentation Became Part of the Ticket Flow

The Numbers Are Marketing, but the Operational Pattern Is Credible

The Lesson for Windows Shops Is Hidden in the Cutover

Stability IT’s Migration Playbook Has a Few Sharp Edges

References