Guidance for cnMaestro Enterprise Customers - (updated) 5 Nov 2026

Products cnMaestro
1

Guidance for cnMaestro Enterprise Customers

Updated: 05-Nov-2026

References:

Summary

As per the announcement and FAQ referenced above, the cnMaestro Cloud is operational and continues to support Enterprise devices post the end of October, 2026.

As per the previous guidance, if you already migrated your Cloud accounts to On-premises and you now want to bring them back to the Cloud, you can follow instructions in the section “Migrating back to Cloud”.

Migrating back to Cloud

You can migrate the management of your devices back to your original Cloud account with some limitations:

  • Device data (statistics, events, alarms etc.) cannot be migrated back to Cloud. When the device was deleted while moving to on-premises, the cloud data history was also deleted. Once claimed back into Cloud account, data collection will start afresh with no history.
  • Any configuration changes that were made in the On-premises managed window must be manually copied back to the Cloud account
  • If you added new devices utilizing the free X trial available, you will need matching subscriptions if you have an X Cloud account to accommodate those new devices

Preparation

  • Confirm that your on-premises instance is online and connected to its Cloud Anchor account. This connection is required to ensure that devices are released from the on-premises so that they can be claimed in the Cloud account.
  • Export the device inventory for ensuring that all devices migrated. It is a good practice to backup this information.
  • Export any configuration changes made while the devices were managed on-premises including device settings and templates.
  • If needed, export reports, events, alarms etc. you need for audits or just for reference.

Steps - moving back to Cloud

  1. Do this in batches, preferably one device group at a time.

  2. On the Cloud account, remove device overrides that were used to point the device to on-premises instance during the previous migration. This is to prevent devices coming back to Cloud from going back to on-premises again.

  3. On the On-premises instance, remove device overrides that were used to point the device to on-premises instance. This is to clear this configuration from devices.

  4. Build a list of serial numbers by exporting device inventory for the group.

  5. Reboot the devices in the group

  6. Delete the devices from on-premises, while connected to the Anchor account.

  7. Claim the devices in the Cloud account, under the group/site. This will succeed only if the deletion from on-premises in the previous step completes without error.

  8. Devices will connect to Cloud and get adopted into the right Site/group

  9. Once devices become online, verify their configuration and add any missing changes that were added while those were managed by on-premises.

Previous guidance - prior to Univastu acquisition

This section is maintained for historical reference only

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).

Steps

  1. Create an Anchor account following instructions here: https://docs.cloud.cambiumnetworks.com/help/6.3.0/index.htm#UG_files/Anchor.htm.
    Note: Copy the Onboarding key and Cambium ID for future reference. These are inputs you provide when creating the new Anchor account.

  2. :red_exclamation_mark: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.

  3. 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.

  4. Onboard the deployed instances to the anchor account. You will need the Cambium ID and Onboarding Key saved above in this step. Instructions: https://docs.cloud.cambiumnetworks.com/help/6.3.0/index.htm#UG_files/Anchor.htm

  5. Migrate devices from your Cloud account(s) to the on-premises instance(s).

    1. 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.

    2. 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.

    3. It is also a good idea to export serial numbers (inventory) and subscriptions from your cloud account for future reference.

    4. Follow this community article to configure the devices to connect to the on-premises server: https://community.cambiumnetworks.com/t/migrating-cnpilot-e-series-access-points-from-cnmaestro-cloud-to-on-premises/63164. The article is dated, but it will work for all Wi-Fi APs and Switches. Note that the CLI syntax for each product could be different.

    5. Do this in batches, preferably one device group at a time.

    6. From the cloud, delete the devices in the group.

    7. 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.

    8. Continue until all devices are migrated.

    9. If you have access to the site’s DHCP server, configure DHCP options for devices that may get factory reset in the future to discover the on-premises instance. Follow this guide: https://community.cambiumnetworks.com/t/cnmaestro-on-premises-device-onboarding-and-dhcp-options-configuration-in-linux-or-windows/45792.
      Note: ensure that the devices have a trusted network path to connect to your on-premises instances (avoid public networks).

FAQs

  1. What happens when the cnMaestro X trial expires?
    The on-premises instances will degrade to Essentials.

    Refer the reference FAQ which states “If your on-premises controller is running a 90-day cnMaestro X trial, please open a support ticket and Cambium will issue a 90-day trial renewal for now. Cambium expects to charge for cnMaestro X on-premises at a later date, and details will be announced.”

  2. 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.

  3. 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.

  4. 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.

  5. I have a mix of Airspan Fixed Wireless and ePMP+Enterprise devices in the same cloud accounts. How should I manage the migration?
    If you want to migrate to on-premises, it is recommended to migrate Airspan devices to a separate server and remaining to a separate on-premise server. Note that Cambium and Airspan are working to split the Cloud based on product ownership.

  6. I am already on on-premises. How does this impact me?
    At this point, you don’t have to take any action. In future, you may have to split products with different buyers to a separate instance.

  7. What about Airspan Fixed Wireless products?
    Maintaining Airspan products together in your Cloud account or on-premises instance is recommended. Note that Cambium and Airspan are working to split the Cloud based on product ownership.

  8. What about NSE?
    NSE is not supported on cnMaestro On-premises and it continues to be suported by the Cloud.
    For other options, review this community page: https://community.cambiumnetworks.com/t/beta-nse-release-2-5-b2-now-available/108960

  9. 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

05-Nov-2026: Updated to reflect post acquisition guiance

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

17-Sep-2026: Initial version

2

@KumarK what about PMP450 and CBRS/SAS? Is there a plan or any guidance for that yet?

Thanks,

3

JFC… this is F*&CK’d up…

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?

Please solve for NSE.

This will not be forgotten or be easy.

4

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

???

NSE ???
CBRS ???

God help us.

5

Yes @KumarK please share an answer to this…

6

Hi everybody,

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!

7

So, can we migrate devices from the cloud to on-prem without a factory reset of the device? I’ve seen conflicting information.

8

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?

9

I am also going to be offering the same assistance to those in need :slight_smile:

Thanks Joel!

10

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.

11

Yes, I did this a couple times today with APs and switches.

12

So what about ePMP and PMP450?

13

We have a lot of ePMP equipment (4600, 4600L, 4625 and 4616) online.

Will cnMaestro in the cloud keep working with those after Oct 1, or should we get an on-premise system up for those, too?

John

14

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?

15

Million dollar question for me as well!

16

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…

17

we will need two different on prem servers if there’s a split between licensed and essentials. That’s if the entitlement ever comes back

I doubt it, as a new company would need to assume and 100% take over existing. Or a new means to create and handle entitlements.

I have a feeling the administrators are turning everything off.

18

so basically the on prem is useless as well after Oct 1?

19

In the FAQ, they state this…

  1. 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.

20

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…