Migrating from Core UI to Angular portal

---
title: Migrating from Core UI to Angular portal
description: Administrators on upgraded instances must install the com.glideapp.servicecatalog.ui16\_portal plugin to migrate from the Core UI catalog experience to the Angular portal.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/servicenow-platform/service-catalog/migrate-core-ui-to-angular-catalog-exp.html
release: brazil
product: Service Catalog
classification: service-catalog
topic_type: reference
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [Service catalog setup, Configuring Service Catalog, Service Catalog, Manage service capabilities, Extend ServiceNow AI Platform capabilities]
---

# Migrating from Core UI to Angular portal

Administrators on upgraded instances must install the `com.glideapp.servicecatalog.ui16_portal` plugin to migrate from the Core UI catalog experience to the Angular portal.

On new instances, the `com.glideapp.servicecatalog.ui16_portal` plugin is active by default. On upgraded instances, administrators must install the plugin manually to move requesters from the Core UI catalog experience to the Angular portal.

When ordering an item, requesters start viewing the Angular portal instead of Core UI.

In Angular portal, catalog items behave as they do in Service Portal, including client scripts and UI policies.

**Note:**

For the plugin installation procedure, see [Install an application or plugin](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/platform-administration/installing-applications-in-application-manager.md).

**Parent Topic:**[Service catalog setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/service-catalog/p_ServiceCatalogs.md)