Application Migration
This is used for migrating ServiceNow scoped applications from one instance migration to another.
Tables and Fields
(Release 2). This project is used to migrate table and field definitions from one application to another.
Note that additional migrations will be required to create/update any views and forms defined for these tables.
Forms and UI
(Release 6). This project is used to migrate form and UI objects from one application to another. Ensure that you set the project variables on the Variables tab when executing.
Development Objects
(Release 5). This project is used to migrate Development Objects from one Service Now application to another. It is recommended that this project be run using the migration method Import Set (Scripted) with business rules turned OFF and Migrate SysIDs set to No.
Service Portal
(Release 7). This project is used to migrate Service Portals and related objects from one Service Now application to another. Ensure that you set the project variables on the Variables tab when executing.
Navigation
(Release 6). This project is used to migrate Navigation objects from one Service Now application to another.
Business Rules and Client Scripts
(Release 2). This project is used to migrate Business rules and Client scripts from one Service Now Instance to another. It is recommended that this project be run using the migration method Import Set (Scripted) with business rules turned OFF and Migrate SysIDs set to Yes. Migrating without these options could invalidate the migration of reference fields.
Change Management
Configuration
(Release 1). This template supports migration of Change Management Configuration data from one Instance to another. The project can be run more than once if necessary if the source instance is still in use.
During the initial migration, all records are created as new, then for subsequent migrations, existing
records are updated (where configured) and records created since the previous migration are created as new.
Proposed Change Requests
(Release 1). This template supports migration of Proposed Changes from one Instance to another. This template is best suited to a migration to a greenfield instance where Precision Bridge has already been used to migrate the reference data.
Change Requests
(Release 1). This template supports migration of Change Requests and related data (including workflow) from one Instance to another.
CMDB
Application CI's
(Release 3). This project is intended to migrate Application Configuration Items only.
Cluster CI's
(Release 3). This project is intended to migrate Cluster Configuration Items only.
Endpoint CI's
(Release 3). This project is intended to migrate Endpoint Configuration Items only.
Facility CI's
(Release 3). This project is intended to migrate Facility Configuration Items only.
Hardware CI's
(Release 3). This project is intended to migrate Hardware Configuration Items only.
Storage CI's
(Release 3). This project is intended to migrate Storage Configuration Items only.
VM CI's
(Release 3). This project is intended to migrate VM Configuration Items only.
Miscellaneous CI's
(Release 3). This project is intended to migrate Configuration Items not included in other templates only.
CI Relationships
(Release 2). Migration of CMDB CI Relationships from one Service Now Instance to another.
Contracts
(Release 1). This template is used to migrate Contracts from one Service Now Instance to another. It is recommended that this project be run using the migration method Import Set (Scripted) with business rules turned off.
Customer Service Management
Configuration
(Release 1). This template supports migration of customer service management configuration data from one Instance to another. Run this before migration accounts and cases. This should be run AFTER the migration of any referenced foundation data, in particular the Organization and CMDB.
Accounts
(Release 1). This template supports migration of customer service management accounts and related data from one Instance to another. Run this before migrating cases. This project assumes that referenced foundation data, in particular the Customer Service Configuration records, Organization and CMDB have already been migrated.
Cases
(Release 1). This template supports migration of customer service management cases and related data (including workflow) from one Instance to another. If workflow is being migrated, the Workflow definitions should have already been migrated.
Dashboards
(Release 3). This project is used to migrate Dashboards and related records from one Service Now Instance to another. If your dashboard contains report type widgets you should migrate the reports first using the Precision Bridge Reports Migration template.
Field Service Management
(Release 2). This project is used to migrate Field Service Work Orders and related records from one Service Now Instance to another. This project includes an optional offset to the Work Order number as part of the migration. If no offset is required, simply set this to '0' on the Variables tab of the execution settings.
GRC
Configuration Data
(Release 1). This Template Migrates Configuration Records related to GRC Modules from one instance to another.
Assessment and Metric Config
(Release 1). This Project migrates assessment and metric configuration from one instance to another.
Entities
(Release 1). This Project migrates Entity Types and their related entities from one ServiceNow instance to another.
Authority Documents
(Release 1). This Project migrates Authority Documents and their related citations from one ServiceNow instance to another.
Control Objectives & Controls
(Release 1). This Project migrates Control Objectives and their related child control objectives (to a depth of 2) and related controls from one instance
Policies
(Release 1). This Project migrates Policies and their related records including policy exceptions other than those related to a specific issue.
Risk Framework
(Release 1). This template migrates GRC Risk Frameworks from one ServiceNow instance to another.
Indicators & Indicator Templates
(Release 1). This Project migrates Indicators and Indicator Templates and their related results and supporting data from one instance to another. This includes related indicator tasks.
Risk Events
(Release 1). This template migrates GRC Risk Events from one ServiceNow instance to another.
Issues
(Release 1). This template migrates GRC Issues from one ServiceNow instance to another.
Risk Response Tasks
(Release 1). This template migrates GRC Risk Response Tasks from one ServiceNow instance to another.
Assessment Data
(Release 1). This template migrates GRC Assessment Instance from one ServiceNow instance to another.
HR Application
HR Cases Global to Scoped (Full)
(Release 28). Full migration of HR Cases, HR tasks and related records (including Workflow) from the legacy HRSM application to the latest HRSD scoped application shipped with Jakarta or later Instance. You must upgrade your Instance to Jakarta or later and activate the Human Resources Scoped App: Core plug in before using this template. Both source and target Instance must be the same. This is the Full version of the HR Migration project which has not been certified by Service Now. It includes everything in the certified version with the addition of workflow. This project must be run using a System Administrator account. If you want to run the certified version, select the Store version of this template.
HR Scoped Application
(Release 4). This project is used to migrate the HR Scoped application data from one Service Now Instance to another. It should be run AFTER the migration of any dependent data, in particular data in the disabled reference mapping tables at the start of the table mapping list.
Incident and Problem Management
Incidents
(Release 1). This template supports migration of incidents and related data (including Workflow) from one Instance to another. The project should be run AFTER the migration of any referenced foundation data, in particular the Organization, CMDB and the Workflow Definitions. Migration of Workflow Definitions is critical for the migration of workflow context migration to work correctly in this project.
Problems
(Release 1). This template supports migration of Problems and related data (including Workflow) from one Instance to another. The project can be run more than once if necessary if the source instance is still in use. During the initial migration, all records are created as new, then for subsequent migrations, existing records are updated and records created since the previous migration are created as new.
Strategic Portfolio Management (SPM)
Portfolios
(Release 4). This project is used to migrate Portfolios and related records from one Service Now Instance to another.
Program
(Release 3). This project is used to migrate Programs and related records from one Service Now Instance to another.
Projects
(Release 3). This project is used to migrate ServiceNow Projects and related records from one Service Now Instance to another.
Demands
(Release 3). This project is used to migrate Demand and related records from one Service Now Instance to another.
ITSM -> CSM
Incidents to CSM
(Release 1). This Project is used to create CSM records from Incident records. SLA Definition records for Case will be created as a part of this project which will be a copy of Incident SLA definition records. Condition fields in these records will have to be manually updated to reflect the fields in Case. This mapping can be disabled if the SLA Definition records already exist for Case with the same name as that on Incident.
Service Requests to CSM
(Release 1). This project is used to create CSM records from Service Request records.
Knowledge
(Release 4). This project is used to migrate knowledge records from one Service Now Instance to another. It should be run AFTER the migration of any referenced foundation data, in particular the Organization and CMDB data. It assumes that all organizational data and cmdb records have matching sys-ids on source and target which should be the case if ITSM Bridge is used to migrate these.
Notifications
(Release 3). This project is used to migrate Notifications and related records from one Service Now Instance to another. This project should be run AFTER the migration of any referenced data, in particular the Organization (users and groups).
Organization
(Release 12). This project is used to migrate Organizational data from one Service Now Instance to another. Schedules, Vendor Types, Companies, Locations, Cost Centres, Departments, Groups, Users, Buildings, User Roles, Group Members, Group Rules, Skills, User Skills, Stockroom Types and Stockrooms are included in this project.
To restrict migrations to a specific company, after selecting the Execute menu option, enter the company name and set Single Company to TRUE. To migrate all records, set Single Company to FALSE and Company Name to ALL.
Note that User passwords cannot be migrated and must be reset on the target environment.
Reports
(Release 2). This project is used to migrate Reports and related records from one Service Now Instance to another.
Resources
(Release 4). This project is used to migrate Resources and related records from one Service Now Instance to another.
SDLC
(Release 4). This project is used to migrate SDLC and related records from one Service Now Instance to another.
Service Portal
(Release 1). This project is used to migrate named service portal, pages and widgets from one Service Now Instance to another.
The following project variables must be set:
- Service Portal Title. The title of the Service Portal to be migrated.
- Page Prefix. The name prefix that all pages to be migrated have (see note below)
- The Name of up to 10 Widgets (not existing on the target) that are to be migrated as part of the
Service Portal. All unrequired widget parameters should be left NULL
- The Title of a Service Portal Documentation record that should be migrated (NULL if none).
Please read the further notes associated with this record in the Precision Bridge software.
Service Request Management
Service and Product Catalogs
(Release 10). Migration of Service and Product Catalogs from one Service Now Instance to another. It is recommended that this project be run using the migration method Import Set (Scripted) with business rules turned OFF and Migrate SysIDs set to Yes. Migrating without these options could invalidate the migration of reference fields.
Service Requests
(Release 1). Migration of Service Requests, Items and related data (Including Workflows) from one Service Now Instance to another.
SLA Definitions
(Release 2). This project is used to migrate SLA definitions from one Service Now Instance to another. It is safe to ignore the key mapping warning related to reference mappings during execution.
SPM
Demands
(Release 3). This project is used to migrate Demand and related records from one ServiceNow instance to another.
Portfolios
(Release 4). This project is used to migrate Portfolios and related records from one ServiceNow instance to another.
Programs
(Release 3). This project is used to migrate Programs and related records from one ServiceNow instance to another.
Projects
(Release 3). This project is used to migrate ServiceNow Projects and related records from one ServiceNow instance to another.
Social Data
(Release 2). This project is used to migrate social data records from one Service Now Instance to another.
System Tables
(Release 4). This project is used to migrate System Table records from one Service Now Instance to another. In general, if the record already exists, it is not updated. It should be run BEFORE the migration of any other projects.
Table Migration
Table and Fields - Custom
(Release 3). This project is used to migrate global custom table and field definitions from one Service Now Instance to another. This project combines the Part 1 and Part 2 table and field migration projects, and should ONLY be used if the field truncation issue does not occur on the target server. Please read the further notes in the Precision Bridge software.
Tables and Fields - Full Table
(Release 1). This project is used to migrate custom and otb table and field definitions from one Service Now Instance to another. Note that this template should be used with caution when migrating OTB tables, it will insert or update ALL fields regardless of whether they are OTB or not. or in an application scope. If you want to migrate only customisations (identified with u_ prefix), use the S2S Custom Table and Field Migration Template instead.
Forms and UI
(Release 3). This project follows from Table and Field Migration and will migrate the UI objects relating to the tables that were migrated. Migrated forms and UI objects from one server to another for a specific set of tables. Note that these actions are not easily undone, so ensure a backup of the target server is in place before migrating to a production server.
Rotated & Extended Tables
(Release 1). This project is used to migrate table rotation configuration and extended/rotated table definitions from one Instance to another.
Before running the project, check the following
- The target table should NOT have table rotation applied already. If it does, executing this project may
interfere with the existing table rotation.
- The target table should be empty initially. If this is not the case, existing records will remain in the
un-extended table, possibly with create dates that do not match with the valid from and to dates in the
table rotation schedule. This can mean that these records do not appear correctly in searches by create date.
Task Boards
(Release 2). This project is used to migrate Task Boards and related records from one Service Now Instance to another. This project includes migration of visual task boards, task board lanes, private tasks, task board cards, task board card history, and board labels.
Templates
(Release 5). This project is used to migrate Templates from one Service Now Instance to another. This project includes migration of templates but not any related items. To migrate related items, use the corresponding migration template.
Time Worked and Timesheets
(Release 4). This project is used to migrate Time Worked and Time Sheets from one Service Now Instance to another. This project includes migration of Time sheets, Time Cards, Time Worked, and related Journal Entries but not the related items for any of these. To migrate related items, use the corresponding migration template.
Workflow Definitions
(Release 9). This project is used to migrate Workflow Definition data from one Service Now Instance to another.
Note that only published workflows are migrated and result in a new checked out version on the target
instance. This is to avoid updating any live workflows. A manual step is required to publish migrated
workflow definitions.
To update a workflow, first delete the definition from the target then re-run the workflow definition
migration.
You must migrate users and groups first since these may be referenced in workflow activity variables.
Other Templates
CSM
(Release 8). This template is used to migrate all CSM Data including accounts contacts and cases from one Service Now Instance to another. It used more reference mappings than the projects in the Customer Service Management Folder.
It should be run AFTER the migration of any referenced foundation data, in particular the Organization
and CMDB. If you want to migrate the contextual workflow, you must first migrate the Workflow Definitions using the Workflow Definition template.
Incidents
(Release 11). This template supports the migration of selected incidents and related records from one Service Now Instance to another. It uses more reference mappings than the project in the Incident and Problem Management folder.
Note that if you are migrating from an older ServiceNow platform using the old Incident state model to a newer platform (Helsinki or later), then you should use the S2S Incidents State Model Conversion
migration template instead.
The new Incident State model includes the On-Hold status and related On Hold Reason field.
Incidents State Model Conversion
(Release 3). This template is used to migrate Incidents and related records from a ServiceNow Instance using the old Incident State model (pre-Helsinki) to the new Incident state model (Helsinki and later versions). Note that if you have upgraded from a pre-Helsinki release then you will still have the old state model.
Change Requests
(Release 6). This project is used to migrate Change Requests and related records from one Service Now Instance to another. It uses more reference mappings than the project in the Change Management Folder. If your source instance is Istanbul or earlier or has been upgraded from a pre-Jakarta release, enable the Change Task Pre-Jakarta source mapping and disable the Change Task mapping. Also enable the IMAC Task Pre-Jakarta Source Mapping and disable the IMAC Task Mapping.
Problems
(Release 7). This template supports the migration of selected problems and related records from one Service Now instance to another. It uses more reference mappings than the other project in the Incident and Problem Management Folder.
Service Requests
(Release 14). This project is used to migrate Service Requests and related records from one Service Now Instance to another. It uses more reference mappings than the project in the Service Request Management Folder. By default this project migrates all requests that were created between the speciied start and end dates and that are either pending approval or approved (excludes all closed requests), and for the specified company (or ALL companies).
HR Cases Global to Scoped (Store)
(Release 15). Migration of HR cases, HR tasks and related records from the legacy HRSM application to the latest HRSD scoped application, shipped with Jakarta or later Instance. You must upgrade your Instance to Jakarta or later.
This is the Store version of the HR Migration template which has been certified by Service Now. If you also want to migrate workflow relating to HR Case records, use the uncertified Full version of this template instead (requires System Administrator account).
This template assumes that the Human Resource: Core scoped application plugin has been activated and that the source and target applications are on the same instance.
Instance Migrator (Store)
(Release 4). This template supports the migration of all Foundation data (including Companies, Locations, Cost centres, Departments, Users, Groups, CI's and Assets) from one Service Now Instance to another.
To restrict migrations to a specific company, after selecting the Execute menu option, enter the company name and set Single Company to TRUE. To migrate all records, set Single Company to FALSE and Company Name to ALL.
Note that User passwords cannot be migrated and must be reset on the target environment.
Comments
0 comments
Please sign in to leave a comment.