Lansweeper Classic in Maintenance Mode: What On-Prem Users Need to Know

A thread on r/Lansweeper has been doing the rounds this month, sharing a Lansweeper support response about the future of Lansweeper Classic (On-Prem). The reply lists ten features now in "maintenance mode" and has understandably unsettled some long-time on-prem customers. As a Lansweeper Solution Partner, we wanted to look past the headline and set out plainly what's actually changing, what isn't, and what it means for your ITSM roadmap.

---

TL;DR

• A Lansweeper support reply confirms that ten Lansweeper Classic modules - Helpdesk, Knowledgebase, Calendar, Deployment, Custom Actions, License Compliance, Location Assets, QR Codes, Software Authorization, and Local Admin Audit - are now in maintenance mode: they'll keep running, but won't see new features or routine bug fixes.

• The core Classic product (discovery, inventory, security scanning) is still actively developed - Lansweeper shipped Classic v12 as recently as July 2025.

• Lansweeper has stated there's no end-of-life date for On-Prem, and that running On-Prem and Cloud in parallel is a legitimate long-term option, not just a stopgap.

• This direction isn't new - Lansweeper confirmed the same maintenance-mode status for Helpdesk specifically back in October 2024.

• If your team relies on the affected modules, especially Helpdesk, now's a good time to plan how asset data feeds into a dedicated ITSM tool rather than waiting for a forced migration.

---

What Lansweeper support actually said

The response quoted in the Reddit post is fairly direct: Lansweeper Classic "still works and is still supported," and the team will "continue to keep it running and make sure the main parts of the product work as expected." But it goes on to name ten features that are "no longer being actively worked on or improved" and are now in maintenance mode - meaning Lansweeper will look into a completely broken feature, but isn't committing to regular updates, improvements, or general bug fixes for them:

Helpdesk, Knowledgebase, Calendar, Deployment, Custom Actions, License Compliance, Location Assets, QR Codes, Software Authorization, and Local Admin Audit.

That's a wider list than we'd seen called out in one place before, which is presumably why it struck a nerve. But it's consistent with Lansweeper's own public messaging, not a surprise reversal.

What's actually changing - and what isn't

It's worth separating the core product from the auxiliary modules, because the support reply is really only about the latter.

The core of Lansweeper Classic - network discovery, asset inventory, and security visibility - is still getting real investment. Lansweeper Classic (On-Prem) v12, released in July 2025, added a .NET 8 platform upgrade, passive discovery via CDP/LLDP, per-asset firewall visibility, and a new Auto-Update Engine. That's not the profile of a product being quietly wound down.

On the broader roadmap question, Lansweeper has been explicit that there's no forced end-of-life for On-Prem. In an Expert Q&A on Lansweeper On-Prem and Cloud, a Lansweeper VP of Product Management put it simply: "…you don't have to choose. You CAN use both in parallel." Lansweeper's own support portal article on Lansweeper and Lansweeper Classic sets out the same coexistence model.

What is changing is the set of features Lansweeper is willing to keep building outward from that core. Helpdesk, Deployment, Custom Actions, and the rest are being left as-is, and Lansweeper's own recommendation for that gap is to connect Lansweeper to a dedicated ITSM platform instead.

Why this isn't really new

If this feels familiar, it's because it is. Back in October 2024, Lansweeper support confirmed in a community thread that the on-prem Helpdesk specifically was in maintenance mode, would keep working, but wouldn't be ported to Lansweeper Sites (Cloud) - and recommended integrating with ServiceNow, Jira Service Management, HaloITSM, or ManageEngine ServiceDesk Plus instead. The Reddit post just restates that direction with a longer list of affected modules. Lansweeper has been telegraphing this for around two years; nothing here suggests a sudden change of plan.

 

What this means for your ITSM roadmap

If your team is using any of the affected modules day-to-day - Helpdesk and Deployment are the two we hear about most - it's worth treating this as a planning prompt rather than an emergency. A few practical options:

Stay on Lansweeper Classic for discovery and inventory, and pair it with a proper ITSM platform for ticketing, knowledge management, and deployment workflows. This is exactly the integration pattern Lansweeper itself now recommends, and it's the approach we typically help customers set up with HaloITSM or Jira Service Management.

Run On-Prem and Cloud in parallel (hybrid mode) if you want Lansweeper Sites' newer capabilities without giving up your existing on-prem discovery investment.

Audit which of the ten modules you actually depend on before deciding anything. Several - QR Codes, Location Assets, Software Authorization - are used by a minority of customers; others, like Helpdesk, are core to daily operations for many teams and deserve a proper migration plan rather than a reactive one.

How BDQ can help

We work with Lansweeper customers on exactly this kind of transition: cleaning up and structuring asset data, then feeding it into a dedicated service desk so nothing depends on a module Lansweeper isn't actively developing. If you'd like a second opinion on what maintenance mode means for your specific setup, our Lansweeper partner services page has more on how we help, or you can look at our implementation and migration services directly.