Hey everyone, I’m in a bit of a pickle with our Jira setup. We’re trying to move from one server to another, but it’s not going smoothly. Our current setup is running Jira 6.4.3, and we want to upgrade to version 7.12 on the new server.
When we try to import the data, we keep hitting a wall. The error message says something like ‘The xml data you’re trying to import is too old for this version of Jira to handle.’
Has anyone else run into this problem before? I’m wondering if there’s a way to bridge this gap between versions or if we need to do some kind of step-by-step upgrade process.
Any tips or tricks would be super helpful. We’re kind of stuck and not sure what to try next. Thanks in advance for any advice!
I’ve dealt with similar issues during Jira migrations. One approach that worked for us was using Atlassian’s database migration tool. It’s designed to handle these large version jumps more smoothly than the XML import method.
First, you’ll need to upgrade your current instance to the latest 6.x version (I believe it’s 6.4.14). Then use the database migration tool to move to 7.12 on the new server. This method preserves all your data and customizations while avoiding the XML compatibility issues.
It’s a bit more involved than a simple export/import, but it’s more reliable for big version leaps. Make sure to thoroughly test everything post-migration, especially any custom workflows or plugins you might be using. Good luck with the upgrade!
hey mate, been there done that. ur gonna need to do a staged upgrade. start with upgrading ur current server to like 7.0, then export. import that into the new server running 7.0, then upgrade to 7.12. bit of a pain but it works. good luck!
I’ve encountered this issue before during a large-scale Jira migration. One effective strategy is to perform an incremental upgrade. Start by upgrading your current 6.4.3 instance to the latest 6.x version available. Then, export your data and import it into a fresh 7.0 installation on your new server. Once that’s successful, proceed with upgrading to 7.12.
This approach minimizes compatibility issues and allows for easier troubleshooting at each stage. Remember to backup your data before each step and thoroughly test functionality after each upgrade. It’s time-consuming but significantly reduces the risk of data loss or corruption during the migration process.
Additionally, consult Atlassian’s official documentation for specific upgrade paths and any known issues for your particular versions. They often provide detailed guides for these complex upgrades.