nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problems importing Jira Software 6.4 into Jira Cloud

sedwards

All I want to do is get our Jira Server 6.4’s data of Projects and Issues imported into Jira Cloud, that is the end goal.

I will list the steps I have gone through so far to try to get it there and the problems I have run into. I am now stuck and have no other ideas on how to proceed. Any advice would be helpful.

This article has steps on how to migrate from Server to Cloud:
https://confluence.atlassian.com/cloud/migrate-from-jira-server-to-jira-cloud-972349848.html

- Step 3: Back up your Jira Server Database (“Database Backup”)

- Step 4: Back up your Jira Server attachments (“Attachments Backup”)

- Step 5: Import your server into Jira Cloud (“Jira Cloud Restore”)

((Our Jira Server is version 6.4 on a Windows 10 machine))

I did the Database Backup and Attachments Backup, then did the Jira Cloud Restore.

Got this error message:

“JIRA must be version 7.0+ for import so start over and install 7.0 upgrade to .11 then re-export and try again”

So I found where to download Jira 7.0, installed it, rebooted our server…

((Our Jira Server is now upgraded to version 7.0, from version 6.4))

I did the Database Backup and Attachments Backup, then did the Jira Cloud Restore.

When on Jira Cloud, I browse the Projects and the data is all there. I browse the Issues, there are NO ISSUES IMPORTED.

I found this forum post suggesting that you must actually have version 7.6 (not 7.0) to prevent the issue of no issues being imported:

https://confluence.atlassian.com/adminjiracloud/importing-issues-776636788.html

So I found where to download Jira 7.6, installed it, rebooted our server…

((Our Jira Server is now upgraded to version 7.6, from version 7.0))

Localhost:8080 has an error, I view the error logs to find:

No JRE_HOME or JAVA_HOME environment variable is set - attempting to just run 'java' command
'"java"' is not recognized as an internal or external command, operable program or batch file.

Related support issue: https://jira.atlassian.com/browse/JRASERVER-21502

I find that JAVA is not installed on the server. I have to now install JAVA. I find that we need JDK 1.8 which translates to Java SE version 8. I install Java SE 8.

I run the config.bat and can now click “Save” (per support issue instructions in above url).

Now our localhost:8080 Jira server loads and I can get back to the localhost “System” page to backup the Jira Server.

I did the Database Backup (and named it “JiraSystemBackupData_7dot6.zip”) and Attachments Backup, then did the Jira Cloud Restore… and get the error message:

Import error
There was an error importing file JiraSystemBackupData_7dot6.zip. Following issues were reported:
Cannot complete the import because one of the import files contains failed upgrade taskrecords: '73011'. Search the Atlassian Administrator Knowledge Base for instructions on how to fix this, or contact Atlassian Support for help.

I have looked and looked and can not figure out how to fix this “73011” error. So now I’m stuck.

For any Atlassian staff who may read this: So far, this has been a very painful and seemingly unnecessarily difficult process to do what seems like should be such a simple task: export data from server, import data to cloud. It’s just a list of Projects, Issues, and associated users. Why are there so many hoops to jump through?

Accepted answers

Andy Heinzer

Hi,

Sorry to hear about the frustrations here. I can see that you are running an older version of Jira and are wanting to migrate this data into a Cloud site. As you have discovered, our Cloud platform does not support importing directly from backups created from these older unsupported versions of server. We have an expectation that your data will have been updated to the most current version of server available prior to migrating to Cloud. As of today for Jira Server, that is 8.13.0.

In turn it will be necessary to complete at least two upgrades to get your data in a state that will be ready to imported to Cloud. All older versions of Jira need to pass through the upgrade of a Jira 7.0.x version as this was a major change. Once that upgrade is successful, you should then be able to upgrade to the latest 8.13.0 version. It sounds like the 7.0.x upgrade was successful here, but that in the process of trying to go to 7.6.x, you appear to have a failed upgrade task with the id of 73011.

I did some searching on this error and found a few different support cases where this has happened. In those other cases it appears that this happened because Jira attempted to make some SQL command changes to the database that were not supported on the older database versions that were running Jira. In turn we always recommend that when you do an upgrade to Jira that you first check to make sure that you are meeting the Supported Platforms listed for that version. You will notice that this document has a version selector on the top right corner of the page. The 7.6 version of that document might be helpful for this specific case. I recall a few other support cases where we saw this commonly happen on MS SQL 2008 or older databases. The particular upgrade task in question here is trying to use a SQL command that is not possible to execute in that version of SQL. However since that version was deprecated back in 7.2 if memory serves, this only became a problem during upgrades to newer versions where that database was no longer supported.

From this point, I would try using the backup from the 7.0.x version of Jira and then create a new database being sure to select a database type/version that is supported for the version that you want to upgrade to. Postgresql 9.6 is a supported platform for both Jira 7.6.x and 8.13.x. So that is my ideal database candidate to use in my view, but of course you can pick any database type/version from that supported platforms page.

I would recommend trying the following steps:

Fresh install of Jira 8.13.0,
Choose a supported database from supported platforms for 8.13
Setup that database per the appropriate guide found in Connecting Jira applications to a database.
Use the Jira config tool to connect Jira to this new, empty database and save changes
Start Jira (when Jira starts connected to an empty database, it launches the setup wizard)
Before doing anything else, restore your file attachments to the $JIRAHOME/data/ directory. This is important because there are potential upgrade tasks that happen between these major versions upgrades that can rename the attachment filenames Jira stores as flat files. If those files are not in place in the correct directory at the time that upgradetask runs, you could end up with broken attachments in Jira
You can then use the setup wizard and choose the option to 'import existing data' This prompts you to select the XML .zip file which should be copied to the $JIRAHOME/import/ folder.
You might need to apply a valid license at the time of this upgrade in order to continue this import. If needed generate an evaluation Server license for Jira Software/Jira Service Desk from https://my.atlassian.com

This should have the affect of upgrading Jira to 8.13.0 on a supported platform with all your data. Provided this is successful, you can then generate a new XML backup zip file here and use that in the process to import to Cloud.

Please try these steps and let me know if you run into any more problems here. Again, sorry to hear that it feels like a lot of hoops to jump through to get your data into Cloud. But I think these steps are necessary in order to maintain the integrity of your data. A lot of the database structures in Jira have changed significantly since 6.4 and our Cloud platform is not expected to be able to support imports from end of life versions of Jira Server.

Let me know how it goes.

Andy

All comments

Andy Heinzer

Hi,

I would recommend trying the following steps:

Fresh install of Jira 8.13.0,
Choose a supported database from supported platforms for 8.13
Setup that database per the appropriate guide found in Connecting Jira applications to a database.
Use the Jira config tool to connect Jira to this new, empty database and save changes
Start Jira (when Jira starts connected to an empty database, it launches the setup wizard)
Before doing anything else, restore your file attachments to the $JIRAHOME/data/ directory. This is important because there are potential upgrade tasks that happen between these major versions upgrades that can rename the attachment filenames Jira stores as flat files. If those files are not in place in the correct directory at the time that upgradetask runs, you could end up with broken attachments in Jira
You can then use the setup wizard and choose the option to 'import existing data' This prompts you to select the XML .zip file which should be copied to the $JIRAHOME/import/ folder.
You might need to apply a valid license at the time of this upgrade in order to continue this import. If needed generate an evaluation Server license for Jira Software/Jira Service Desk from https://my.atlassian.com

Let me know how it goes.

Andy

sedwards

Thank you for your thorough detailed reply. I have tried following those steps but ended up at the exact same end result: no issues found in Jira Cloud.

I did a fresh install of 8.13 with a fresh clean database (sql 2016)
I imported the data and all projects and issues showed up in Jira Server (yay!) so my local 8.13 jira appears to be working correctly
I backed up the data into a new .zip file from 8.13, and the backup appears to have been successful.
I restored Jira Cloud from the 8.13 .zip backup.
All of the projects imported
None of the issues imported << SAME ISSUE I ran into before that made me think I need to upgrade from 7.0 to 7.6 before backing up local data into .zip to import into cloud

The reason I think none of the issues imported is because if I am at Jira Cloud, and I choose any project to see its "Issues" page, I see "No issues were found matching your search" as the default home page of the issues page. This makes me think there are no filters applied and the default search result is to show all issues, that there are no issues at all.

Assuming that the 8.13 local is a valid database, and the backup is a valid backup, can you think of any reason a successful import could cause issues to be hidden from me if I am logged in as the only administrator user? Is there some funky security settings I'm unaware of? Can't think of any other reason to cause this.

I am open to suggestions on how to try to get the issues to import correctly, or to be able to view them on Jira Cloud.

Thanks

Andy Heinzer

Jira Cloud won't apply secret security settings. But if the Jira Server issues were using Security Schemes, then those would schemes be imported as well by this method, and your Cloud administrator account might not necessarily meet the criteria needed to view those issues. So while it is possible the issues exist in Cloud right now, and you can't see them because of issue security, but that's not really a common scenario.

Also there might be another more common factor here in that this appears in Jira Cloud Free plan where you are trying to do this import into. The Free plans in cloud have a number of limitations as noted in https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-free-jira-cloud-plan/

To avoid that as a potential complicating factor, it might be best to upgrade your Cloud site to an evaluation of the Standard plan, at least temporarily to complete this migration. At least when Jira Cloud is in this standard level, you can make adjustments to project roles, permission schemes, etc that you cannot do when Jira is using the Free plan.

However before you do that, I would want to first confirm that the initial upgrade from Jira 6.4 to 7.0 worked. Such as by confirming that you see those issues in Jira 7.0 and it appears to be working there. If so, then I would also want to confirm that the upgrade to 8.13 worked, and you can see the Jira issues in that version as well, before creating a new backup there to be used in Cloud.

sedwards

I checked the issues and they appear to be working (they exist, I can browse any individually to review all comments and timestamps), after both upgrades: 7.0 and 8.13

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud