Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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).



1 answer

1 accepted

4 votes
Answer accepted
Dave Mathijs Community Leader Jan 04, 2023

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.

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 ?



Dave Mathijs Community Leader Jan 04, 2023

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.

Like Matt Smith likes this

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 



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events