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

Can Jira Service Desk/Portals (on Prem) still function while migration assistant is migrating?

Matt Smith

When migrating Jira Service Desk to cloud using the migration assistant tool, will the the original SD and portals be accessible and useable during the migration?

- Performance degradation?

- Access Issues?

- response times.

(Our servers are scalable and are of a generous specification).

KR,

Matt

Accepted answers

Dave Mathijs

Hi @Matt Smith , you don't want to have Jira "active" while migrating to Cloud via JCMA.

Any changes in issues in projects that are in scope during the migration might result in errors or the migration becoming stuck.

I would advise to avoid this and setting your Server to "read-only" as described in one of the migration steps.

All comments

Dave Mathijs

Hi @Matt Smith , you don't want to have Jira "active" while migrating to Cloud via JCMA.

Any changes in issues in projects that are in scope during the migration might result in errors or the migration becoming stuck.

I would advise to avoid this and setting your Server to "read-only" as described in one of the migration steps.

Matt Smith

Hi @Dave Mathijs , thanks for the answer.

I think the wording of set your server to read only is misleading (unless I am misunderstanding this).

It should be set all user permissions to Read only (using a scheme)?

Is this is case ?

KR,

Matt

Dave Mathijs

Yes, indeed. Unfortunately, there is no simple toggle to set Server read-only.

Also, please note that if the active permission schemes are no longer associated with their respective project(s), they won't be migrated to Cloud!

In my case, I had to create dummy projects and link them to those permission schemes in order to migrate the permission schemes as well.

I wish Atlassian would reconsider this and find a more practical solution.

Matt Smith

Thanks again Dave,

Another Quick question:

As long as there are no interactions with the "prod" (origin) db while the migration happens then this would be as effective as making permissions "read only".

We are thinking to make the URL accessible by the range that Jira cloud would ustilise

Regards,

Matt

Welcome!

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

Quick Links

Find more posts tagged with

server

migration

jira-service-management

migration-customer-care

jira-service-management-server