User Manager or an External RADIUS Server? When to Stay, When to Move
Most small ISPs start with User Manager — the subscriber system built into RouterOS. That is a sound decision early on: it's free, it ships with the device, and it has you running in half an hour.
The question isn't "which is better". It's when the thing that works for you today becomes the thing holding you back.
What User Manager genuinely does well
Let's be fair, because half the articles on this topic undersell it in order to sell you something else:
- No second server to buy or maintain. That isn't a detail — it's the lowest possible operating cost.
- No network between you and it. It runs on the same device, so there is no timeout, no blocked port, no mismatched shared secret.
- It generates and prints cards without external tooling.
- If the router is up, the system is up. No second point of failure.
If you have one router, under a hundred subscribers, and you manage everything from one place — stay put. Migrating in that situation adds complexity without solving a problem.
Where it stops
1. A second router means a second system
This is the big practical one. User Manager lives inside one router, and the subscribers registered there mean nothing to any other device.
So the first time you open a branch or add a router elsewhere, your options are: duplicate subscribers by hand across both (and inherit the conflicts), or split your network into two separate islands. Both hurt more with every device you add.
An external RADIUS server inverts this: routers become access points to one system, and a subscriber connects through any of them with the same account.
2. The data lives on the device
The User Manager database sits on the router's own storage — on most models, limited internal flash. Which means:
- If the device dies, the data goes with it, unless your backup is recent
- Backups are entirely your responsibility, and nobody remembers them until after the first disaster
- Historical usage accumulates on storage never designed to be an archive
3. Upgrades
Moving from RouterOS 6 to 7 brought an entirely new version of User Manager. Not an update — a rewrite, with different concepts and a migration path that has conditions. Anyone who has crossed that gap with live subscribers knows it isn't "click Upgrade and carry on".
The practical consequence: upgrading the router's OS becomes a business decision, not a maintenance one.
4. Reporting hits a ceiling
You get usage and sessions. You don't get: which subscribers are about to churn, this month's revenue against last, which plan is actually profitable, or a warning before a quota runs out.
That isn't a flaw. It's built as a router tool, not a business system.
5. No separation between who manages what
Access to User Manager is access to the router's interface. So a staff member who renews subscriptions needs access to a device where they could also change firewall and routing rules. That kind of permission split barely exists here.
Signals that it's time
Not theory — concrete symptoms:
- You have more than one router and you're repeating manual work across them
- You're afraid to upgrade because you aren't sure the subscribers will survive it
- You calculate revenue in a spreadsheet, because the system won't tell you
- A staff member has router access and you aren't comfortable with it
- A customer says "the internet is down" and you can't tell whether that's an exhausted quota or something else without opening the device
Two or more means the real cost has moved into your time, not into a server subscription.
What you gain
- One system across every router — one subscriber, one account, from any access point
- Data off the device — a router can die and be replaced without losing anything
- Instant disconnect and reactivation via CoA, without opening the device
- Network-wide reporting instead of device-by-device
- Separated permissions — the person doing renewals never sees the firewall
And what it costs
Be honest about both sides:
- A new point of failure. Server down means no authentication. (The usual answer: a local
fallbackon the router, or a grace period — configuration that must be in place from day one, not after the first outage.) - The network is now part of the equation. A short timeout or a blocked port becomes a plausible cause of login failures.
- A recurring cost — a server you run, or a managed service.
- A migration day that needs planning. It is not "export, import, done".
The decision in one line
One router, small and stable → stay. Don't migrate for its own sake.
More than one router, data you're nervous about, or you need to see your numbers → move. And it gets harder the longer you wait, because the volume of data to carry across only grows.
If you do decide to move, the next step is connecting the router to a RADIUS server — and, more importantly, planning the migration itself so nobody gets cut off.
Read next
- Connecting MikroTik to a RADIUS Server — A Complete Walkthrough
A practical guide to linking a MikroTik router to RADIUS: PPPoE and hotspot setup, enabling CoA for instant disconnects, and the mistakes that trip most people up.
- Migrating Subscribers From an Old System Without Losing Anyone
A practical guide to moving your subscribers between systems: what to export, the traps that corrupt data silently, and how to run cutover day without downtime.