The 6 Phases of a Successful Atlassian Cloud Migration

[#1]

Hello there!

I'm Elena from Communardo Products.

Atlassian recently introduced Atlassian Ascend, signaling that Cloud will become the primary hosting platform for all Atlassian products, eventually replacing Data Center. This change reinforces the importance of preparing for a smooth transition to the Cloud. For many organizations, moving to Cloud involves more than just migrating data. It requires careful planning, testing, and adaptation of workflows and integrations.

In this article, we outline the six key phases of an Atlassian Cloud migration and provide a guide to help you navigate each step successfully.

Why migration planning matters

Migrating Atlassian apps, such as Confluence or Jira, from Data Center to Cloud is a significant step. It impacts not only your technical setup but also your users, processes, and integrations.

Without a structured approach, you risk broken links, missing data, or frustrated teams. That’s why we recommend breaking down the journey into six clear phases.

The migration journey typically follows six main phases:

1. Assessment
2. Planning
3. Preparation
4. Test Migrations
5. Production Migration
6. Post-Migration 

Let’s go through them step by step.

This framework has been proven effective in numerous migration projects with Communardo Products customers. Read about a successful migration.

Phase 1: Assessment

Start by understanding your current environment.

• Inventory all Atlassian products in use.
• Review Marketplace apps and verify their Cloud availability.
• Audit your content: which spaces and pages are active, and which can be archived?
• Identify risks like missing features or critical integrations.

This evaluation guides your migration decisions—what to move and what to leave behind.

Phase 2: Planning

Once you know where you stand, you need a roadmap.

• Decide whether you’ll move everything at once (a big bang approach) or in stages.
• Define the scope: which projects or spaces first, and what gets archived.
• Assign roles: project lead, IT administrators, content owners, and support personnel.
• Develop a communication plan tailored to stakeholders and end-users.
• Prepare for technical aspects, including cloud site setup, SSO, and backups.

A solid plan avoids surprises later.

Phase 3: Preparation

Now clean up and prepare both your old and new environments.

• Archive or delete outdated content.
• Remove unused apps and macros.
• Standardize naming conventions and permissions.
• Check Cloud app availability and install required tools.
• Set up your target Cloud site, including groups, permissions, and test users.

Good preparation reduces errors during migration.

Phase 4: Test Migrations

Before going live, it’s essential to practice.

• Start with a pilot migration of one space or project.
• Validate content, macros, permissions, and attachments.
• Gather feedback from test users.
• Run larger test migrations to simulate real conditions.
• Obtain business approval once all verification is complete.

These test runs highlight problems early and build confidence for go-live.

Phase 5: Production Migration

This is the actual move.

• Choose a migration window with minimal disruption.
• Inform users about possible downtime.
• Run a final sync to capture recent changes.
• Execute the migration using Atlassian’s tools.
• Perform quick checks on access, links, and permissions to ensure everything is in order.
• Clearly communicate the go-live to everyone.

With proper preparation, production migration proceeds smoothly.

Phase 6: Post-Migration

The project doesn’t end once the data is in the Cloud.

• Verify everything with a structured post-migration check.
• Replace unsupported macros and reformat pages where needed.
• Provide support channels and training for users.
• Take advantage of Cloud-only features, such as scheduled publishing or archiving.
• Decommission or archive your old Data Center system.

This phase ensures stability, adoption, and long-term success.

Common Pitfalls to Avoid

When migrating to the Atlassian Cloud, there are several common pitfalls to be aware of.

One frequent issue is unsupported macros, as many macros that work on Data Center may not function in the Cloud; therefore, it’s essential to plan replacements. Another challenge arises from the legacy editor, which can cause formatting issues, requiring manual reformatting of pages to ensure the content appears correctly. Incomplete app migrations are also a risk, as not all app data is automatically transferred to the Cloud, and some apps may require additional configuration or manual intervention. Many teams also underestimate the time needed for a migration, leading to delays and unnecessary pressure. Finally, poor communication with users can create resistance and frustration, so keeping all stakeholders informed throughout the process is essential for a smooth transition.

Key Takeaway

Migrating Atlassian products to Cloud is a journey with six distinct phases: Assessment, Planning, Preparation, Testing, Migration, and Post-Migration.

Approaching the project step by step makes it manageable, reduces risks, and sets your teams up for success.

---

I’d love to hear from you. Share your experiences, insights, or questions about Atlassian Cloud migration in the comments and join the conversation.