Summary

Currently, there is no automated way of migrating data from Assets (previously Insight) Datacenter/Server versions into the Cloud version, the process is mostly manual. This article will detail the necessary steps to migrate your data. 

The following information will not be automatically migrated with your objects:

• References -  these will have to be created manually in your new Assets for Cloud instance, see below.
• Statuses - these will have to be created manually in your new Assets for Cloud instance, see below.
• Roles - these will have to be created manually in your new Assets for Cloud instance, see below.
• Attachments - these will have to be created manually in your new Assets for Cloud instance, see below.
• Assets objects custom field - these will have to be created manually in your new Assets for Cloud instance, see below.
• Links between Jira fields and Assets objects - these will have to be created manually in your new Assets for Cloud instance, see below.
• Automation rules - Automation rules in Assets must be recreated using Automation for Jira.

Unfortunately, object history cannot be migrated from Assets for Server/DC to Assets for Cloud.

Learn more about the differences between Assets for Cloud and Assets for Data Center / Server.

1. Export Objects from Assets Server/Data Center to a CSV file

1. On the Datacenter/Server version, navigate to Assets and select the object schema that will be migrated.
2. For each object type, go to the Bulk Actions (gear) menu and click on Export Objects > Export.
3. Download the files. We'll use them later to import the objects to the Cloud version.

2. Create Schemas, References, Statuses & Roles on the Cloud

Now it's time to replicate your Datacenter/Server configuration on the Cloud. This needs to be done manually. These articles can help with that:

• Create an Object Schema
• Create a Reference
• Add a Status
• Manage Roles with Assets

3. Import the CSV files

Now that you have recreated your configuration on the Cloud, it is time to use your CSV files to import the data by following the steps in the Import a CSV file into Assets article. 

The Prepare your data step can be ignored since we already have the CSV files prepared from the Datacenter/Server export, unless you use Jira User attributes in any object type.

The exported from Datacenter/Server uses emails to identify the users. However, Assets for JSM Cloud uses Account IDs, which are unique identifiers for each Cloud user account.

In this case, you will need to edit your exported CSV files from that object type to use Account IDs. Jira uses a unique identifier for each user account that is called the Account ID.

Follow the steps on the Export Users from a Site article to get a list of users, you'll notice that there is a "User ID" column with the Account ID values. Now, since your .csv file from Server only has the email address of the users, we suggest using the VLOOKUP function in order to correlate the Account ID in the exported users file with the email addresses in the CSV file, so you're able to create a column with the account IDs for the users in the proper order. You could also do this manually, but using something like the VLOOKUP function to automatically do this would certainly be quicker.

4. Migrate attachments

At the moment, it is not possible to export/import attachments from objects, so this process needs to be done manually by downloading the attachments from the Server objects and uploading them to the Cloud objects. Consider voting for the following feature request if you're interested in the implementation of a feature for migrating attachments and avatars.

• JSDCLOUD-10459 - Getting issue details... STATUS  

5. Create the Assets object fields

Follow the steps described in the Set up the Assets field article to recreate your Assets fields on the Cloud.

6. Update values of Assets' custom fields

When you import the objects on the Cloud, the object keys are not imported. This means that the object keys will be different than the ones on Datacenter/Server, so any import of issues on your instance won't update the Assets fields since the import file will be pointing to the old Assets keys. The article linked below details two possible workarounds to help you automate the process of linking your Assets objects with the new keys to the already existing issues that were imported to the cloud:

• Workarounds to automatically link the Assets object to Jira issues

7. Set up Assets automation rules

Set up Jira Assets automation rules (to replace post-functions and Assets object automation rules).