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

[SebBinet]

In EP1, When filter device for appliance, I can see the 1130C and Tunnel Concentrator we recently deployed for our customer, but when clicking on it, nothing happen. There is also no menu available to update or request anything to/from them.

In classic UI, other than the  action/diag/update menu, when you click on those kinds of devices you are able to see classic monitoring info for the 1130C like port status and so on. And for both you have a link to proxy through XIQ to reach the local webUI.

When will it be available on EP1 ? (but the list of missing features is so long that it should be wayyyyy under the features implementation list)

[DeVoID]

@WW oh boy!

Now that I was right, and I have the XIQ "new" and the lovely XIQ Classic, I see so much more disparity between the data from one to the other.  Latest is an AP in EP1/New with an alert of "insufficient power" for PoE... You guess it, in Classic its completely fine....

Honestly I think they are quite literally programming at crazy speed trying to get it all just shoved over into the newer interfaces (remember EP1 and New are the same thing, just ep1 has Ai) as quickly as possible - with errors and bugs -.

"They" are probably banging away at their keyboards to get that code shoved in as I type this out.

DeVoiD

[DeVoID]

@SebBinet Have you tried the left menu... Monitoring >> Network Devices ?

There are a few things under that, like wired, wireless sd-wan, etc....

It might be there.  If it is, click the 3 vertical dots to the right of the listed equipment, that will open up access to Actions (reboot, update, etc).

And yeah, lots missing, and also not the same data between Ep1/New and Classic.. I just posted about PoE .. insufficient in EP1 and just fine in Classic....

DeVoiD

[DeVoID]

@WW I tried the same thing, with and without the :'s after each two characters and like you, "nothing found'... What the heck!?

I used my iPhone's MAC address, which I knew was on wifi - for a couple of hours at least -, and not a thing!

Like you I went back into Classic and it found it right away.

This kind of search is a BASIC requirement/necessity, and should be one of the first "things" to work!!  This is honestly appalling.  My hope is that Classic "lives" beyond the end of the 4th quarter, so we have a "backup" interface not only for functionality, but for the integrity of the data we see (EP1/New not matching data with XIQ Classic).

DeVoiD

PS: Oh and that Real Time Troubleshooting - near the top right -.  Monitoring >> Clients>> Wireless - doesnt work.  Click on it, and fill in the fields, like the MAC (has to have the :'s) address, then Location, BUT then it requires which AP the client is on!!!!!! BUT - again - it doesnt matter what I type in, it pops up "No search results found" and the "start & Stop" buttons remain un-clickable....  I should be able to simply put the clients MAC into a field, press enter and it displays all the properties, including which AP its on! I can do that in Classic!  @WW  give it a shot, see what I mean.

[JuSeu]

I’ve recently started using the new UI more seriously for day-to-day work, and honestly, it just makes me want to go back to the old UI.
Right now, I find it hard to trust the new XIQ when working on production setups. Just yesterday, while creating a new network policy, all SSIDs suddenly disappeared and didn’t come back for a couple of minutes. That’s a bit of a heart-stopping moment, since it immediately looks like something went seriously wrong.
But besides such major issues, there are also a lot of smaller bugs that make the overall experience pretty frustrating.
In a few menus, the Help button overlaps with the Save button. It also seems to register clicks slightly below where it visually ends, which makes hitting “Save” difficult at times. It's so annoying when you're making a lot of changes.
When I tried to change the DNS directly in a network policy, it unexpectedly overwrote and renamed the existing object. When I tried to revert that, it suddenly created a completely new object instead, which was quite confusing.
I do like the overall look of the new UI, but in its current state, it’s hard to rely on for daily work. I also really miss features like the Config Audit, as well as the ability to customize columns in the device overview.

[DeVoID]

@JuSeu Sadly you are preaching to the choir.  I can imagine that Heart Stopping moment.  Thankfully "my stuff" is set up, and I do not have to change things often (although this summer im putting in 17 x AP4060x's due to EOSL AP1130's), but I think everyone who has posted in this thread has seen and had exactly what you are describing.

Then you move onto seeing different data in New/EP1 versus Classic (with Classic what I trust 99% versus the others), and you have a bit of a nightmare. I dont trust New or EP1. Read all of this thread and you will see actual screenshots of one versus the other, which proves something isnt right about the data, and when Classic goes away, how CAN you trust what you know wasnt accurate previously!?.  Thats a huge issue. 

So yup, we feel your pain. 

Id suggest each bug or anomaly you encounter, do a post in this thread.  @SamPirok did say they will keep up on this thread and pass along anything in it to the relevant people. Its a good idea.

Oh, and do you like the fact you have to constantly hit their refresh button to see if an AP is up or down - or anything else - ?

DeVoID

[EF]

Hi Team,

keep in mind, Essentials --> Extreme Guest is not avalible at new XIQ new yet.

Regards

EF

[DeVoID]

@EF A lot of things are not in EP1/New "yet"..  I have a sinking feeling that its going to be a long "yet" before we see almost full feature parity between Classic and EP1/New. 

We really also need the data to be the same between Classic and the others; thats what baffles me. They are edge devices, the data should be exactly the same between all of them - new and older -, unless there are bugs in their math within the new platforms and it displays that after ingestion.

DeVoiD

[house_arelius]

At this point, I think it is worth stepping back and looking at the broader issue.

The transition announcement states that customers will have a new UI and UX to manage their networks with ExtremeCloud IQ New, with no impact to customer data, networks, logs, or devices. It also states that customers will continue to manage and monitor their networks as they had prior to the upgrade, with no impact to network operations and no configuration, policy, or data loss.

The problem is that throughout this thread, customers are repeatedly showing and describing a very different reality:

• Missing core workflows
• Inconsistent representations of data
• Unreliable health indicators
• Broken or confusing configuration workflows
• UI anomalies such as overlapping elements, unclickable controls, or objects unexpectedly disappearing
• Missing features
• Reduced visibility
• Basic table, sorting, and filtering functionality that is either absent or significantly reduced

Those two realities cannot both be true in any meaningful operational sense.

This is no longer simply a question of whether someone likes the new UI. If the new experience removes or weakens core workflows, reduces visibility, presents inconsistent data, performs poorly, and makes production changes harder to validate, then there is an operational impact.

Across this thread and in my own experience, I have not seen one clear example of something the new platform does better than Classic from a day-to-day operations standpoint. I also have not seen workflows that are faster, clearer, or more effective. The most common positive feedback appears to be that the new UI looks cleaner, but appearance does not compensate for reduced capability or reduced trust.

For me, this has shifted from:

“Do I like the new UI?”

to:

“Do I trust this platform's management plane and release process enough to keep building my environment around it?”

As one example, if I need to quickly update an existing network policy during incident response, or apply a dedicated isolation policy to a location or specific fleet of APs, the 10 to 20 seconds it currently takes in EP1 for the embedded Network Policies interface to load matters. So does the lack of usable filtering needed to quickly narrow down the APs I need to target. That is not just a UI preference. That directly affects operational response.

This example is only one piece of a larger concern. Others have raised issues around client visibility, health indicators, configuration workflows, troubleshooting tools, performance, filtering, and inconsistent data representation. Taken together, these are not minor UI preferences. They directly affect confidence in the platform.

Right now, the messaging says “no operational impact,” while the customer experience being described here says otherwise.