ScreenConnect to MeshCentral: The MSP Migration Guide

ConnectWise raised ScreenConnect pricing by as much as 275% on some tiers in 2025, and MSPs did the math. When a remote access tool that used to be a rounding error becomes a line item you have to defend, the question stops being "which features do we like" and turns into "what else is out there." MeshCentral keeps coming up in those conversations: open source, self-hosted, Apache 2.0, free to run. This guide covers why the migration is happening, what MeshCentral does and does not replace, and the exact steps to move without leaving a client stranded mid-session.

TL;DR: Moving From ScreenConnect to MeshCentral

• The short answer. Move if you want to kill per-technician remote-access fees and own your stack, because MeshCentral gives you browser-based remote desktop, terminal, and file transfer for the price of a small VPS.
• The catch. MeshCentral is remote access, not an RMM, so patching, alerting, and ticketing stay your problem.
• The setup. Stand up MeshCentral on Docker, npm, or Windows, deploy the agent in parallel, then retire ScreenConnect once you have parity.
• The upgrade path. Need real RMM around it? Tactical RMM bundles MeshCentral and adds the missing layer.

Why MSPs Are Leaving ScreenConnect in 2026

ScreenConnect, formerly ConnectWise Control, is a genuinely capable remote support tool. Fast sessions, solid unattended access, a mature feature set built over more than a decade. Our own ConnectWise ScreenConnect review does not pretend otherwise. The problem was never the software. It's the bill, the licensing model, and a security record that got too expensive to shrug off.

For years ScreenConnect was the default remote-access layer in thousands of MSP stacks precisely because it was cheap and reliable. That combination is what changed. When the price of a tool triples while the tool itself stays roughly the same, loyalty gets tested. The r/msp threads that used to defend ScreenConnect started filling with migration questions instead.

The Price Hike, In Numbers

In 2025 ConnectWise restructured ScreenConnect pricing. Entry plans rose around 20%. The larger unattended-access tiers, the ones priced by how many computers you manage, absorbed the real damage, with increases reported as high as 275% on some accounts. The jump was steepest exactly where growing MSPs live: the more endpoints you had under management, the harder the new pricing hit.

Here is roughly where the published plans sit now, on annual billing:

The sticker price is only half the story. ScreenConnect licenses per concurrent technician or session, which sounds tidy until you staff up. A three-technician shop on Standard is at $1,620 a year before a single increase lands. Add a fourth tech and a Premium upgrade for the auditing your compliance clients want, and you are past $2,600. Renewal quotes tend to climb year over year, so the three-year total runs well ahead of the first-year number you signed for. In one analysis of ScreenConnect reviews, licensing complexity was the single most common complaint, cited in roughly half of the negative feedback.

Now put MeshCentral next to that. A self-hosted server on a $10-a-month VPS covers hundreds of agents. The software costs nothing. The three-year math is a few hundred dollars in hosting against several thousand in per-seat fees that keep rising. That gap is the whole reason this article exists.

The deeper issue is the model, not the number. A per-technician license means every hire raises your remote-access bill before that tech has closed a single ticket. Growth gets taxed. Self-hosting flips that: your cost is tied to a server you control, not to headcount a vendor gets to price. For a shop planning to add clients and staff, that difference compounds every year.

The Security Record You Inherit

Price is the trigger. Security is the accelerant. In February 2024, security firm Huntress documented SlashAndGrab, a pair of ScreenConnect vulnerabilities tracked as CVE-2024-1709 and CVE-2024-1708. The first was an authentication bypass scored CVSS 10.0, the maximum a vulnerability can carry. It let an attacker reach the setup wizard by adding a trailing slash to a URL, then create a brand new administrator account on an exposed server. Ransomware crews were weaponizing it in the wild within days of disclosure.

ConnectWise shipped a patch in version 23.9.8, and cloud-hosted instances were fixed quickly. On-prem shops that were slow to update wore the consequences, some of them badly. The lesson many MSPs took from it was not "ScreenConnect is uniquely unsafe." It was "a widely deployed, internet-facing remote-access tool is a giant target, and we should think harder about what we run and how it's exposed."

That thought cuts toward MeshCentral in an interesting way. When you self-host, patching and exposure become your job instead of a vendor's. You own the risk. You also own the timeline, the attack surface, and the decision about what faces the public internet at all. For a team with the discipline to lock a server down, that control is a feature, not a burden.

What MeshCentral Is, and What It Is Not

MeshCentral is an open-source, web-based remote management platform. It was created by Ylian Saint-Hilaire, whose work on it began at Intel, and it's still actively maintained on GitHub under the Apache 2.0 license. That license matters. It's genuine, OSI-approved open source, not the source-available model that some tools market as open. You can read the code, fork it, run it, and never send a dollar or a telemetry ping to a vendor.

From a single browser console you get remote desktop, terminal, file transfer, and session recording, with no technician-side client app to install. A tech logs into the web interface and connects. The server footprint is light: a 1 to 2 GB RAM VPS comfortably handles hundreds of agents, and the MeshAgent that runs on managed machines is small and quiet. You can install the server three ways depending on your comfort zone: npm for a fast Node.js setup, Docker for a container you can move anywhere, or as a native Windows service.

There is real depth under the hood. MeshCentral does multi-tenant device groups, granular per-user permissions, relay routing so you can reach machines behind NAT without port forwarding on every client, and Intel AMT integration for out-of-band management on hardware that supports it. For pure remote support and unattended access, it holds its own against tools that cost thousands a year.

Here is the part the listicles skip. MeshCentral is remote access. It is not an RMM. There's no built-in patch-automation engine, no alerting engine, no PSA, no ticketing, no billing, no fleet-wide scripting scheduler. Point it at those jobs expecting a full commercial RMM and you'll feel the gaps fast. Scope it as what it is, a remote-access layer you fully control, and it's hard to beat on price or privacy.

ScreenConnect vs MeshCentral: How They Compare

On core remote access the two are closer than the price gap suggests. Where they diverge is cost, hosting model, and who picks up the phone when something breaks.

The pattern is clear. On the day-to-day work of connecting to a client machine, they trade blows. On cost, they do not. What ScreenConnect gives you that MeshCentral cannot is a support contract and a company to hold accountable when a session fails at 2 a.m. For some MSPs that safety net is worth the premium. At 2025 prices, a growing number decided it wasn't.

The ScreenConnect to MeshCentral Migration, Step by Step

Migrations go sideways when you rip out the old tool before the new one has parity. So don't. Run them in parallel and cut over only when your team trusts the replacement. Here is the sequence MSPs use to move without a single dropped client session.

1. Inventory your ScreenConnect estate. Export the device list and separate unattended agents from one-off support sessions. That unattended count is your target for MeshCentral, and the export is your rollback insurance.
2. Stand up the MeshCentral server. Spin up a small VPS, 1 to 2 GB RAM to start, install through Docker or npm, and point a dedicated subdomain at it. Put it behind a valid TLS certificate before anything connects. This is not optional.
3. Lock the server down. Turn on two-factor auth for every operator account, restrict the admin interface, and decide precisely what, if anything, is exposed to the public internet. This is the step that prevents your own CVE-2024-1709 moment.
4. Rebuild your device groups and permissions. Recreate your ScreenConnect organization structure as MeshCentral device groups, so each tech sees only the clients they support. Get this right before you deploy agents and you avoid a permissions cleanup later.
5. Deploy MeshAgent in parallel. Push the agent through your existing RMM, a GPO, or a login script, alongside ScreenConnect rather than instead of it. Confirm every machine checks into the console.
6. Run both tools for a week. Handle real tickets in MeshCentral while ScreenConnect stays as the fallback. You want to find the rough edges on live sessions during overlap, not on cutover day with no safety net.
7. Retire ScreenConnect. Once MeshCentral has full parity and your techs reach for it by habit, uninstall the ScreenConnect agents and cancel the renewal. Keep the archived export in case a client machine surfaces later.

For most small shops the whole thing is a weekend of server setup and a week of overlap. The build is the real cost, and it happens once. The savings recur every month for as long as you run it.

Where MeshCentral Falls Short, and How to Fill the Gap

The limitation worth planning around is simple: MeshCentral does one job. If your team also needs patch automation, monitoring, alerting, and scripting across a fleet, a remote-access tool alone will not cover you. That's not a knock on the project. It's scope, and pretending otherwise is how MSPs get burned three months into a migration.

Two paths close the gap without sending you back to a per-seat contract. The first is Tactical RMM, which uses MeshCentral as its remote-access engine and layers patch management, scripting, and alerting on top. If you like MeshCentral but need a real RMM wrapped around it, that's the natural next step and it keeps you in open-source territory. If you're weighing a full RMM either way, our rundown of the best RMM tools for MSPs compares the commercial and open-source options side by side.

The second path is a managed all-in-one platform, for MSPs that want MeshCentral-grade remote access without owning a server at all. OpenFrame is an AI-native all-in-one MSP platform with native PSA included, priced to undercut the legacy stacks, and built with no multi-year lock-in. You get the consolidation and the AI handling routine tickets without the self-hosting burden. It's a different trade than pure open source, less to maintain in exchange for less low-level control, and worth knowing exists when you scope the move.

Other ScreenConnect Alternatives Worth a Look

MeshCentral is not the only exit. How much you want to self-host, and how much RMM you need bolted on, decides which of these fits. For the wider ConnectWise stack rather than remote access alone, our ConnectWise alternatives guide goes deeper on each.

RustDesk is the closest open-source cousin for TeamViewer-style use, though its defaults need hardening and the paid server tier adds up once you want the web console and LDAP. Splashtop is the low-friction commercial swap when self-hosting is a non-starter, and its per-tech pricing usually undercuts TeamViewer. TeamViewer stays polished and pricey. Atera and NinjaOne make more sense when you're replacing the entire stack, not swapping one tool, since remote access comes bundled with the RMM you were going to buy anyway.

Who Should Move, and Who Should Wait

The call comes down to two questions. Do you have someone who will own a Linux server, and how much RMM do you need bolted to your remote access?

Move to MeshCentral if you have in-house comfort with self-hosting, you want per-seat remote-access fees gone for good, and you're fine sourcing support from documentation and a GitHub tracker. A three-technician shop can erase four figures a year and take direct control of its own uptime and attack surface. For technical MSPs that already run a Linux box or two, the maintenance load is small and the payback is immediate.

Wait, or pick a managed option, if nobody on your team wants to babysit a server, your clients demand a vendor SLA on the tool itself, or you're mid-contract with no room to run a parallel migration properly. There's no prize for self-hosting something you won't maintain, and a half-secured remote-access server is worse than the bill you were trying to cut.

The price hike made the question urgent. The answer was already sitting in the open-source community, running quietly under a large share of the RMM stacks in the business. ScreenConnect's bill went up. Your remote access doesn't have to.