Platform Analytics - Classic Dashboard Migration

Nenad Berbatovi
Tera Contributor

Dear community,

 

On Dashboard Overview page in the classic ui we can see the message explaining that dashboard migration to the  platform analytics will take place in Yokohama release (Q2 2025). We can test this migration before. And I did it. 

My dashborad was correctly migrated. I can see the "old one" (classic UI) with mention "inactive". What does this means? I can edit it... What will happen with existing dashboards in classic UI in Yokohama? Would we be able to make new dashboards in classic UI or it will not be possible starting Yokohama?

 

Best regards,

 

Nenad

 

1 ACCEPTED SOLUTION

Mark Manders
Mega Patron

On Yokohama nothing will happen. With the Zurich release everything will be migrated (no way of opting out, Platform Analytics will be the only way to go).

You still have access to the old dashboards and reports, but the question is, why would you want to? Start creating everything on Platform Analytics now, because you will need to get used to it. With/after Zurich, the old modules will disappear and Platform Analytics will be the only way to go.
And 'inactive' just means: no longer used, because you migrated it (read that as 'no longer supposed to be used').


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

View solution in original post

11 REPLIES 11

@mikkojuola There no longer is a mandatory migration. When Australia is released, you will no longer be able to create 'old' reports and dashboards, but you can still use them (read only). New stuff needs to be created in PAE, but no mandatory/forced migration anymore.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

bvlo
Tera Expert

I am in the exact same spot at the moment. How do I point to the new / migrated dashboard? Most of my end users' landing pages contain dashboards; how did you handle transitioning them to the new dashboard boards once you migrated all the "old" dashboards? 

Migration will put redirection in place as well. But don't think too lightly about this. You can't just ignore users and do the migration. You need to inform them. Tell them things are going to be different. Tell them 'view / run' will no longer exist and tell them where to go.

 

And as an addition to my answer from August: the mandatory migration is extended to at least Australia. They found out Zurich will be too early.

Also: asking a question on someone else's question is never a good idea. It may get you an answer, but creating your own makes it more manageable (and doesn't bother subscribed users with notifications of an old question that was already answered).


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

"You can't just ignore users and do the migration. You need to inform them. Tell them things are going to be different."

 

This is exactly what I am trying to accomplish but I have to understand it first. I have migrated some test dashboards and see nothing regarding redirection. When I log in, the dashboard, which is my landing page, simply states, "Dashboard Name (inactive)." So, I don't know what to inform the end users to or go. I would this think this scenerio is not an edge use case and would be accounted for in the Migration Center, so I am either missing some basic concept here or ServiceNow is missing some basic functionality. 

Would you mind giving some insight as to where you are hearing the migration is extended to Australia? All the documentation (fairly recent) and the Migration Center still states "Zurich". This changes are planning immensely. 

After full migration you end up on the new dashboards. The single dashboard migration only migrates that dashboard, not the entire functionality that is being changed. 

 

And the extended mandatory migration was mentioned in the Platform Analytics Academy sessions with the note that communication would follow. I guess they realized Zurich was too soon, but since it used to be Yokohama and got changed to Zurich and now extended as well, they are hesitant to communicate extending to Australia, in case that's too soon as well.

This is what I heard (and also see mentioned on LinkedIn and the Community). For communication with ServiceNow logo, please reach out to NowSupport. I can't make it any more official than telling you what someone from ServiceNow said on a ServiceNow academy.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark