Without creating a new Atlassian Cloud Site, of course, nothing works. Since you can't fly without an airplane, this item is not on our checklist. Nevertheless, an important tip: If you have not yet decided on one of the paid versions (Standard, Premium or Enterprise), you can start by using the free Free Plan. Free Plan stands for the Cloud Trial of the complete Atlassian Software Suite. Although not all features of the paid versions are available in the free Free Plan, everything is available for a solid cloud flight for up to 10 users.
Let's go through our checklist together:
First, you need to verify your company's domains with Atlassian. All you need to do is set a DNS entry for your domain or upload a verification file to your company's web space. Verification allows you to manage all your company's Atlassian accounts in one central location in the administration portal. Here you can also define security policies such as two-factor authentication or SAML single sign-on for specific or all users.
Once the domain has been verified, release it for the registration of new user accounts for your cloud site. If one of your employees logs in using an email address with an approved domain, they automatically gain access to your company's cloud instance. This saves a lot of time for your IT department, as not every user has to be added individually or manually.
Now set a date for the migration and announce it in your legacy system. It is advisable to inform users about the migration at least four weeks in advance. This allows your employees to reschedule important project dates in good time.
The period leading up to the final migration is a good time to carry out a test migration. In this way, you can identify potential blockers at an early stage and eliminate them before the final migration. Data generated during the test migration is overwritten each time it is imported. This prevents damage during the iterative test.
This step is small, but extremely important! If stakeholders are still working with the old system during the start of the migration, a gap opens up between the data sets. If you allow this to happen, manual rework will be necessary in the new system, which is extremely time-consuming. In addition, there is always the risk that the data status is not congruent despite all the efforts.
You should therefore clearly communicate the date on which the old system will be write-protected and stakeholders will only be able to pull data, but no longer save it, using various channels (announcement in the old system, circular email, etc.). Only when this step has been completed and you are sure that a consistent data status has been established do you take your starting position.
Then you are ready for take-off! You can find out how to proceed with the migration in our white paper Atlassian Cloud Migration. Of course, I am also happy to answer any detailed questions you may have. Simply send your request using the contact form below.
Do you want to migrate to the Atlassian Cloud? We will be happy to help you.