Planning your cloud migration is now easier than ever with our new guide

[#1]

Hi Atlassian Community,

My name is Michelle Viegas and I’m a Product Marketing Manager on the Enterprise and Migrations Product Marketing team.

With server end of support now only 9 months away, we want to make it easier for you to evaluate cloud and build a winning migration plan. So, I’m excited to share that we have a new pre-migration assessment to help you navigate the trickiest areas of your migration like apps, security, and user management. In this post, we’ll cover what pre-migration assessments entail and how you can get started.

What you need for a successful assessment

We created a new guide to help you evaluate the top prerequisites and streamline your move to cloud. The guide covers the six key areas for a successful pre-migration assessment:

1. Apps: Your apps, integrations, and customizations are important for team productivity but they’re often the most time-consuming and trickiest parts of building your migration plan. You’ll need to figure out which apps you want to bring with you, find alternatives if they aren’t available, review security requirements, and understand the migration path for each of them.

2. Security and compliance: Moving to cloud won’t change your requirements, but the way you approach them will. When you switch from on-premise to cloud, the responsibility shifts from just you and your team to a shared responsibility between you and Atlassian. And that’s one of the great things about cloud – because we take on some of the administrative work, you'll have more time to focus on other things. But we also understand that your organization may have strict security and compliance requirements and recommend familiarizing yourself with how security is built into the platform and how it can give you the controls you need.

3. User management: You’ll also need to account for your user migration and identity and access management setup in cloud. It’s a good idea to loop in your IT or identity team early on so that you understand your current identity landscape and compliance requirements. That way, you can help your organization stay aligned with its cloud IAM strategy.

4. Performance: Before you make the move, you’ll want to evaluate your data size and shape. The more data you have, the longer and more complex your move may be. We recommend cleaning up your data before you run a test migration for an easier and smoother transition.

5. Cloud product differences: It’s also essential to map out the key differences between your self-managed products and cloud. By creating a list of functionality differences, you’ll be prepared with the information you need to enable your teams once you’ve made the move.

6. Migration team: You’ll have project management support and guidance from your Atlassian cloud migration manager, but you may find that you need additional support in areas like planning your migration, choosing a strategy and tool, or technical support during testing or production migration.

If you assess your migration prerequisites and realize Cloud doesn’t quite meet your requirements yet, we recommend upgrading to Data Center.

How to get started

Ready to assess your migration prerequisites? Head over to our new guide, designed to walk you through all the key considerations for a successful pre-migration assessment. And as always we’re here to help!

[Joseph Chung Yin]

@Michelle Viegas -

Excellent article with the appropriate content for the community members.

Thanks, Joseph

[Brian Hill]

Thanks for this. Would be good to see some more attention on what to do when critical apps that the business relies on are flagged as having low quality migration pathways and how to mitigate those. In practice, I've found that these create considerable complexity in migration planning, rehearsal and execution. There can be significant volumes of data associated with them that are important for the enterprise and application swaps are not always viable. This makes it super important to do rehearsal runs of migration plans in order to help identify the issues that will occur, taking particular note of cycle times and how that will inform production outage planning.