Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Atlassian Cloud Migration

Cloud migration resources roundup: June 2021

...ustomers receive an estimated 155% ROI and total benefits/savings of $1.8M over three years! Check out the report and the rest of our newest resources below, as well as our tried and true that m...

427 views 2 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you