Through a set of simple steps, quickly migrate your ITSM Agent Workspace features including configurations and customizations to Service Operations Workspace for ITSM.
Before you begin
Ensure that the scope is set to Service Operations Workspace Core.
Role required: admin
Procedure
-
Navigate to if you're upgrading from AW 2.0 or higher.
If you're installing the latest migration utility, navigate to .
-
On the Migration from ITSM Agent Workspace to SOW page, perform the following steps.
- Optional:
If required, create a basic authentication configuration with existing or new user credentials by selecting Create basic authentication configurations.
Important:
- This configuration must contain the credentials of the user who is logged in and has the admin role.
- Only after you create the basic authentication configuration, create an update set to record any changes that are made to Service Operations Workspace for ITSM in your non-production instance during the migration. See Create and select an update set as the current set.
-
From the Select a basic auth configuration drop-down, select the required configuration.
-
Select Test the configuration.
-
Review the mentioned guidelines.
-
Select Start migration.
Note: In case your previous migration task is partially complete, you can select Continue migration on this page to resume the migration process.
-
On the Features to migrate from Agent Workspace page, for each feature, select the configurations and customizations to migrate.
Apart from the pre-defined features or application and sub features within the features that correspond to specific tables, you can also configure to add custom tables or multiple tables to
the features for migration from ITSM Agent Workspace to SOW using the ITSM Agent Workspace migration grp tables [sn_sow_migration.itsm_aw_migration_grp_tables] system property.
This includes the tables that you created or modified in ITSM Agent Workspace.
On the Features to migrate from Agent Workspace page, the banner displays a notification message with the link to the system property. You can select the link to access the system property
page. On the system property page, you can modify the json string in the
Value field to add custom tables or multiple tables to the features for migration. When editing the json string, you
must ensure the following points to avoid errors during migration process:
- Maintain the format and structure of the json string as is and ensure that the json string is valid.
- Add multiple or custom tables that correspond to the features such as Incident Management or Change Management.
- Avoid duplicate entry of the same custom table under multiple features except for List and Other features.
- As the List and Other features does not correspond to a specific table, it contains multiple tables from other features or applications in ITSM.
- If you want to run the migration for the custom table in List and Other features, then add the custom table to the existing pre-defined features as well as in
List and Other features section of the json string.
- In case, if any custom table does not correspond to any pre-defined features or application or categories, you can add the custom table in Custom Table Migration section of the json string.
For information about configurations and customizations that can be migrated, see Configurations and customizations that can be migrated from ITSM Agent workspace to SOW for ITSM.
-
Select Next.
-
From the Migration confirmation page, review the selected features and select Confirm the migration.
The migration can be fully or partially successful.
- Full successful migration: All configurations and customizations of selected features are successfully migrated to Service Operations Workspace for ITSM and captured in the specified update sets in the non-production instance.
- Partial migration: All successfully migrated configurations and customizations of selected features are captured in the specified update sets in Service Operations Workspace for ITSM in the non-production instance.
-
Select View migration details to review the migration information.
What to do next
Complete the post-migration tasks for each configuration or customization that you have migrated. For more information, see the following topics.