I am trying to do a Site Import into Cloud because user has one large Service Management product. The current system uses the following products with an on-prem server: Jira Software, Jira Core, Jira Service Desk. There are about 30 Jira Software products and 1 big Service Desk project that is mission critical. The system has an Active Directory connection, with 269 users. There are 28 internal JIRA directory users.
The vast majority of AD Users have never used the system, but there are some AD Users who are active. Essentially, there are 15-20 users total that need to make this migration.
This migration is more complicated than necessary due to Atlassian’s lack of a Jira Service Desk/Management migration tool. Therefore, I am trying the Site Import option to recreate the current site in the cloud.
However, I am stuck during the test migration phase regarding Users. I am following this document, but stuck between a rock and a hard place.
I’ve tried the following with no success:
When I try to do a CMT of only the Users to the Cloud, I need to assign email addresses to abut 12 AD users. It will not allow me to run the migration of users-only without email addresses to the 12 Users. This is a live system and may be possible, but not preferable.
When I try to Site Import, with any option of Merge with existing, Overwrite existing, or “I've migrated user data using the Jira Cloud Migration Assistant “, the import balks with:
“There was an error importing file JIRA_Backups.zip. Following issues were reported:
We have detected users from external directories. Convert your external directory to internal ones on server, take a fresh backup, import again. Learn more.”
Therefore, even when I tell the import to not import User data, it still requires me to convert Users. This is a problem for three reasons:
Ultimately, this is a merge into an existing Cloud instance of Jira Software and Service Desk. I would like to get the current on-prem into the Cloud to test Adapivist’s Project Configurator to import the Service Desk project to the Cloud instance we are merging to for testing. However, I cannot re-create the current on-prem in the Cloud without this User issue addressed.
Is there something I am missing that won’t risk the current on-premise production instance of User and Groups and allow me to move the data into the Cloud? We can adjust the Users and Groups after, there are not many, but I cannot proceed unless I deal with AD now.
Hi,
we're facing the same issue. We have Atlassian Access though, up and running. Error message as mentioned above turns up nevertheless when we try running the import. So far, we couldn't find a solution except very time-consuming ones.
THX, Manja
Following. Migration support advised me to follow this procedure- use custom "special sauce" jcma tool (special support-issued .jar file) to migrate external users to cloud. Then, backup server, then run site import. The problem is, the site import still wants me to convert the external users. I have the same issues relating to this being a live fire production server. I can't just take it down, and I can't just spin up a clone, to convert these users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And here's the answer. Support wants me to delete the lines containing the following. They offered me these commands to run against the entities.xml file, to automate the removal of the lines in question.
Linux:
sed -i '/<User id="/d' entities.xml
sed -i '/<Group id="/d' entities.xml
sed -i '/<Membership id="/d' entities.xml
sed -i '/<GroupAttribute id="/d' entities.xml
MacOS
sed -i '' '/<User id="/d' entities.xml
sed -i '' '/<Group id="/d' entities.xml
sed -i '' '/<Membership id="/d' entities.xml
sed -i '' '/<GroupAttribute id="/d' entities.xml
I'm sure you could use Excel or some other IDE to knock out the entries in question, too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! I'm at the point in the migration to try this out. I'll post my results.
Were you successful?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Success is relative! We had to refine our process a bit because we lost ownership over tickets and items for the internal users who were cut out of the xml. So we cut out only the external users. The internal users came in about perfectly. That problem is solved, now we have to deal with all the other issues. Hopefully I don't have to do this all over again when we have to go to prod.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I ran the above commands, recompress and either get the same "We have detected users from external directories." error. I've double checked the entities.xml file and indeed, all of those entries are gone.
Not sure where to turn at this point. You're more helpful than support and the errors are vague!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having the same problem. Did you find any solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey all - I'm going to prod on a migration shortly, so I will attempt to document my procedure here. How did you all make out?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.