End of life Knowledge Management UI16?

Sanna
Tera Contributor

Hi! Is there an official end date for when Knowledge Management UI16 will no longer be available? We are scheduled to upgrade to the Brazil release in December, and our plan is to transition to Knowledge Center sometime during 2027–2028.

 

Have a nice day!

 

Best regards,

Sanna

3 REPLIES 3

MaryG
ServiceNow Employee

Hi@Sanna  

As of now, I'm not aware of an officially published end-of-support date for the Knowledge Management UI16 experience.

There is an important distinction worth mentioning. ServiceNow documentation indicates that the Knowledge Management v3 homepage has been preparing for deprecation since the Washington DC release, with the Knowledge Management Service Portal identified as its replacement. However, that guidance does not specify a definitive retirement date for UI16.

I would recommend treating the transition to Knowledge Center as part of your modernization roadmap rather than waiting for a mandatory retirement date.

Is there a specific feature or functionality you're concerned about, such as the legacy article editor, article management, or another aspect of the UI16 experience? I ask because the transition to Knowledge Center and adoption of the new article editor are separate considerations, and understanding your concerns may help clarify what your organization needs to plan for.

Sanna
Tera Contributor

Hi Mary,

We are not concerned about any specific functionality at the moment. We are mainly trying to plan how and when we should transition to Knowledge Center.

I also thought of another question. In the Knowledge Center article creation form, will it still be possible to add custom fields to support an organization's specific needs, or will everything be strictly out of the box?

For example, we currently have custom fields that allow authors to select and link relevant service offerings to a knowledge article. We are wondering whether similar customizations will still be supported in Knowledge Center.

MaryG
ServiceNow Employee

Hi Sanna,

Thanks for clarifying! That helps.

The good news is that Knowledge Center does support custom article templates. ServiceNow Product Management has confirmed that existing OOTB and custom article templates are compatible with the new Knowledge Center Article Editor and generally should not require migration.

There is an important distinction, though, between supporting custom fields on the underlying knowledge record and how those fields are presented in the new authoring experience.


In your example, linking service offerings to knowledge articles is a reasonable use case, and I wouldn't expect you to have to abandon that relationship simply because you're transitioning to Knowledge Center. However, I would recommend validating how those custom fields are displayed, populated, and maintained in the Knowledge Center editor, particularly if you're using reference fields, custom relationships, or UI policies.


Since you're planning your transition for 2027–2028, I'd suggest testing a representative sample of your existing articles, templates, and custom fields in a sub-production environment before establishing your migration timeline.


One other consideration: Knowledge Center and the new article editor can be adopted separately. ServiceNow provides a property (
sn_km_center.glide.knowman.ece.enable) that allows organizations to continue using the legacy editor within Knowledge Center. That may give you some flexibility in planning your transition.


Here are two useful references:

I hope that helps with your planning!