Migrate Legacy GRC to new Modules

Matt Dumont1 · ‎07-27-2017

Has anyone done the migration from Legacy GRC to the new separate modules? We're interested in doing so, but need to come up with an estimated LOE for our project plan. We are aware of the migration tool, but there are several functions of Legacy GRC that are not supported by that tool, so we would like to get some insight into the true difficult from someone who has accomplished the task. Thanks!

Matt Dumont1 · ‎08-29-2017

Mr. Ramlochun,

Thank you for the input. We did find that documentation. As with many things in ServiceNow, implementation often takes longer in practice than in theory. In case anyone was wondering, I have entered the answer from ServiceNow HI below:

It takes anything between 1-2 months for the entire migration process. This activity includes following steps: 1) Understanding differences between legacy and current GRC modules 2) Understanding and creating profiles and profile type structure 3) Identifying control and profile relationships 4) Migrating risks, policies, controls, authority documents, citations etc. using migration utility 5) Migrating Control test definitions to indicator templates for creating manual indicators using migration utility 6) Coming up with custom scripts for other migrations if they are not available as part of out of the box migration utility 7) Migrating all legacy custom fields into new GRC modules 😎 Once all the data is migrated, mapping all the right permissions/roles with all your custom roles and groups (if any) There might be other activities involved based on how the customer has set up the legacy system.

View solution in original post

Michael Bachme1 · ‎10-18-2018

How do we accomplish migrating the unsupported table structure? Are there field mappings to understand the replacement(s)? (i.e. Audit [grc_audit / field] --> [new_table_name / field])

Thanks in advance.