More and more organizations are deciding that now is the time to make the move to Cloud. With recent improvements to data residency, on top of Cloud’s ability to save customers money & time and improve security & agility, there’s never been a better time to make the switch.
As a Cloud Specialized Atlassian Platinum Solution Partner, we are perfectly situated to help you on your journey to the Cloud. Feel free to get in touch with us for any and all of your migration needs!
Migrating can be a daunting process and there is a lot to take into account before and during the move. However, we’ve put together 7 key pieces of advice that will help make your migration smoother.
Planning is a key feature of all migrations.
Establish a timeline, expected downtime, data validation, and post-migration checks to be executed.
2. App Usage and Features
Not all DC/Server apps are available on the Cloud.
If you use an app that is not available on the Cloud it is essential to access what the app does to find a relevant solution that will be available on the Cloud.
Through our MARS™ Database of 3rd party apps, we are uniquely situated as Atlassian Solution Partners to help you with this.
There will ideally be no more than 30 days between testing and performing the actual migration.
Cloud is continually changing so keeping the testing and actual migration dates close helps to assure everything will run smoothly and no surprises happen.
4. Get the Audience Involved
When moving from DC/Server to Cloud some UI features change–it is therefore imperative to engage your team in this process.
Once the test migration happens make sure your users actually use the Cloud site to perform their everyday activities. Hopefully, this will get them more comfortable with the new platform and further helps with testing the migration. (verify if all integrations, functionalities, and performance are working as expected)
5. Testing the Migration
When performing the test migration, review your cloud site to validate that everything works as expected. (application links, app data, integrations, data creation (projects and issues for Jira and Spaces and pages for Confluence), verify if attachments were migrated correctly and if they can be edited/deleted)
6. Migration Run-Book
Carefully document the test migration steps executed so they can be executed repeatedly on the actual migration.
Take notes on changes detected between your DC/Server instance and your Cloud instance.
This will be useful for training your users during and after the actual migration.