5.2.1 Approach to data migration

The approach to data migration from Ops I verification environment to actual environment is as follows.


(Table) Approach to data migration from Ops I verification environment to actual environment

Item Approach to data migration
1
  • Files in Git repository
 Files registered in Git on Ops I can be migrated using the git command. For details, see "Data migration of files in Git repository".

(Note)
A Git client must be installed in the local host environment.
2
  • User and customer settings
  • Repository settings
  • Authentication information for secret management
  • Automation AWX settings
  • IT Service Management (ITSM) settings
 No migration capabilities are available for definitions configured from Ops I UI, API, and ITSM. Therefore, they need to be reconfigured in the actual environment. This applies to user and customer settings, repository settings, authentication information for secret management, e-mail notification settings, and settings for e-mail notifications and creating tickets using e-mails, which often differ between the verification and actual environments.
3
  • Non-user-defined data such as execution history
 Non-user-defined data such as execution history cannot be migrated.