---
sourceDocument: Brazil Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/now-intelligence

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Platform Analytics Migration Center

# Platform Analytics Migration Center {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Platform Analytics Migration Center

The Platform Analytics Migration Center enables ServiceNow customers to migrate their Core UI data---including dashboards, reports, interactive filters, and Performance Analytics widgets---into the unified Platform Analytics experience.
This migration consolidates visualizations and filters from multiple data sources into a single, streamlined environment accessible via the Platform Analytics library.
Show full answer Show less  
Since the Zurich release, both Core UI and Platform Analytics dashboards coexist in the library, allowing analytics managers to selectively migrate individual Core UI dashboards. From the Australia release onward, Platform Analytics experience is enabled by default for all users upon upgrade.

## Key Features

* **Comprehensive Migration:** Most Core UI dashboard content migrates successfully to Platform Analytics experience, ensuring continuity of analytics assets.
* **Compatibility Mode:** Content without direct Platform Analytics equivalents is migrated within containers (iframes) to maintain access without disruption.
* **Migration Process Steps:**
  * Remove unused dashboards and reports to optimize migration.
  * Run the migration procedure to identify compatible and compatibility-mode content.
  * Review migration results to exclude outdated or unwanted content.
  * Activate migration to finalize the transition.
  * Create custom content using tools like UI Builder for unsupported content.
* **Automatic Updates:** The Migration Center automatically updates previously incompatible content during ServiceNow upgrades when compatibility is improved.
* **Menu Changes Post-Migration:** After activation, all analytics assets are accessible under Platform Analytics \> Library, replacing previous navigation paths like Self Service \> Dashboards.
* **Migration Control:** Administrators can block or control migration actions by setting the system property `com.glide.par.coreui.migration.enabled` to `False`, disabling migration start and activation options as needed.

## Key Outcomes

* **Unified Analytics Environment:** Customers gain a consolidated analytics platform with consistent dashboards, reports, filters, and KPIs across all data sources.
* **Streamlined Content Management:** Migration encourages cleanup of unused content and facilitates creation of new, customized visualizations.
* **Controlled Migration Process:** Customers can carefully plan, test, and activate migration in non-production and production instances using Migration Center tools rather than update sets.
* **Enhanced User Experience:** Users access all analytics content in a single location, simplifying navigation and improving usability.  
When you migrate your Core UI data, your existing dashboards, reports, interactive filters, and Performance Analytics widgets are moved to Platform Analytics. When you activate the migration, the result is a single set of visualizations and unified filters for all data sources.  
Note:  
To learn more about Platform Analytics and the Migration Center, see the [Platform Analytics enablement toolkit](https://sn.works/analytics/pae) on the ServiceNow Community.

From the Zurich release, both Core UI and Platform Analytics experience dashboards and visualizations sit side by side in the Platform Analytics library. Analytics managers can choose to migrate individual Core UI dashboards from the common library page.

Platform Analytics experience is enabled by default for all users on upgrade to Australia.

Once migration is complete, you won't be able to add Core UI reports, PA widgets and filters to Platform Analytics experience dashboards. It is possible to add only migrated content and content created within Platform Analytics experience to these dashboards.

You cannot use update sets to move the migrated material from a non-production instance to a production instance. Test the migration on the non-production instance and then use Migration Center functionality to migrate the production instance.

## What is migrated {#data-migration__section_zlg_w5s_xxb}

Both Core UI and Platform Analytics experience content is available in the library. The migration process takes your dashboard content and migrates it from Core UI (Dashboards and visualizations in the classic environment) to Platform Analytics experience. If you use indicators, you get tools to alert you of significant changes.  
Note:  
When you upgrade releases, the Migration Center automatically migrates any previously incompatible content that is now compatible.

## What isn't migrated {#data-migration__section_hg5_bvs_xxb}

The short answer is that almost everything is migrated. Most Core UI dashboard content is supported in Platform Analytics experience. Some content doesn't have an analogous Platform Analytics feature. Any dashboard with content that isn't migrated and is migrated into a container, also called an iframe. This is called Compatibility mode. For detailed information about
content that isn't migrated, see [Unmigrated content and compatibility mode migrations](https://www.servicenow.com/docs/v80suBJDhP9cWwf70RwFxA "Most dashboard content is migrated to the new Platform Analytics experience. However, some visualizations, aspects of visualizations, filters, and configurations can't be migrated. Dashboards with this content are migrated as embedded content (iframes), also known as compatibility mode.").

## What is the migration process {#data-migration__section_tdl_pxs_xxb}

The migration process has the following steps.

Remove unused dashboards
:   Remove any unused dashboards and reports to promote a streamlined process.  
    * Navigate to pa_dashboards.list, select the dashboards you want to delete, and then select Actions on selected rowsDelete.
    * Navigate to AllReportsAdministrationAll, select the reports you want to delete, and then select Actions on selected rowsDelete.
    {#data-migration__ul_vpz_j5h_rzb}

Run the migration procedure
:   The procedure identifies what can be migrated directly into Platform Analytics and what is migrated in Compatibility Mode.

Review the migration results
:   You may identify dashboards or other content that you don't want to migrate, for example, unused dashboards, out-of-date visualizations, or filters that don't work as expected.

Activate the migration
:   Activation might be time-consuming, depending on how much content you're migrating.

## Create custom content {#data-migration__section_rlx_bys_xxb}

You can use tools such as UI Builder to create custom content that meets the needs of content that doesn't migrate.

## What happens to my menus {#data-migration__section_tf3_kys_xxb}

Before migration, users navigated to Self ServiceDashboards to view the dashboard overview and to ReportsView / Run to view the list of reports. After you activate the migration, all analytics content, including dashboards, data visualizations, filters, and KPIs are under Platform AnalyticsLibrary.

## Block Migration Options {#data-migration__section_at3_33r_rcc}

You can disable the Start Moving and Activate
Platform Analytics experience options. Create the system property `com.glide.par.coreui.migration.enabled` and set it to <kbd class="ph userinput">False</kbd>. If you set the property to
<kbd class="ph userinput">False</kbd> before you migrate any content, both options are turned off. If you set the property to false after you migrate your content, only the Activate button is inactive.

If you want to start the migration and view what artifacts are in compatibility mode, and resolve any issues, set the property to <kbd class="ph userinput">False</kbd> after you run the migration to help prevent activation of Platform Analytics experience. If you want to prevent the migration process, set the property to <kbd class="ph userinput">False</kbd> first.

For more information, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).

*[\>]: and then


