ExtremeCloud™ IQ UI Transition: What You Need to Know

[SamPirok]

The ExtremeCloud™ IQ classic UI will be retired Q4 calendar year 2026. The new UI has been available  since July 2025 to ensure customers have ample time to become comfortable before the classic UI is retired.

We will be transitioning from the classic UI to our modernized new UI which will become the default interface for all ExtremeCloud IQ customers in July 2026. The classic UI will be officially retired in Q4 2026 (before December 31, 2026). 

Why is This Transition Needed?

• ExtremeCloud IQ classic is based on legacy architecture
• No new features are being added in ExtremeCloud IQ classic 
• All features / capabilities are developed in ExtremeCloud IQ new UI and Extreme Platform ONE 

Seamless Transition to ExtremeCloud IQ new

• Customers will have a new UI and UX to manage their networks with ExtremeCloud IQ new 
• There will be NO IMPACT to customers data / networks / logs / devices 
• Customers will continue to manage and monitor their network as they have been doing prior to the upgrade

What’s Changing

• ExtremeCloud IQ is transitioning from the classic UI to the new UI experience.
• This is a user interface update only. The underlying platform, configurations, policies, and data remain unchanged. 
• There are specific features that will not be available in ExtremeCloud IQ’s new user interface based on customer usage or were not working in prior releases 
• There are specific 3rd party switches that will no longer be supported with ExtremeCloud IQ’s new user interface

What’s Not Changing

• No impact to network operations
• Same URL and login credentials
• No configuration, policy, or data loss
• No licensing or entitlement changes 

Resources

• UI Transition FAQs (attached)
• UI Feature Comparison (attached)

UI Transition Workflow Videos- Classic to new

• The following videos are available here:
• ExtremeCloud IQ UI Transition Introduction
• Device Filtering
• Device Onboarding
• Device Status, Health, Usage Capacity
• Menu Changes
• Upgrading Device

[IwanB]

We have built many automated tasks and queries using the ExtremeCloud IQ API  https://api.extremecloudiq.com/swagger-ui/index.html.  Can you confirm whether this API and its current endpoints will remain supported and continue to work as expected in the future?

[CalvinRempel]

I'm not finding any mechanism to effectively manage existing users (e.g. Manage > Users) for our Guest WiFi. I make use of bulk user creation, user exports, large scale user deletion, and looking up of users for resetting passwords and troubleshooting. The only thing I could find is under Network Policies, but this is not a sufficiently robust user management tool to meet our needs.

Another set of items that would be a nice-to-have is:
- sortable everything: in the Classic Interface, a lot of columns are arbitrarily not sortable - it would be nice to be able to sort by nearly any column.
- complete sortability: when I sort guest users by name, I get one page of A-Z, and then the next page is also another group of A-Z, rather than the entire user list sorted A-Z (put another way: each page gets some of the A's, some of the B's, etc, rather than having a few pages of all the A's, and THEN all of the B's, etc). It seems like the REST functionality sends over a page of users (which, from an alphabetical point of view, is in a random order) and then the sorting sorts JUST that page, rather than requesting A-Z sorted names from the server.

[SamPirok]

Hey all, thanks for your patience today, I've been chasing down answers and didn't want to clutter up the post more with fluff updates, so here's what I've learned today:

@D_Bereda - Your question about Web SSH and advanced CLI- this is not currently slated to go in to NEW XIQ UI or EP1. If this strongly affects you, please help me understand why and I will bring your feedback to the PLM team; always happy to help bring your view point to our leadership. 

@IwanB - Your question about ExtremeCloud IQ APIs and will they be supported in New XIQ- Nothing is changing with xapi, they should all work as normal for the forseeable future. 

@bernie_noel - Appreciate all the great feedback you've given! I've made sure your points about the scroll bars in device view, the unsortable columns, and the missing columns have all been logged and we will work on getting those fixed. (Several of you mentioned those last two points, that helps, every voice added helps us raise the priority)

@DeVoID - I'm still digging for an official answer to your replacement for 1130's question (I know you're shocked, but there's debate, so we're clarifying). As to why you can't see the New XIQ UI, you are absolutely correct, it's due to your licensing. The only reason you see EP1 as your landing page now, is because of those 3 different licenses. When Classic XIQ goes away, you will only see EP1, and not the New XIQ. The plan is to have a license for either New XIQ or EP1, and both should have feature parody with Classic XIQ.

@Ralexander - PPSK in the New XIQ UI should be under Configuration> Network Policies> User Management> (several PPSK options here). I can send you a screenshot as well if that helps,  just let me know. 

@CalvinRempel - Are the options you're looking for not present under Configuration> Network Policies> User Management> (sub menu with several user management options)? If not, can you help me understand specifically what you're looking for? I can send a screenshot of what I'm look at if that helps, just let me know. Also appreciate your note about the nice to have filters, all of those have been added to PLMs list. 

@Mark_V - Appreciate the note about adding in uptime and device status, I've made sure that's on the list for PLM now. 

@SDK - I haven't forgotten your question on Fabric in New XIQ, I'm still chasing down this answer, many apologies for the long wait. 

If I haven't gotten back to you yet please forgive me, I'm trying to make sure I respond to all of you and we get all of your feedback in front of our PLM team ASAP.

I will follow up again tomorrow, please don't hesitate to continue to share any and all feedback and questions and I'll make sure they get to the right people. 

[CalvinRempel]

Oh, I see. You have to expand the heading once you are in the "Network Policies" page to get to additional menu items in that section. I would push back and say that this is not an especially intuitive way to do it, though on the flip side... I kind of like it.

In regards to @D_Bereda 's note about executing CLI commands via the web interface: we also make use of this functionality periodically. Unless something has changed that I have missed, the "WiFi Neighbors" just shows our own access points, but it is helpful to know about other people's access points when I am dialling in a facility's channel settings, broadcast strengths, etc, so that I can ensure we avoid overlap (we never had great luck with turning on automatic settings and letting it do its thing). This is where CLI commands come in - we can get this information and dump it into a spreadsheet for analysis. Granted, for myself, since I mostly operate within the same network as these devices live on, if I had to use a local SSH client to gain access to these functions it wouldn't be the end of the world. Where I could see it being an issue is if one is looking after facilities that do not share a common network nor VPN - in which case the web portal would be a helpful point of contact with these devices.

[house_arelius]

As a long-time customer going back to the original HiveManager, I’m struggling to understand the direction of the EP1 / XIQ “New” platform.

I’m hoping to better understand where things are headed, because there are a few areas where the current experience feels very different and somewhat disconnected from the platform we’ve been using for such a long time.

For example:

• Are there plans to reintroduce the level of data visibility currently available in XIQ Classic (particularly in Client 360 and the client/device views)? This includes current client/session state, client radio capability, WiFi/application, and overall health. In the new UI, the level of detail is noticeably reduced compared to what we’ve been accustomed to, which is surprising given that one of the stated goals is “enhanced monitoring, troubleshooting, and visibility.”
• I see this has already been mentioned, but I want to reinforce that customizable views and granular filtering are critical for day-to-day operations. This includes flexible column resizing, sorting, additional columns that are currently missing, more flexible filtering, and the ability to save filters for quick pivots between sites, device groups, or device/client conditions and states.
• Is there a design goal around data density? Right now the UI feels more spaced out and requires more navigation and scrolling, which makes it harder to quickly correlate information when troubleshooting.

Right now, it feels like a decent chunk of what some of us rely on for day-to-day management is either absent, less accessible, or requires significantly more navigation to piece together. At the moment, I haven’t found workflows in the new UI that are faster or more effective than what exists in Classic, so I’m trying to understand what the intended improvements are from an operational standpoint.

With the timeline set to move fully away from the Classic UI, it would be helpful to understand whether these gaps are temporary and planned to be addressed, or if the expectation is to adapt to a different operating model.

[Brent_Addis]

Hey @DeVoID  New XiQ is Extreme Platform One. If you've got access to that, it's all you need.

Don't forget this cutover isn't until Q4, with EP1 in steady development, I am sure most all of the actively used features inside XiQ will be available.

[SamPirok]

Slight add on to Brent here, New XIQ and EP1 are a lot more similar than Classic and EP1 (on purpose), but they are still in fact two separate platforms with separate licensing needs. 

[hello-world]

Hi @SamPirok ,

According to your FAQ, and some of your comments, it seems older Aerohive and other EoSL APs will not be able to be managed in the New XIQ UI. It is unclear which models of APs will be affected, with the FAQ only mentioning AP230, AP250, and AP130. What about the AP245s, the AP150s, the AP1130s? There is no comprehensive list.

My company has ben running a lot of AP250s, which have not even reached EoSL yet. We were hoping to replace them within the next few years. According to your comments, the 250s will become unmanageable only a few months after their EoSL date 5/15/2026.

Historically, EoSL has meant no RMAs and no firmware upgrades, but the AP would continue to be supported by the Extreme Cloud. Why wouldn't they be? It is the same API after all. To artificially block them from connecting to the management platform makes no sense. Such a huge policy change should have been announced far earlier, and the customers should have been given a few years to upgrade. Our account manager should have been told, and he should have been able to let us know. We received no indication that this was even on the roadmap.

Budgets have already been put in for this year, companies like ours cannot be forced to upgrade hundreds of APs within 6 months. Your EoSL page mentions Extreme cannot guarantee that hardware will continue to work after EoSL. That's a nice way to avoid liability, but clearer communication in advance that the AP250s etc. will be blocked from the cloud would have been appreciated.

I truly hope Extreme reconsiders their decision. Can your team please at least publish a full list of the currently-supported APs that will no longer be able to onboard/be managed? With such limited specific information we cannot even hold a meeting with our management yet.

I have reached out to our account manager, and he is unclear on the details as well. Apologies for the frustration, I was just kind of blindsided by this and my C-Suite needs answers.

Edit: Now I see @Nithisha is saying the opposite, that even old APs will still be able to be managed. But maybe if something breaks they will not be able to be managed(?). Can you all please clarify definitively what is going on and let the account managers know too? I already freaked out my team lead over this, and this all could have been better communicated instead of with comments buried on a forum post and vague FAQs.

[Ralexander]

@SamPirok 

---

@SamPirok wrote:

PPSK in the New XIQ UI should be under Configuration> Network Policies> User Management> (several PPSK options here). I can send you a screenshot as well if that helps,  just let me know. 

---

Found it now. That does seem a little unintuitive, especially considering you're going into a "Network Policies" menu on the left hand side, which we know to be just our Policies, only to then change to a "User Management" sub menu which isn't Policy management.
Perhaps it shouldn't say "Network Policies" in the left hand menu?
Classic made sense: 

New doesn't:

Regarding client monitoring: This also absolutely needs to be sortable so we can order by highest client count.

Classic had the ability:

[DeVoID]

As Sam pointed out, "new" and EP1 are not thew same thing.  As he confirmed its all about what license you have, and sadly we received 3 (out of 183) EP1 licenses, and we get logged into EP1.  I have to say I agree with a lot of the posts on this page (5) concerning lack of data visibility of Clients in EP1 versus Classic. Client 360 is very helpful versus trying to find anything similar in EP1.

If im being honest, i really dont like the interface at all - EP1 that is - its clunky, terminology doesnt always appear accurate, it can be slow to load, doesnt have one-for-one settings between classic and EP1 and overall there are parts of it that seem a heck of a lot less intuitive.

I can say with honesty that Ill miss classic, and can only hope that when those 3 darn EP1 licenses expire - in May - and the proper licenses get purchased, that maybe "new" will have more of a feel to classic (although from the sounds of it, it will look and feel like EP1).

 The other part that concerns me, is the fact that if backend code - the engine - of either New or EP1  changes something, which in turn makes any of those EOSL AP's crap out, then the customer is SOL seems very harsh of Extreme. But if its in writing, which it is, we do not have a leg to stand on.  That means we have to work towards purchasing newer models to replace those EOSL, knowing that will only happen when budgets are approved; but maybe a fast track is to let management know of that potential "outage" possibility and they make provisions to get us the money.  Then its on them for a timeline based on them giving funding - even though its users who shout at us... 😉 -  But of course, that means Extreme is risking the possibility that is customers management teams says, "rip it all out and go with a different vendor"... thats something I wouldn't gamble on if I were Extreme.

DeVoiD