What are the considerations, procedures and steps when migrating from UI16 to Next Experience?

[Rain Vaine]

Hello experts,
After finding this article:
https://www.servicenow.com/community/now-platform-articles/prepare-to-turn-on-next-experience-in-van....

I find that the info here is very general. Did anyone of you have any additional insights to share when migrating from UI16 to Next experience? Any area that we need to watch out for when migrating to Next Experience? Aside from customizations, are there any special things to take note of when migrating to new UI?

Regards,
Vaine

[Dr Atul G- LNG]

Hi @Rain Vaine 

The article you shared is excellent, and I'd like to share my perspective as a BPC.

The migration of interfaces is a significant challenge, akin to shifting users' mindsets. Training plays a crucial role here, so it's essential to plan an adequate number of training sessions for users.

Additionally, it's not necessary to enable all features during the initial phase. First, identify the primary changes introduced by the new experience and categorize them based on user roles—what's most relevant for developers, end-users, and fulfillers.

Test these changes in the development environment first, and then prepare training documentation and FAQs accordingly. You may encounter resistance from users who wish to revert to the older interface, so it's important to highlight the benefits to convince them effectively.

I hope these points prove helpful!

[Brad Tilton · Accepted solution]

Hi Rain,

The link you have is a pretty good resource, but here's another one: https://www.servicenow.com/community/next-experience-events/next-experience-academy-10-what-you-need... 

For the most part, when you move to the new UI, all that's really happening is that there's a new/different header and sidebar, and some icons and buttons have moved around on the list and form pages due to accessibility and user experience improvements.

The main thing I'd think about is change management and communicating out to your user based what the changes are and how the affect them.

One thing I want to address from the other answer is "Additionally, it's not necessary to enable all features during the initial phase. First, identify the primary changes introduced by the new experience and categorize them based on user roles—what's most relevant for developers, end-users, and fulfillers." There is not a way to only implement part of the new UI. It's just a property you turn on.