Plenty has been written about what RouterOS 7 added. Much less has been written about what it moved, which is what bites you if you run a hotspot and rely on scripts, tutorials or tooling written for version 6.
These are the differences that actually cause work.
User Manager is no longer installed by default
This is the single most disruptive change for hotspot operators, and it produces a confusing failure.
On RouterOS 6, User Manager ships with the system. On RouterOS 7 it is a separate package you must download and install. Until you do, every command under that menu fails with no such command prefix — which reads like a syntax error rather than a missing package, and sends people hunting for typos.
Download the user-manager package matching your router’s architecture and RouterOS version, upload it, and reboot.
The menu moved
Where RouterOS 6 had /tool/user-manager, RouterOS 7 has /user-manager. Every script, API integration and tutorial written for version 6 needs this path changed.
The reorganisation goes further than the prefix:
- Version 6 kept limits under
/tool/user-manager/profile/limitation. Version 7 has a top-level/user-manager/limitation. - Version 7 introduces
/user-manager/user-profileto link a user to a profile. Version 6 has no equivalent menu — you call an action on the user instead.
Field names changed underneath
Less visible, and therefore more dangerous if you automate anything.
Creating a user in version 6 uses a username field, and supports a customer field for multi-tenant setups. In version 7 the field is name, and there is no customer concept in the same form.
Assigning a profile differs too. Version 6 uses an action — create-and-activate-profile — on the user. Version 7 adds a row to user-profile. Same intent, entirely different call.
Anything speaking to both generations has to branch on this, not merely rewrite paths.
VPN: OpenVPN gave way to WireGuard
RouterOS 7 added WireGuard, and for linking sites it is the obvious choice: dramatically simpler configuration, better performance, and far less to get wrong. RouterOS 6 has no WireGuard, so multi-site operators on version 6 remain on OpenVPN or IPsec.
If you are running remote sites and still on version 6, this alone is a strong reason to plan an upgrade.
Values come back normalised
A small thing that causes real bugs in automation. Write a rate limit of 5M and RouterOS stores and returns 5000000. Compare what you wrote against what you read back as plain strings and they will never match, so scripts that check “is this already configured?” conclude “no” forever and reapply the same change on every run.
Compare rates numerically, not textually.
Should you upgrade?
If you run a single site on version 6 and it works, there is no urgency. Version 6 remains supported and stable, and the upgrade will cost you an afternoon of adjusting to moved menus.
Upgrade when you have a reason: WireGuard for linking sites, hardware that only ships with version 7, or a feature you actually need. Do not upgrade a working hotspot the week before a busy period.
If you do upgrade: take a backup first, and remember to install the User Manager package afterwards, or your entire voucher system will appear to have vanished.
Supporting both
MikrotikAdmin detects which generation it is talking to on connect and uses the correct paths, field names and profile-assignment method for that version — including telling you plainly when the User Manager package is missing on version 7, rather than passing the raw API error through.