You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
Migration from Atlassian Server to Cloud is the talk of the town! But if the mere thought of migrating to the Cloud gives you sleepless nights, you’re not alone! Many people want to benefit from everything that Cloud offers, but don’t know where to start with the process.
This article, based on a recently held webinar, will guide you on simplifying the Cloud migration process and reducing the risk of data losses by migrating your Jira Server to Cloud in phases. You will also learn why you should migrate to the Cloud in the first place and other possible migration strategies.
Only interested in a specific part? Jump to specific topics in the video via the chapters below:
Interested in a deeper dive for your team? Book a demo of Backbone Issue Sync for Jira.
Atlassian support for Jira Server is ending in February 2024, and new Jira Server license sales will already be discontinued from February 2023. Consequently, if you’re currently using Jira Server, the best time to start planning and migrating is now!
It takes an average of 9 months to migrate an instance with 5000+ users (≈ 6 months for 1000+ users and ≈ 3 months for more minor instances). This leaves you with just enough time to plan and execute a well-planned Jira Cloud migration.
So, why should you move to Cloud? Below are some key benefits of using the Cloud based on a survey of Atlassian customers.
Reduced costs: The Cloud removes a lot of hidden costs in comparison to the on-premise Jira instances, such as maintenance, change management, and security.
Peace of mind: Updates are taken care of automatically.
Speed & accessibility: Better performance and easier access to data.
Employee satisfaction: Better UI and features mean happier employees.
There are different migration strategies when migrating from Server to Cloud, each with its own benefits and downsides.
The more popular ones include:
1) Start Fresh
2) Lift and Shift
3) Optimize and Shift
4) Phased Strategy
We will only discuss the Phased Migration strategy in this blog. If you’re interested in learning more about other strategies, you can read the complete blog here or watch the chapter titled “Migration Strategy” in the webinar video above.
The “Phased Migration” or “Migration in Phases” strategy allows you to divide the migration process into phases as per your requirements. For example, you can migrate project by project or any other scheme.
Allows flexibility and customization in migration strategy.
Allows gathering of iterative feedback along each phase, with can improve the process for the upcoming phases.
Reduces the risk of data losses or a significant problem during the migration.
Reduces single downtimes for the involved instances.
Users can be onboarded gradually, affording them more time to get used to the new system.
Careful planning for the phases is required.
Working in two environments at once can lead to confusion and misalignment.
Configurations on Cloud and Server might drift apart during this process.
Most of the problems during the phased migration strategy can be circumvented using Backbone Issue Sync for Jira!
Backbone allows you to sync Jira issues across instances seamlessly. By syncing issues from Cloud to Server and vice versa, changes made on either instance can be kept up-to-date in real-time. This makes it easier to plan and migrate projects dependent on one another.
Furthermore, Backbone’s functionality allows users to keep working on one system while the tool handles synchronizing issues on the instances. This means that the risk of misalignment between teams and data loss across instances is minimized.
When actually performing the phased migration, we recommend a few practical steps.
Freeze the server-side project so that no data is lost and no changes are made during the migration.
Perform migration of the project using Atlassian’s Jira Cloud Migration Assistant (JCMA).
Let your users know that the project has been migrated, and work should be done on the Cloud now. Ideally, you should set up a banner on that project for better visibility and internal communication.
Keep the frozen Server project in sync with the migrated Cloud project using Backbone Issue Sync for Jira. This allows your users to stay on only the Cloud project while Backbone synchronizes the changes made to the Server, which keeps both instances in sync without needing manual updating.
Thankfully, it is still not too late for you to migrate to Jira Cloud! Although moving to the Cloud sounds daunting, it offers many advantages, including the latest updates and apps, better collaboration, and lower costs.
In addition, you can use the phased migration strategy to circumvent the risks and complexities of Cloud migration. And with the help of Backbone Issue Sync for Jira, you can ensure your journey to the Cloud is smooth and incident free!
If you are interested in learning more about how Backbone can help in your phased migration to Jira Cloud, check out the page linked below or sign up for a free demo.
Use Backbone To Migrate to Jira Cloud