As per the notice referenced above, the cnMaestro Cloud may not support Enterprise devices post the end of October, 2026. The recommendation is to migrate your cnMaestro Cloud account to cnMaestro On-premises so that you can continue managing your network. This document provides guidance on doing that.
If the October end timeline is giving enough headroom for your operations, you may wait some more time before initiating the migration.
Create a Cloud Anchor account, deploy 6.0 cnMaestro on-premises instance(s) and migrate your Wi-Fi APs and Switches to those instance(s).
Starting 17 Sep 2026, all new anchor accounts will include a 90-day cnMaestro X trial license. This will allow the on-premises instance to operate in the X feature mode.
Deploy cnMaestro on-premises 6.0 instances based on your scale and management needs. The images and user guide can be found here: https://support.cambiumnetworks.com/files/cnmaestro/. Note: If installing multiple on-premises intances, please do not clone VMs; create each one from scratch. Cloned VMs use the same synthetic serial number and will overwrite each other in the Anchor, preventing license sharing. Avoid moving on-premises instances from one Anchor account to another to limit mistakes.
Migrate devices from your Cloud account(s) to the on-premises instance(s).
You can use the export/import of group configuration feature to copy configuration. Export and Import options are available under Configuration → Wi-Fi Profiles and Switch Profiles.If you have cnMaestro X, you can potentially use APIs to export and import configuration with custom scripts. Note: The Cloud 6.3 version has additional Port Configuration for switch. This is not yet supported on the 6.0 on-premises. This must be handled manually - before migration, view device config and save it per switch. After migration, view the device config again and add the missing lines as port config changes for each of the switches.
If you have device overrides, note them from Device → Configuration → Device Configuration page for each device. If you have cnMaestro X, you can use Bulk Export/Import feature for Wi-Fi APs. For this, go to Site → Devices → Configuration → Bulk Config → Device Overrides → Export/Import.
It is also a good idea to export serial numbers (inventory) and subscriptions from your cloud account for future reference.
Do this in batches, preferably one device group at a time.
From the cloud, delete the devices in the group.
Devices in the group will connect to the on-premises server and will appear in its onboarding queue. Approve all the devices from the onboarding queue. Wait a few minutes for all the devices to acquire subscription slots (even for Essentials) and complete onboarding.
What happens when the cnMaestro X trial expires?
The on-premises instances will degrade to Essentials. We expect that if the Enterprise business is acquired by an entity, they will help you with an appropriate extension or replacement of trial and will guide you with the process.
What happens if Anchor is discontinued or disconnected?
cnMaestro on-premises will continue to work, but you will not be able to add or delete any devices.
Before the Cloud Anchor shuts down, we plan to release an on-premises image for Wi-Fi and Switches only, without any dependency on the Cloud Anchor. This image will also provide all supported on-premises X features with no need for licenses. You will be able to upgrade the 6.0 version to this unrestricted build.
What features are not available with the on-premises cnMaestro?
For Enterprise customers, the most important features that you will miss from cnMaestro Cloud are:
> Network Assurance (X)
> Some EasyPass features like Google/Azure/Social logins/UPSK (X)
> MarketApps (X)
> AFC for Wi-Fi 6E/7 APs
> Support for NSE, RV22
Refer the cnMaestro On-premises user guide section “cnMaestro features” for an exhaustive table.
I have a mix of Essentials and X cloud accounts. Should I create separate on-premises instances for them?
It is recommended to keep an exact replica of the Cloud accounts to on-premises servers, however you can choose to consolidate or split them. At this point, the Anchor account provides you with unlimited trial X license, so all instances can use X. As mentioned above, do not clone VMs, always create them fresh.
I have a mix of Fixed Wireless and Enterprise devices in the same cloud accounts. How should I manage the migration?
At this point, it is recommended to migrate only Enterprise devices to an on-premise server. If you want to migrate Fixed Wireless devices also, you can, but migrate them to a separate on-premises server.
I am already on on-premises. How does this impact me?
At this point, you don’t have to take any action. In future, depending on the product lines that are acquired, you may have to split products with no buyer or different buyers to a separate instance.
What about Fixed Wireless products?
Review the Airspan announcement (reference link above has details) - maintaining Airspan products together in your Cloud account or on-premises instance is recommended. We will provide guidance in a short while for other Fixed Wireless Products like ePMP.
What is the new 6.0.0-r11 On-premises cnMaestro build about?
This build has some bug fixes related to onboarding of devices through Cloud Anchor account. This is not the unrestricted build mentioned in FAQ-2. You can upgrade from the previous r5 build to this build throgh the UI. See release notes here: https://support.cambiumnetworks.com/files/cnmaestro/
History
24-Sep-2026: Updated with Oct end date; minor updates; more additions to FAQ
18-Sep-2026: Updated migration steps; clarified some details; added more to FAQ
What about the security appliances, NSE - that Cambium poured so much time into.. are we dead, jim?
What happens post October 1st when cloud-anchor connectivity dies. If we do NOT migrate and establish on-prem relationship before then – are those devices locked out?
How do we account for the customers where we dont have remote access to devices? in order to move them to our on-prem?
I am assuming what you mean by “cannot add or claim devices” is by means of the Serial Number and the on-boarding from cloud inventory… IE: the Cambium cloud managed device serial list.???
I assume we can do this MANUALLY via remote CLI onto the devices and configure the management cambium url https://FQDN.com
management cambium-id ANCHOR-SITE KEYHERE
no cambium-remote validate-server-cert
For those looking to move to cnMaestro On-Premises; If you don’t know how to migrate to on-premises and/or if you would like to avoid the cost of a server to install it, I’m here to help!
My team and I are experts migrating cnMaestro instances to managed virtual servers, it keeps things in the cloud with full data center security & support, VPNs, firewalls, backups, redundancy and more, without the upfront infrastructure costs. We are also offering general consulting to ensure a smooth migration.
If anyone is stuck or needs a hand figuring out their next steps, feel free to reach out via DM!
Is there any way to transfer existing (paid) X licenses from a cloud account to a new “Anchor”?
If we have a combination of X devices and non-X devices, do I need to run two on-prem instances, one for the licensed devices and one for the unlicensed?
Is it possible to setup a totally “cloudless” on-prem server, or does on-prem always require an Anchor instance to function?
What am I supposed to do with the ~170 devices we have that rely on MarketApps?
Thank you for the guidance; it is good to know that some members of the cnMaestro team are still around. It would be of great help if, should cnMaestro Cloud be discontinued or disconnected, there is already an independent version of cnMaestro On-Prem available. And if the Enterprise business is not acquired, the software should include all cnMaestro X features by default, as it would be a waste if these were lost forever. There are a lot of partners, companies, and users that rely on cnMaestro.
The best option (and in my opinion, the only option) would be to make cnMaestro (X) available as open source if the Enterprise business is not acquired.
The cnMaestro team that is still there could really help a lot of Cambium partners in these worrying times for everyone.
Generally you can’t sue something that’s being reorg’d. Or I guess you can try, but you’re not going to get anything from it…
I’m trying to understand how licensing works when using on-prem. We currently use two cloud instances, one for “X” devices and one for non-X/essentials/unlicensed.
Obviously if the cloud dies the licensing won’t matter, and per the post above everything will be X for 90 days if it’s migrated. But let’s assume something good happens and someone steps in to continue the licensing and help migrate paid X licenses to their Anchor, and keep running the Anchor part for longer (which should be much lower cloud spending if they can get all of the device check-ins and stats offboarded to “on-prem” instances).
In this future scenario, do I need to have two separate on-prem instances, one for X-licensed devices and one for Essentials (everything else)? Or can I commingle the two licensing types on a single on-prem controller?
Based on the guidance so far, I think it would be in your best interest to migrate your stuff to an “onprem” instance (even if that actually means you’re running it in someone else’s cloud yourself). I would guess that the more customers migrate to their own instances, the longer they can keep at least the basic “anchor” instances running, allowing what’s left of the company (as well as all of us customers) more time to figure out what to do next.
I have to assume that the ongoing cost of running the cloud instances is not small when hundreds/thousands of devices are sending stats and check-ins to them. By comparison, I would expect an “Anchor” instance to be pretty low-resources if it’s only really used to validate licensing & ownership during onboard or offboard of a device…
What happens if Anchor is discontinued or disconnected?
cnMaestro on-premises will continue to work, but you will not be able to add or delete any devices.
If the Enterprise business is acquired by an entity, they will guide you at that time.
If not, we plan to release an on-premises image for Wi-Fi and Switches only, without any dependency on the Cloud Anchor or licenses.
So, it at least sounds like they will remove the cloud dependency for the on prem version if no one else takes over cnMaestro cloud.
So is NSE dead, or this product being possibly being picked up by another manufacture?? I know I’m not alone, and a minority as far as loss - but we’re thousands ourselves for NSE.
Given the statement says on-prem cnMaestro might have a final released version that only supports WiFi and switching…
Starting 17 Sep 2026, all new anchor accounts will include a 90-day cnMaestro X trial license. This will allow the on-premises instance to operate in the X feature mode.