If you typed "UNMS" into a search engine and landed here, you already know the short version: UNMS (Ubiquiti Network Management System) no longer exists as a product. In late 2020, Ubiquiti rebranded and rebuilt it as UISP (Ubiquiti ISP Platform), and every UNMS installation has long since been funneled into the UISP ecosystem.
This article covers what actually changed in the transition, what UISP does well today, where operators tend to hit its ceiling, and what your options look like when that happens.
From UNMS to UISP: a quick history
UNMS launched as Ubiquiti's free network management system for internet service providers - a way to monitor airMAX, EdgeMAX, and other Ubiquiti gear from a single dashboard. It was genuinely useful and, importantly, free.
Around version 1.0, Ubiquiti announced the rebrand to UISP. This was more than a name change:
- The scope grew. UISP positioned itself as a platform for running a whole WISP: device management, topology maps, outage detection, plus a CRM module with subscriber records, service plans, invoicing, and a client portal.
- The hardware line grew with it. Ubiquiti started shipping UISP-branded routers, switches, and power products designed to be managed from the platform.
- Hosting split in two. You can self-host UISP (Linux, Docker-based) or use Ubiquiti's hosted option, with the console tying into the broader Ubiquiti account system.
If you are still running an old UNMS instance, you are several major versions behind, and the upgrade path leads through UISP whether you like it or not.
What UISP genuinely does well
Credit where it is due. For the network side of a Ubiquiti-based WISP, UISP is hard to argue with at its price of free:
- Device monitoring and alerting for Ubiquiti radios, routers, and switches, with firmware management from one screen.
- Topology visualization that understands airMAX access points and stations, so you can see a tower's client list without touching a spreadsheet.
- Outage detection that tells you a sector went down before the phone starts ringing.
If your access network is Ubiquiti end to end and your main problem is "I want to see all my radios in one place," UISP solves that problem well.
Where operators hit the ceiling
The friction almost never comes from the network features. It comes from running the business on the CRM module. Patterns we hear from operators who migrate:
Billing depth. UISP CRM handles basic recurring invoices, but ISP billing rarely stays basic. Proration on mid-cycle plan changes, late fees with grace periods, taxes that differ by jurisdiction, multiple payment gateways, prepaid periods, seasonal suspensions for RV parks and vacation markets - each of these is either partial or missing, and each one you work around ends up as a spreadsheet next to the system instead of inside it.
Hardware lock-in by design. UISP is built around Ubiquiti equipment. That is not a criticism - it is the point of the product. But most real networks are mixed: MikroTik routers at the core, Ubiquiti or Cambium radios in the access layer, maybe a fiber segment with its own OLT. When your management platform only understands one vendor deeply, the rest of the network lives outside it.
Support workflows. A lightweight ticket feature is fine at 50 subscribers. At 500, you want email-to-ticket conversion, assignment rules, an audit trail tied to the client record, and a way for a technician in the field to see the whole history on their phone.
Provisioning tied to billing. The step that separates ISP platforms from network tools: when an invoice goes unpaid, the service should suspend itself - RADIUS, PPPoE, queue change, whatever your enforcement is - and restore itself on payment. Doing this reliably across a mixed-vendor network is exactly the gap between a monitoring system with a CRM attached and a billing engine with provisioning built in.
Your options in 2026
Option 1: stay all-in on UISP. If you are a smaller, Ubiquiti-only operation with simple monthly billing, UISP remains a reasonable answer, especially at its price.
Option 2: keep UISP for the network, move the business. This is the most common path we see. UISP keeps doing what it is best at - watching radios - while subscribers, services, invoices, payments, and tickets move to a dedicated ISP platform. The two do not fight each other; they simply own different layers.
Option 3: replace the stack entirely. Operators consolidating on MikroTik or multi-vendor RADIUS often drop UISP at the same time and run monitoring, provisioning, and billing from one system.
Migrating without the spreadsheet purgatory
The reason operators put this decision off is never the destination - it is the move. Re-typing 400 subscribers with their plans, balances, and payment methods is nobody's idea of a weekend.
This is why ISPbox imports a UISP backup directly. You upload the backup file, the importer runs a dry-run preview - showing exactly which subscribers, service plans, invoices, and even saved Stripe payment methods will be created - and nothing goes live until the numbers match what you expect. If something looks wrong, you roll back and adjust instead of cleaning up a half-imported database.
From there, billing, ticketing, the customer portal, and provisioning that follows the invoice are part of the platform rather than add-ons - see the full ISPbox vs UISP comparison or the migration playbook. And if part of your decision is comparing the wider market, our guide to the best ISP billing software puts UISP CRM side by side with the paid platforms.
FAQ
Is UNMS still available? No. UNMS was rebranded and rebuilt as UISP in late 2020. Old UNMS installations must upgrade through the UISP path, and the UNMS name is no longer used by Ubiquiti.
Is UISP free? The UISP software itself is free to self-host, and Ubiquiti offers hosted options. The costs that matter are operational: the CRM's billing limits and single-vendor focus, which many growing ISPs eventually pay for in workarounds.
Can I use UISP for network monitoring and something else for billing? Yes, and it is a common setup: UISP watches Ubiquiti devices while a dedicated ISP platform like ISPbox owns subscribers, invoices, payments, and support tickets.
How do I migrate my subscriber data out of UISP? ISPbox imports a UISP backup file directly, including subscribers, services, billing history, and saved Stripe payment methods, with a dry-run preview and rollback before anything goes live.
