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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to migrate a single project to a new Jira-software server running later version? Edited

I want to split-off a project on an old Jira server (v6.4.5) and import it to a new server (v8.0.2). I tried using an xml backup file, with the intention of deleting all unwanted projects in the new server instance at some later time, but it says "The xml data you are trying to import is too old to be upgraded by this version of Jira."

It seems the only option left is to dump a csv file using some complex SQL command, which I guess has to be executed directly in the database interpreter psql (we are using PostgreSQL on both source and target servers).

It seems migration from many other tools is supported, but not from old Jira versions!

Is anyone aware of an easier way to do this?

BTW - both servers are (separate) stand-alone servers running in Linux.

1 answer

0 votes
Petr Vaníček Community Leader Apr 03, 2019


yes, that's version is really too old. Meanwhile there has been several interim versions (where many thinges has been changed) over which you need to upgrade. So best will be install second (temporary) instance with same version 6.4.5 and by this instance to upgrade data set.

Reccomended way is this:

6.4.5 - > 6.4.14 -> 7.0 -> 7.1 -> 7.13 -> 8.0.2

After than you can use data without any compatibility problem. Maybe you can try to import it after upgrade at least 7.0 or 7.1.

Let me know if it's clear for you.

Thanks a lot Petr - that is very helpful.

I assume the upgrade process is just "import-then-export". I'm not sure why I would need a second instance of 6.4.5 - surely I could start by importing into 6.4.14? Or are you suggesting the extra/temp 6.4.5 instance as an opportunity to do the data pruning that I mentioned?

BTW - one thing I did not say is that my target server only has a 10-person starter licence, as it's for a very small group. So I may not have the ability to create multiple instances at different tool versions. I'll look into it.

Petr Vaníček Community Leader Apr 03, 2019

Upgrade process is usually as you wrote, but between your old and new versions there are two platform releases - so many changes under hood, API, ...etc. From my experience is good practise make upgrade once per quarter of year.

Second instance is like TEST environment.

Yes, you can install on this second one 6.4.14, that could be ok. I hope you will done it without any major issues. Let me know when you will have done it and what will be result.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

4,488 views 5 15
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you