Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Atlassian Insight: Migrating from Server to Cloud


We love Insight, and we're thrilled to hear about Atlassian's purchase.


We have a lot of objects in our Insight Server that we want to import into Cloud. 


However, when we try to do CSV import, Insight Cloud assigns a new key. This isn't feasible for our situation because we're not going to spend the a)time and b)money mailing out new asset tags for physical equipment, or ship/tag/return the physical equipment.

Are there any plans to address this paradigm?




3 answers

1 accepted

0 votes
Answer accepted

Hi Andrew, 

Thanks for highlighting this and I've flagged up Key attribute consistency with the Insight product team. 

We know that with the announcement about Jira Server that many people will be looking to do as you're doing and migrate. As we plan how Insight will be integrated into Jira Service Management we're considering all possible migration paths too. 



Hi @Charlotte Nicolaou , thanks for your response.

I really hope this is something that can be accommodated. 

It goes beyond the inconvenience of having to re-tag assets; many organizations set computer/server hostnames to the asset tag identifier, which has significant operational impacts if that has to be changed. 

@Charlotte Nicolaou

Do we have news for the progress? We need to migrate our Insight to Jira Cloud.

Like Yevgen Lasman likes this
1 vote
Kat Marketplace Partner Nov 15, 2020

As Insight is now an Atlassian product I am going to move this question to the "Migrations" home in hope that it will be seen by people who can help.

Do you have a server-to-cloud migration guide to follow for the Insight - Asset Management add-on?

Like # people like this
Dylan Atlassian Team Jun 10, 2021

Hi @Andrey Suray we don't have a tool to help move data from Server to Cloud at this point. The suggested workaround is as follows:

  1. Export objects to CSV from “Insight - Asset Management app” (this has to be done at an object type level)
  2. In the new feature, create schema and create references, statuses & roles
  3. Import CSV/s of object data via import tab in schema configuration
  4. Create Insight custom fields (to replace Assets custom fields)
  5. Setup Jira automation rules (to replace post-functions and Insight object automation rules)
  6. Update values of Insight custom fields to include values of Assets fields (i.e. use bulk editing)

We're looking at how we can make steps 1-3 easier by provide export/import of asset schema easier. Please feel free to contact our Migration Support team if you need further help. 

Like # people like this

I'm having trouble with the import steps and understanding the "predefined configuration" part.

Hi, thought it worth adding to this post for anyone else trying to use external system import to bulk update Insight fields during a cloud migration - the CSV field values for Insight custom fields need to be in the following format <WorkspaceID>:<ObjectKey>.


key, summary, insight
SANDBOX-2,this is my summary,dd4fe90e-752d-4103-8dad-abe7fd869b51:3

It isn't immediately clear from any documentation that this is the formatting required, the only thing I could find suggested that Label (Key) or Key should work but it doesn't. Note the : rather than a / which is what a CSV export chucks out at you. 

Like # people like this
Taranjeet Singh Community Leader Mar 02, 2022

Thanks for sharing this tip, @Matt Budnyj ! This is going to be very useful for others looking to migrate Insight fields from Server to Cloud using CSV import.

Wow, there's no good way to migrate Insight objects and preserve linkages?

Dear @Dylan , Is there any progress on the migration pathway for moving Insight Data from server to cloud ? We have an upcoming cloud migration where we need to move 2 Jira projects with extensive Insight usage. Since Insight is now natively available in JSM Premium cloud, will it be possible to have a similar integration possible where we have projects in Jira Software and Insight in JSM ?




Suggest an answer

Log in or Sign up to answer

Atlassian Community Events