I took the steps from:
The third step is rather vague:
Create an XML backup of the issue data and compress the attachments.
Since the zip does contain the XML files.
And then I get this error:
There was an error importing file 2016-Dec-20--1245.zip: "There was an error parsing the entities.xml file: An invalid XML character (Unicode: 0xb) was found in the CDATA section.". Please try again or choose a different file.
How can I correct this? I want to migrate from JIRA Server to JIRA cloud.
The zip of the attachments is used in the next step, in the Import to JIRA Cloud section.
The error you are seeing is not uncommon, it's because databases aren't all quite equal. You can fix it and retry the upload with https://confluence.atlassian.com/jira/removing-invalid-characters-from-xml-backups-12079.html
Also experiencing this, and the workaround fails. After running the .jar cleaner I get:
There was an error importing file import-20170124.zip: "The file import-20170124.zip doesn't contain any valid import data.". Please try again or choose a different file.
A diff of the entities.xml file indicates all special characters (like emoji) have been replaced with ��, and file sizes are basically the same (old=259553002 bytes, new=259553202).
I'm looking for the replacement point which may have invalidated all data... but this is getting pretty involved for a simple server (7.2.6) => cloud migration. Curious to hear if @Rommel Tinoco has any update for his situation.
I had a ticket open with Atlassian support for about a month. Apparently they were seeing errors related to non-unique email addresses for different users, so that might be something to check, although it still didn't work for me after I fixed those in the server export.
After a few more back-and-forth cycles with support I gave up trying. We ran out of time to spend on migration (higher business priorities) so we decided to just let our server license lapse for a while.
The support ticket never mentioned any other obvious cause. They seemed to think the XML cleaner was working correctly, and at one point they claimed the import worked on their end. I also saw lots of updates to https://jira.atlassian.com/browse/JRA-62240 over that period so hopefully it'll be addressed soon. I'd recommend opening a support ticket to make sure it's logged in their reference count.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot