How to copy records from global to scoped

[jhb]

Hello All,

We are planning to move from global application to scoped application. We should move all the records (incidents, problem, cases...... not scripts, record producers..etc) present in global space to scoped. When I try running a fix script to copy records from global application to scoped application, system is throwing an error of cross-scoped access is denied. Can someone help me on how to copy the records or can someone share the link if someone have already got a solution for it?

Also, is there any way for scripts, record producers....etc to be copied from global to scoped instead of recreating them again in scoped app? 

Thank you. 

[Kiel Sanders]

I would recommend reviewing the HR Scoped Application Migration FAQ document for more details on the migration to the scoped HR app.  There are some components that require more review since it's not a 1:1 copy of records.  We have introduced HR Services within the scoped app as a core foundational element of HR Cases, which requires special attention to how the configurations are made in the new application.  In general, we recommend customers do not migrate their legacy cases.  More information can be found under the What do I need to consider when migrating? question in the FAQ.

There are some scripting items that you can easy duplicate into the scoped app by selecting the HR scope and performing an Insert & Stay.  This will create a duplicate record in the new scope; however I would recommend reviewing the delivered functionality first.  Many customers have found that custom functionality they built previously is no longer necessary because it is part of the delivered functionality now.

If you are trying to script some of these conversions and receiving the cross-scope access issues, it is likely Restricted Caller Access (RCA) blocking this.  You can learn more in the product docs or our Ask the Expert recording.

[bryan_strasburg]

jhb,

You mention inc,prob,cases, but have posted in HR.  I'm going to assume you are talking about moving from the legacy HR global application to the newer scoped HR Service Delivery application.

My first comment is that, in my opinion, this is a crucial, but non-trivial, activity.  I definitely suggest getting some advice from ServiceNow Professional Services or a ServiceNow Partner with experience specifically doing this HR global to scoped migration.  I'll go ahead and plug both The Anti or my group, ITG, as partners with this expertise.  

With that out of the way...

ServiceNow does have a plug in specifically to address this migration.  Docs page HERE.  

My quick two cents on this migration:

There is a lot more to this migration than moving data and roles.  The newer HR Service Delivery product is a different way of thinking.  Instead of categorizing HR cases, we now focus on the HR Services that HR delivers.  Cases are worker interactions of one of those services.  This difference is the biggest thing to tackle.

Good luck!

[bryan_strasburg]

Ha, Kiel always answers better than I do.

Quick side note:

As Kiel points out, it is definitely caller access restrictions stopping you from running your fix script.

DON'T override this caller access restrictions.  I too often see customers / partners not understand caller access and, say, allow access to HR Profile from other scopes.  You don't want to do this.  Application Restrictions exist for a reason.