Are you looking to migrate your CMDB to the cloud? Atlassian Jira Service Management provides built-in storage for Assets, but there are differences between importing possibilities on the Server/DC and on Cloud. Recently, a customer asked us to migrate their CMDB with 80 object types and imports from on-premise to cloud. In this article, we’ll share our experience and insights on how we did it.
Importing Assets to Jira Service Management Cloud: Differences from On-Premise
Atlassian Jira Service Management provides built-in storage for Assets (AKA Insight). We were asked by customer to migrate their CMDB with 80 object types and imports from on-premise to the cloud. The CMDB is actualized daily by import from prepared database sources in MS SQL.
There is a difference between importing possibilities on the Server/DC and on the Cloud. The on-premise platform provides built-in importers, the possibility to install importers for many specific sources, and an extensible framework for implementing custom importers. We have also created one for items discovered by Zabbix.
An automated import has to be driven from outside. It should be noted that the Imports REST API is capable of substituting database imports when you are able to prepare JSON files (import definition and data files).
Automating CMDB Import: A Solution for Efficient Data Migration
So for our customer, we have:
- cloned schema structure from on-premise to cloud using the REST API
- generated import definition from existing on-premise imports on Server/DC. We have simply transformed database records defining import sources, e.g. “AO_8542F1_IFJ_IMPORT_SRC_OTA”, “AO_8542F1_IFJ_OBJ_TYPE_ATTR”, “AO_8542F1_IFJ_IMPORT_SRC_OT”, “AO_8542F1_IFJ_OBJ_TYPE”
- provided a Powershell Script encapsulating the import workflow for the given import definition file and directory with JSON files prepared by the customer.
The customer has to only dump their database tables to JSON (a single-liner in PowerShell). And schedule the script.
Don’t hesitate to reach out
With our expertise and experience, we were able to provide our customer with a solution that meets their needs. By cloning the schema structure from on-premise to cloud using REST API, generating an import definition from existing on-premise import on Server/DC, and providing a Powershell Script encapsulating import workflow, we made the migration process seamless. If you’re planning to migrate your CMDB to the cloud, don’t hesitate to reach out to us for assistance.
Our Atlassian solutions