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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,463,473
Community Members
 
Community Events
176
Community Groups

Do we need any downtime if we are migrating data from jira server to jira jira cloud ?

Do we need any jira server downtime if we are migrating data from jira server to jira cloud using jira migration assistant?

3 answers

0 votes
Amna Elabbas Atlassian Team Jun 07, 2021

Hi @khushboo_puri ,

To install the JCMA  to the server that doesn't cause downtime.

It is very important to set a staging environment which is an exact replica of your production environment to have a solid estimation on how long the migration will take and the downtime during testing

Also, most customers migrate during the weekend to result minimal impact to the business. 

We recently migrated from server to jira cloud and could not fully shutdown the server instance as a project was used for tracking and addressing customer escalations.

We migrated in two steps--first migrated all projects except the one. And then later we migrated just the one project.

Ultimately all projects had downtime--the one project that was migrated last had the shortest downtime.

In Nic's example above the team/project B had downtime but it was shorter than waiting for the entire onprem instance to move to the cloud.

Our migration was scheduled over a long weekend to minimize disruption.

Phase 3 and Phase 4, in the migration guide, were critical to our success. Can't emphasize enough on the importance following the steps in the guide.

thanks. 

0 votes
Miles B. Atlassian Team Jun 04, 2021

Hi @khushboo_puri - You shouldn't need downtime as long as you're on Jira Server 7.6 or newer, however every migration is different.

For more information, please see our migration guide and Jira Cloud Migration Assistant documentation

It also depends a bit on your intended usage.  Imagine you've got three teams, A, B and C.  You're migrating team B to Cloud only.

You don't want down-time for A or C, so you leave it running, but from the point at which you copy the data out of the Server, until it is fully loaded and ready to use in Cloud, then team B will have to have down-time - changes they make to server after the export starts will be lost, and they can't use Cloud until the import is finished and validated.

Like Lalit Shahani likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events