If you’ve decided that it’s time for you to migrate to Cloud you might have already started wondering what is the process for migration.
So here we are to tell you that the process consists of 6 phases. Surprisingly but analysis and planning are those things that take almost all the time, not the migration itself.
Phase 1. Assess
First of all, it’s crucial to learn the difference between Cloud and Server if you want to avoid surprises or a mess in the future.
There are different costs, management, security, features, and so on. You can check the details here - https://support.atlassian.com/migration/docs/compare-atlassian-cloud-and-server/
Also, you need to find out what makes your system unique and suitable for you. Explore your system and analyze what products you have and which versions they are , how many people use each of them, what apps and integrations you have, and why.
Accurate auditing and answering questions like “why your system looks the way it looks?” and “why do you need every element of your system?” will make the next phases easier for you.
If you have resources build a team that will work only on the migration process because this phase is only a beginning.
Phase 2. Plan
It’s time to start planning the migration.
Firstly, using your cloud migration trial, you need to set up your organization and verify your domain. That’s all work for your cloud site for now.
The main goal is dealing with the audit results.
When you have all the gathered information about your system it’s time to cut out unnecessary things. To decrease the complexity, you need to look for everything unimportant you can handle without.
Check these factors:
- Size: do you need the whole your data and number of users;
- Apps: check whether your apps available on Cloud and what is the migration process for them;
- Number of products: the more you have the more complex migration will be;
- Hosting: whether you choose consolidation, federation, or hybrid hosting, it can increase the complexity;
- User management: are you intend to use Atlassian Access.
When you have an understanding of the complexity and you know when you want to have the migration completed, it's time to choose the migration strategy and method.
There are four strategies:
- Optimize and shift
- Lift and shift
- Start fresh
The first two are for systems with lower complexity (fewer than 5000 users and 10 apps), phased strategy is suitable for higher complexity. The strategy name Start fresh speaks for itself – it’s fast, but you need to forget about your old data.
Detailed information about migration methods you can find here - https://support.atlassian.com/migration/docs/compare-cloud-migration-methods/
The result for this phase is a migration plan with deadlines and actions.
Phase 3. Prep
This is the time when every single detail about migration should be discussed and explained to your team. Also, you have to choose when and how you want to inform all people that will be impacted by these changes.
Besides, it’s the time for the last check for your system.
Ensure that your product versions are supported by the migration method you have chosen before.
Clean up your data. Delete all unnecessary data, inactive users, and apps – everything that could affect migration complexity and you can work without.
Review the pre-migration checklist to be sure you are ready for the test migration:
Jira pre-migration checklist - https://support.atlassian.com/migration/docs/jira-pre-migration-checklist/
Confluence pre-migration checklist - https://support.atlassian.com/migration/docs/confluence-pre-migration-checklist/
Do not forget to install those cloud apps you want to test as well.
We do not recommend skipping this phase. Testing takes time but it will save your mind in peace when it comes to the actual migration.
Do a test run using this testing guide - https://support.atlassian.com/migration/docs/test-your-server-to-cloud-migration/
Back up your data and conduct User Acceptance Testing (UAT).
When you are sure that everything is in order, every issue is solved and you are satisfied with the test results you can start choosing your production migration window.
As you had run the test migration you've known how much time your migration takes, so you can choose the date for your migration. Night time or weekends are better to choose – the time when no one is using your server instance or cloud site.
Also, it necessary to inform Atlassian about your migration window two weeks in advance so they can offer you extra support.
Before your migration, you need to take care of users’ tuition. Prepare user guides for your end-users and admins. Make sure that everybody understands that everything will be different after the migration: URLs, the way a user log in, interface.
You may have the sense of users’ questions after UAT. Use them as a base for user manuals and tutorials.
Make sure your team knows when the migration will happen, what the new workflow routine is, who they contact if they run into an issue.
Phase 5. Migration
Set your server to read-only mode to avoid any confusion for your users.
Follow the steps in the runbook you made during the test migration.
Migrate all apps you have defined critical.
Check that your data migrated fully and correctly, and that everything is working and in order.
Notify your users about the new URLs and, if possible, apply a site-wide banner to redirect end-users who use the old URLs.
Phase 6. Launch
Congratulations, you have made it!
Now it’s time to share the good news with your stakeholders and give them the link to your new cloud site.
Review the getting started in cloud documentation https://support.atlassian.com/migration/docs/get-your-users-started-in-cloud-after-migrating/ to mark key points and inform your users.
Also, don’t forget to follow the updates on Cloud Roadmap - https://www.atlassian.com/roadmap/cloud.
If you have any concerns about migration, you’re out of human resources or you need help – contact us to get our consultation.
We will help you with every phase and migrate you to Cloud - https://www.teamlead.ru/display/EN/Contact+Us