Migration from Core UI to Platform Analytics

[AnnaO6373147320]

Hi,

I have a couple of questions regarding the migration process from Core UI to Platform Analytics:

1. Standalone Reports: Will reports that are not currently used in any dashboards (i.e., standalone reports) be included in the migration process? If not, what should we do with them?

2. Out-of-the-Box Reports: What will happen to out-of-the-box reports during the migration? Some of these reports already exist in Data Visualization—will they be migrated again, or are they excluded from the process?

I’d appreciate any clarification you can provide on these points to help us plan accordingly.

Best regards

[Mark Manders · Accepted solution]

With Australia, you will be able to also migrate single reports. Until then, only a full migration will migrate everything. The dashboard migration is only meant for 'checking if everything is still ok'. So if you do a full migration, you will have migrated everything, including the reports that aren't on a dashboard.

OOB reports will be migrated as well (assuming you mean with the full migration [see above]). ServiceNow teams will migrate their content as well, but that could take some time. You shouldn't have active OOB reports that are also DVs. It could be that the same report exist(ed) twice? ServiceNow makes the same mistakes their clients make: creating a new report is often faster than checking if it already existed.

[Ankur Bawiskar]

@AnnaO6373147320 

this is a reference guide, please check

Moving from Classic/Core UI reporting to Platform Analytics - suggested migration path 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@AnnaO6373147320 

Thank you for marking my response as helpful.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[kaushal_snow]

Hi @AnnaO6373147320 ,

Based on the Platform Analytics Migration Guide by ServiceNow:

1. Perform a Full Migration in a sub production (non prod) or sandbox instance to ensure everything, including standalone and OOB reports is captured and can be reviewed.

2. Use the Migration Center's review tools to: Preview how each report is translated into Platform Analytics. Identify items migrating in Compatibility Mode and then decide whether to keep, tweak, recreate, or exclude (Mark Do not migrate in bulk) any content.

3. Update your migration decisions via an Update Set while in sub production. This allows those choices to be propagated when you migrate in production.

4. Finally, replicate the migration in production, activate it, and ensure proper redirection and visibility in the new Platform Analytics UI...

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.