Platform Analytics experience upgrade: FAQ for Dashboard Owners

[Dan_Kane]

Common questions about upgrading from Core UI to Platform Analytics, addressed for dashboard owners and content creators.

How to use this FAQ: Click any question to expand or collapse it. Use your browser’s search (Ctrl+F / Cmd+F) to find topics by keyword — collapsed sections are searched automatically in Chrome and Firefox.

---

Q1  ·  Is migration required, and is there a deadline I need to plan around?

Migration is not required. Your existing Core UI dashboards remain accessible and usable after upgrading to Australia or later releases. Beginning with Australia, new Core UI content creation is still available and will remain so through the end of 2027 — this deadline was extended from prior communication based on customer feedback requesting more preparation time. Migrated and unmigrated dashboards are accessible from the same unified Library interface.

Core UI dashboards that have not been migrated are available to view and edit. Starting with Australia, Core UI is unsupported in a specific sense: ServiceNow will no longer release new product capabilities or bug fixes for Core UI content, with the exception of critical security issues. Support assistance for Core UI-related issues remains available. If an issue is caused by a Core UI product defect, the resolution path is to migrate or recreate the content in Platform Analytics rather than wait for a product fix.

Q2  ·  What will happen to my legacy reports and dashboards after upgrading to Australia?

Your legacy reports and dashboards are unaffected by the upgrade. You can continue to run, view, and edit them after upgrading to Australia or any later release.

Starting with Australia, legacy content is accessible within the Platform Analytics UI. Legacy dashboards appear alongside Platform Analytics dashboards in the unified Library. A UI version column indicates which experience each dashboard will open in, so you can see at a glance which content is legacy and which is Platform Analytics.

Q3  ·  I’ve seen that support for Core UI ends after Australia. Doesn’t that contradict the statement that I can use legacy content indefinitely?

No — these are not contradictory. You can continue using Core UI content indefinitely. What changes is the scope of support: the Support team will help you with usage questions and troubleshooting, but ServiceNow will no longer develop or release product fixes for Core UI defects. If an issue is caused by a Core UI product defect, the resolution is to migrate or recreate the content in Platform Analytics. Legacy content that is working correctly remains usable without any required action.

Q4  ·  Can I migrate my own dashboard, or does this require a system administrator?

Starting with the Zurich release, dashboard owners can self-service migrate the dashboards they own. You do not need to involve a system administrator to migrate your own content. Migration is initiated from the Migration Center (navigate to Analytics Administration > Migration Center).

System administrators and users with the analytics admin role can run a full migration across all dashboards in the instance.

Q5  ·  How do I know what’s in my dashboard before I start?

The Migration Center includes a “Try your content” preview that lets you preview an individual dashboard in Platform Analytics without committing to migration. You can use this to assess how your dashboard renders before triggering a full migration run.

After a migration run in sub-production, the Migration Center flags every item that migrated in compatibility mode and provides detailed logs at par_coreui_migration_bridge_component. This surfaces items that need attention before you run production migration.

Q6  ·  Will my dashboard look and behave the same after migration?

Most dashboard components migrate to direct Platform Analytics equivalents. Reports and PA widgets become Data Visualizations. Interactive and breakdown filters become Platform Analytics Filters. The dashboard layout is preserved for responsive dashboards.

Specific items migrate in compatibility mode rather than as native Platform Analytics components (see Q8). A small set of items do not migrate automatically and require a deliberate decision (see Q9). The Migration Center surfaces which items fall into each category; a side-by-side comparison view is available for each migrated dashboard.

Known migration fidelity issues — including filter condition preservation, tab name translations, and static content translation — are documented in the Interactive Known Issues Companion, with fix status and workarounds where available.

Q7  ·  What if my legacy dashboard or report doesn’t migrate cleanly, or loses functionality after migration?

Do not keep the migrated version as your working copy until the underlying issue is resolved or you have recreated a working equivalent in Platform Analytics. You can continue using the legacy version for as long as needed — there is no requirement to complete migration by a specific date.

Q8  ·  What is compatibility mode, and what does it mean for my content?

Compatibility mode is how the Migration Center handles content that cannot be fully converted to native Platform Analytics components. These items are embedded as iframes within the migrated dashboard.

Content that migrates in compatibility mode includes: Funnel, Pyramid, Trendbox, Histogram, and Control reports; word clouds; some custom filters; and static HTML content blocks. Dashboards containing compatibility mode content load more slowly than fully native dashboards. End users can still configure compatibility mode content.

Compatibility mode is a migration outcome, not a permanent state. You can leave low-priority content in compatibility mode or replace it with a native Platform Analytics visualization.

Q9  ·  What content requires special attention or won’t migrate automatically?

Workbench process widgets

Starting with PAe Bundle v8.0 (Australia), existing Core UI Workbench widgets can be added to PAe dashboards as an element in the dashboard component picker. The Workbench renders within the PAe dashboard with styling matched to the PAe experience. This capability requires the system property com.snc.pae.workbench_enabled to be set to true; it is false by default and must be explicitly enabled by an administrator.

New Workbench creation is not available from within PAe. Attempting to create a new Workbench from the PAe editing experience redirects to Core UI, where Workbench creation continues to work as before.

Static HTML content blocks

Static HTML content blocks migrate in compatibility mode and render as iframes within the migrated dashboard. A warning message — “This is a migrated content block. Behavior may be different than expected.” — is displayed on migrated content blocks; this is intentional. If a migrated content block is removed from a PAe dashboard and the change is saved, the block cannot be re-added.

A known active defect affects static content blocks that contain HTML: HTML tags may appear as literal text after migration to the Platform Analytics rich text visualization. A fix is targeted for the Brazil release. This is documented in the Interactive Known Issues Companion.

Dynamic Content Blocks

Dynamic Content Blocks are not supported in the Platform Analytics inline editor. This is a deliberate architectural decision, not a migration gap. The PAe inline editor is designed specifically for analytics dashboards — KPIs, trends, and visualizations — while Dynamic Content Blocks require a different model. To recreate dynamic, context-aware dashboard behavior in Platform Analytics, use Technical Dashboards with Data Resources instead. For a detailed explanation, see Dynamic Content Blocks vs. Data Resources: Why the Model Changed.

If you prefer to keep your existing Core UI dashboards with Dynamic Content Blocks running rather than migrate to Technical Dashboards, those dashboards will continue to be accessible indefinitely.

Items with no migration path through the Migration Center

The following require a deliberate plan — recreate in Platform Analytics or leave on Core UI:

• Indicator Scorecard — Show Distribution and Bullet variants. Not migrated by the Migration Center. Recreate using a column chart with reference line or equivalent Platform Analytics visualization.
• Calendar year view / year-highlighting indicators. Not migrated. Rebuild using Platform Analytics date range and time series capabilities.
• Non-responsive dashboards. Must be opened first to allow layout conversion; the Migration Center cannot process a non-responsive dashboard otherwise.
• Legacy PA widgets without a parity version in Platform Analytics. If a parity version exists, the Migration Center can migrate the widget directly. If no parity exists, recreate the widget natively in Platform Analytics.

Q10  ·  Can I test migration before it goes live in production?

Yes. The recommended process is to run and fully evaluate migration on a non-production instance before triggering production migration. Use a non-production environment that closely resembles your production instance in terms of dashboard content. Run migration during off-peak hours in both environments.

You cannot move migrated content from a non-production instance to a production instance — each environment’s migration must be run independently.

Q11  ·  What happens to bookmarks and saved links my users have to this dashboard?

Bookmarks are not migrated. Starting with the Zurich release, users who follow a bookmark, favorite, or direct link to a Core UI dashboard are automatically redirected to the migrated Platform Analytics version when a full migration has been completed. With a partial migration, system administrators can enable this redirect behavior by setting com.glide.par.coreui.migration.admin_redirection.enabled to true.

Q12  ·  What happens to Scheduled Exports associated with my dashboard?

Scheduled Exports are carried through migration. Known issues affecting Scheduled Export behavior after migration — including loss of Business Calendar configuration and PDF rendering behavior — are documented in the Interactive Known Issues Companion, with fix status, target releases, and workarounds.

As a post-migration step, run a test PDF export for any dashboard that backs a Scheduled Export before relying on it in production.

Q13  ·  Are there any licensing or entitlement changes when using Platform Analytics?

No. You remain entitled to all capabilities you had in the legacy system. Some newer capabilities — such as AI-driven features — may require additional licensing.

Q14  ·  Can I undo a migration if something doesn’t work?

Individual dashboard rollback is available via the Migration Center. You can revert a specific migrated dashboard to its Core UI state if needed. A full instance rollback is also available, but requires contacting ServiceNow Technical Support.

Important limitation: content created in Platform Analytics after migration was completed is not included in a rollback. Only content that existed before migration can be restored. Core UI dashboards that were migrated are set to inactive after migration but are not deleted from the instance.

---

© 2026 ServiceNow, Inc. All rights reserved. The development, release, and timing of any fixes referenced in this article remains at ServiceNow’s sole discretion.