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; } } }

Jira Server to Cloud Migration - Migration errors

Ratko

Hi,

I'm trying to migrate JIRA Standalone Server to Cloud and Jira Server to Cloud Migration Assistant report me those odd errors, but nothing as real error.
I'm trying to migrate one project only, with 3 active users.
It give me warn about user limit, again strange, because only 3 users are active on Standalone JIRA.
Those "We couldn’t check for ..." failed checks are also very odd, as not showed as errors

Also, "We found some errors while preparing your data for migration" but where I can see those errors?

I can't raise a ticket on Support as we're trying to spin up Free plan for start

Any idea? Thanks in advance.

Accepted answers

Ratko

Final update

- Had to enable the dark feature:
com.atlassian.jira.migration.skip.preflight.check.export.errors
- Able to run migration even Data preparaion check was grayed (and blocker)
- My project with 611 issues - transfered to cloud, can see all listed and project is created
- All users are migrated, all groups migrated

Thanks guys for your effort to help me

All comments

Benjamin_tmh9yg

Hi @Ratko ,

Migrated several times from server to cloud but with Paid plans and I haven't ran into these issues. It could possibly be that you are on a free plan and that's the reason for this issue.

Do note that the migration tool doesn't just migrate Active users. It also migrate inactive users. In order to make sure you are below the limit, the Inactive should be deleted till you are below the user cap of 10(I think??)

-Ben

Trudy P Claspill

There is a downward pointing arrow to the right of each message. Click that to see if any additional information is available.

Ratko

Hm, but that is only warning for users, it not stop me to run migration. I'll remove users after import on Cloud.
Other undefined check results are problem here. See gray icons on screenshots.

Ratko

Nope, every single of them shows this same message about unexpected error...

Ratko

Also, I've selected only users assigned to project, and there is less than 10 users (both active and inactive)

Benjamin_tmh9yg

you can remove the users after migration but it might be the issue for not being able to run the rest of user checks.

Do you also have the same error for the data preparation?

-Ben

Trudy P Claspill

Do you have the latest version of the migration assistant installed?

What is the version of Jira on the source system?

Do you have a non-expired license on your source system?

If you are working with a licensed version that is within the parameters of supported versions for the version of the Migration Assistant you are using, I would suggest that you contact Atlassian Support directly.

https://support.atlassian.com/contact/#/

Ratko

- Migration Assistant is latest (1.74)

- JIRA Software v8.22.6

- Licence on source expired 2 weeks ago, we started to switch to Cloud.

Tried to raise ticket on Support, but not allow me, as we have Free JIRA Cloud plan atm. So support point me to try Community

Ratko

So, as suggested by @Benjamin and @Trudy P Claspill I've cleaned up users on JIRA Server, and now there is only 9 remain (3 active, 6 inactive) - that cleanup was pain as user can not be deleted until he have comments on issues, so I had to update comments authors directly in database.
And new migration now report only Data Preparation problem with again 'Unexpected error...'
However, even I have 9 users only in total, again there is Warn icon for Users and groups section Is that some bug?
So, wait product owner to get me new trial SEN so I can try with active non-expired license on JIRA Server.

Ratko

So...
Received new Free Trial license, activated on server, attempted Migration - and nothing new...
Same as above image - still complain about users (total 9), and still "Unexpected error" for data preparation.

And still - not possible to contact support directly, as our cloud instance is on free plan

I'm open for suggestions @Trudy P Claspill @Benjamin if you have any

Benjamin_tmh9yg

@Ratko ,

Not much options since not on any paid plans or services.

What you can do at this point is try to export and import by CSV. It does have limitations.

Review the documentation below:

https://support.atlassian.com/migration/docs/cloud-migration-methods-for-jira/

-Ben

Ratko

Hm, CSV import is last resort, but checking that exported file manual is overkill after as per above article.
No matter of free/paid plan I'd expect such serious application to at least show me what is error during migration checks so I can try to fix it.
We ran a standalone for a years... but now migrating it mostly for archiving/history purposes.
How could I suggest my boss to go to paid cloud plan when such a elementary process like export/import between basically same applications fails at start

Ratko

So... update...
I've upgraded Jira on our server to latest version - 9.3.1 and tried again.
Same problem reported - for Data preparation only.

In logs - I've found this lines repeats a lot during migration check

2022-11-05 22:43:13,663+0100 pool-36-thread-2 INFO ratko 1363x206x1 9z3pp 178.149.209.74,127.0.0.1 /rest/migration/latest/check/plan/f5a51c6b-5896-43e8-b14d-3375fd3c664d [c.a.j.m.preflight.reports.PreMigrationReportsService] Unable to generate pre-migration reports. Report export outcome is missing from preflight check for executionId : 0161a72cd7294393006d299544cdf987a72d30fb
2022-11-05 22:43:13,663+0100 pool-36-thread-1 WARN ratko 1363x206x1 9z3pp 178.149.209.74,127.0.0.1 /rest/migration/latest/check/plan/f5a51c6b-5896-43e8-b14d-3375fd3c664d [c.a.j.migration.preflight.AsyncCheckExecutor] Preflight Check ProjectErrorReport failed.
com.querydsl.core.QueryException: Caught MySQLSyntaxErrorException for select `AO_D9132D_ISSUE_SOURCE`.`ID`, `AO_D9132D_ISSUE_SOURCE`.`CONVERSION_FACTOR`, `AO_D9132D_ISSUE_SOURCE`.`PLAN_ID`, `AO_D9132D_ISSUE_SOURCE`.`SOURCE_TYPE`, `AO_D9132D_ISSUE_SOURCE`.`SOURCE_VALUE` from `AO_D9132D_ISSUE_SOURCE` `AO_D9132D_ISSUE_SOURCE` where `AO_D9132D_ISSUE_SOURCE`.`SOURCE_VALUE` is null or length(`AO_D9132D_ISSUE_SOURCE`.`SOURCE_VALUE`) = 0 or `AO_D9132D_ISSUE_SOURCE`.`SOURCE_TYPE` = 'Project' and not `AO_D9132D_ISSUE_SOURCE`.`SOURCE_VALUE` in (select cast(`PROJECT`.`ID` as char) from `project` `PROJECT`) or `AO_D9132D_ISSUE_SOURCE`.`SOURCE_TYPE` = 'Filter' and not `AO_D9132D_ISSUE_SOURCE`.`SOURCE_VALUE` in (select cast(`SEARCHREQUEST`.`ID` as char) from `searchrequest` `SEARCHREQUEST`) or `AO_D9132D_ISSUE_SOURCE`.`SOURCE_TYPE` = 'Board' and not `AO_D9132D_ISSUE_SOURCE`.`SOURCE_VALUE` in ('2', '3', '4', '5')

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'jira.AO_D9132D_ISSUE_SOURCE' doesn't exist

I've did a search, and turns out that table (jira.AO_D9132D_ISSUE_SOURCE) belong to Portfolio plans addon, but we don't have that plugin installed? Could be it was installed years ago.
What is strange - why migration check attempting to read tables which belong to not installed plugin/addon?

Ratko

And also, I tried to find it on Addon market, but that plugin doesn't exist - at least I couldn't find it

Portfolio plans
Plugin key: com.atlassian.jpo
Developer: Atlassian
Version: 3.0.0

Ratko

If I just could recreate that table, maybe migration check will pass then

Ratko

And after all - turns out there is actually BUGs in this Migration Assistant
This one looks very similar to one I have.
https://jira.atlassian.com/browse/MIG-1178

Ratko

Thanks guys for your effort to help me

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland