Atlassian Cloud migration: A step-by-step approach for high-volume Jira environments

Migrating to Atlassian Cloud can significantly improve your team’s efficiency and collaboration. However, the process can be complex and challenging. This article provides a step-by-step guide to help you manage your Atlassian Cloud migration. It focuses on practical strategies and insights that IT professionals and business managers need to ensure a successful transition. After reading this article, you will know how to:

  • Assess your current setup and determine what to migrate;
  • Choose the best cloud migration approach to meet needs;
  • Implement best practices for a smooth migration process;
  • Engage users and stakeholders effectively to minimize resistance;
  • Identify and address common challenges that arise during the transition;
  • Select the most optimal staff and resources for the migration.

With these actionable insights, you will be ready to handle the migration process efficiently. You can confidently minimize disruptions and maximize your business’s benefits from Atlassian Cloud migration.

Atlassian Cloud migration overview

We will start with the most critical aspects of the migration process. These include:

  • The answer to why consider Atlassian Cloud in the first place,
  • An explanation of how the Cloud migration benefits companies,
  • An analysis of the migrated components (and what to omit).

Knowing these will help you navigate through the migration process with confidence and maximize the efficiency of your new Atlassian Cloud instance.

What actions you can take to optimize your Cloud instance

The Atlassian Cloud migration provides an excellent opportunity to improve your instance. You can take a few steps to ensure your new Cloud environment is free from disruptions and clutter that might be hiding in your current system. Here’s what you can do.

1. Thorough assessment

During migration, you can conduct a comprehensive assessment of your current systems. This includes plugins and custom solutions. A detailed evaluation helps identify potential issues early on. It ensures all your necessary components are compatible with the cloud environment. You can also improve your system before migration.

2. User Acceptance Testing

This is a critical phase in the migration process. It also allows end-users to validate that the migrated system meets their needs. This provides added value to the assessment – users have a say in how the system works. If you play your cards right, you can achieve higher user satisfaction with the new system.

Deviniti Insights

The emphasis on User Acceptance Testing (UAT) highlights the importance of involving end-users early in the migration process. IT teams should prioritize gathering feedback from users to ensure that the new system aligns with their needs and expectations. This engagement can significantly enhance adoption rates post-migration.

3. Instance restructuring

If your assessment indicates the need for changes, migration is your best option for implementing them. For example, you can redesign user management, and introduce new customizations. Other cases include providing new collaboration tools or feedback mechanisms.

4. Data cleanup

The migration process provides an excellent opportunity to clean up your existing data. Decide what data is essential for migration and what can be archived or discarded. This will lead you to build a more stable cloud environment. With only relevant resources, you can count on improved system performance.

Which system components the cloud migration includes

When planning a migration to Atlassian Cloud, you should know which system components will be migrated. This section will show you what typically gets transferred to the cloud environment. It will also point out what may be left behind.

Components typically migrated

  • User accounts and permissions. These ensure continuity of access and functionality within the Atlassian ecosystem. They include roles assigned to users across different products like Jira and Confluence.
  • Workflows and configurations. Custom settings that dictate how teams operate within Atlassian tools. This ensures that the operational processes remain intact post-migration.
  • Projects and issues. These also include tasks and subtasks. Having them transferred allows teams to continue their work without interruption.
  • Attachments and files. Documents attached to issues or pages in Jira and Confluence. They are vital for maintaining context and reference for ongoing projects.
  • Marketplace apps. Many of these can be migrated; however. You should verify compatibility with the cloud version of Atlassian products. Some apps may have different functionalities or may not be available at all.
Deviniti Insights

The migration process is not merely a technical transition. It also offers a strategic opportunity to reassess and optimize existing workflows. Experts should conduct a thorough evaluation of current practices. Their goal is identifying inefficiencies and areas for improvement. This proactive approach can lead to enhanced operational efficiency in the new cloud environment.

Components not migrated

  • Inactive or unused data. No longer relevant data is often left behind. This helps streamline the new environment and reduces clutter.
  • Custom plugins. Custom plugins developed for on-premise versions may not be cloud-supported. Evaluate your reliance on these plugins and seek cloud-compatible alternatives if necessary.
  • Historical data. You might not want to migrate such data to reduce overhead in your cloud instance. Instead, you can archive it for compliance or reference purposes outside your cloud.
  • Hosting-specific configurations. Leave out any configurations specific to Atlassian DC or (rarely) Atlassian Server without a direct counterpart in the cloud. This includes certain network settings or integrations typical for other hosting options.

Why it’s important to have a migration plan

A well-defined migration plan can support you with a smooth transition to Atlassian Cloud. It also addresses key considerations that can significantly impact the outcome. Examine the elements below and discover how a thorough migration plan simplifies the entire process.

Not omitting crucial steps

Ensure that you don’t overlook any steps when transitioning to Atlassian Cloud. This will help you minimize risks and disruptions. Key steps are provided below.

  1. Preparation and testing. Conduct test migrations to identify and address issues before the final rollout, ensuring smooth execution.
  2. System assessment. Evaluate current systems to determine what needs to migrate, adapt, or be retired.
  3. Migration strategy. Define the approach – Fresh Start, Lift and Shift, or Phased Migration – based on business needs.
  4. Timelines and execution. Establish clear timelines and execute in phases to reduce downtime and maintain functionality.

Meticulous planning preserves data integrity, reduces downtime, and enhances performance, ensuring a successful migration.

Deviniti Insights

The importance of conducting test migrations cannot be overstated. IT experts should implement multiple test phases to identify technical issues before the final rollout. This proactive testing approach minimizes risks associated with data integrity and operational disruptions, ensuring a smoother transition for all users.

Better resource allocation

Optimize resource allocation by effectively assigning tasks, managing timelines, and focusing resources where needed. You will need to remember the following points.

  1. Understand the migration scope. Identify critical tasks such as data cleanup, user management, and testing.
  2. Assign roles. Designate key personnel for each phase to prevent overlaps and ensure accountability.
  3. Anticipate challenges. Identify risks early and allocate resources to address potential issues.
  4. Focus on efficiency. Streamline efforts to improve resource efficiency. Ensure your teams can concentrate on core business activities.

Minimizing risks

Minimize risks during your Atlassian Cloud migration by proactively addressing potential pitfalls. See below how to do it.

  1. Identify risks. Recognize potential challenges early to prevent data integrity and operational disruptions.
  2. Testing beforehand. Conduct test migrations to resolve technical issues in advance. Reduce the likelihood of impact on end-users.
  3. Establish roles and responsibilities. Assign team members specific tasks to eliminate confusion. Ensure you have covered all critical areas.
  4. Introduce contingency planning. Prepare for risks with proactive resource allocation and backup plans.

Ensure compliance

Ensure your migration process and new Atlassian instance are in line with regulatory requirements. Reduce legal risks and protect your company’s organizational reputation. You already know about Atlassian Cloud’s certifications (e.g., GDPR, ISO/IEC 27001, SOC2). Here’s what else you can do.

  1. Conduct pre-migration audits. Assess current data handling practices. Identify compliance gaps, and address them before migration.
  2. Engage key stakeholders. Define roles and expectations. Ensure all team members understand their compliance responsibilities.
  3. Mitigate risks. Proactively address potential data breaches and non-compliance risks. Include thorough planning and monitoring.

Why read this guide?

The guide is quite lengthy, but it covers all three Atlassian Cloud migration approaches in detail. Furthermore, it delivers a few benefits that can support you throughout the entire transition process. They are enlisted below.

Get a migration roadmap

Get a structured migration roadmap. This is crucial for navigating the complexities of transitioning to Atlassian Cloud.

  1. Provide comprehensive planning. Manage risks and maximize benefits with a clear migration strategy.
  2. Take practical steps. Follow detailed guidance for planning and executing your transition effectively.
  3. Acquire necessary support. Define key roles and responsibilities to streamline migration phases.
  4. Increase efficiency. Refine or create plans that ensure a smooth, successful transition to Atlassian Cloud.
There are several important steps that need to be carried out in the pre-migration stage. A thorough assessment of current plugins and custom solutions is crucial before migrating to identify any compatibility issues and plan for necessary adjustments. Creating a detailed runbook before migration not only helps coordinate efforts but also provides a roadmap for troubleshooting potential obstacles during the transition.
A quotation by Szymon Szerewicz, Atlassian DevOps Team Leader at Deviniti.

Understand best practices

Learn about best practices that are critical for a smooth and successful migration.

  1. Implement proven strategies. Get insights from industry experts. This includes Deviniti, a leader in Atlassian Cloud migrations.
  2. Build a structured plan. Follow a detailed migration plan. Streamline the process and avoid disruptions.
  3. Discover tools. Learn about the Cloud Migration Assistant (CMA) and other specialized tools to simplify the transition.
  4. Follow comprehensive frameworks. Deviniti’s migration roadmap offers step-by-step strategies, including handling key phases and risks.
Further reading

Find out more about Atlassian’s top migration tool:

Get a bargaining tool for other stakeholders

Secure stakeholder buy-in for the success of your Atlassian Cloud migration.

  1. Present clear benefits. Highlight advantages such as enhanced security, streamlined maintenance, and access to new features.
  2. Leverage expert insights. Use data and strategies from expert companies like Deviniti to build a compelling case.
  3. Address stakeholder concerns. Prepare to answer questions with concrete examples of proven strategies.
  4. Promote structured planning. Emphasize how a well-researched migration plan minimizes risks and maximizes outcomes.

Would you like Deviniti to draw up a Cloud migration roadmap for you?

As an Atlassian Cloud Specialized Partner, we are prepared to handle all aspects of your cloud migration and deal with any issues that appear on the way.
Read more

Atlassian Cloud migration approaches – your options

Your main goal in the Atlassian Cloud migration is selecting the right migration approach. This is crucial for ensuring a successful and efficient process. Each strategy offers unique advantages and is suited to different business needs and circumstances. There are three general approaches to Atlassian Cloud Migration:

  • Fresh Start,
  • Lift-and-Shift,
  • Phased Migration.

We will discuss them one by one below.

The Fresh Start approach

The Fresh Start migration strategy involves leaving behind existing data on the old instance and migrating only essential users and workflows to the Atlassian Cloud. This approach can allow you to begin anew. You can optimize your cloud environment without the burden of unnecessary data.

Usage

The Fresh Start strategy is best suited for situations where:

  • You want to streamline your operations and eliminate obsolete data.
  • You need to redefine workflows and processes in the cloud environment.
  • Your current instance is cluttered with redundant data that does not need to be migrated.
  • You are setting up new teams or projects that require a clean slate without the complexities of legacy data.

Main benefits

  • Streamline your environment. Reduce clutter by migrating only essential data. Get a more efficient cloud setup.
  • Optimize workflows. Redefine and improve workflows – tailor them to your current business needs.
  • Reduce migration complexity. Simplify the migration process by focusing on necessary components. Minimize technical challenges.
  • Implement faster. Deploy your environment quickly since there is less data to transfer compared to other approaches.

Potential challenges

  • Data loss risk. You may leave behind important historical data without a careful assessment before migration.
  • Change management. Employees may need time to adapt to new workflows and processes. This can lead to temporary productivity decreases.
  • Initial setup effort. You need extra resources for thorough planning and setup of new configurations in the cloud.

Best practices

  • Conduct a data audit. Before migration, perform a comprehensive audit to determine what is essential for the new environment.
  • Engage stakeholders early. Involve key stakeholders in discussions about workflow redesign and data requirements. Ensure they are aligned with business goals.
  • Use migration tools. Apply solutions like the Cloud Migration Assistant (CMA) for efficient user migration and workflow setup.
  • Test thoroughly. Implement a test migration phase to identify potential issues. Ensure that workflows function as intended in the new environment.

Sample scenario

Consider this scenario:

  • A company has decided to migrate to Atlassian Cloud. Their existing instance has accumulated years of unused projects and outdated user accounts.
  • The company conducts a thorough audit of its current data. It identifies only active projects and essential users for migration.
  • This approach allows it to set up a streamlined Jira Cloud instance tailored to their current operational needs.
When considering migration strategies, organizations can choose between Fresh Start, Lift-and-Shift, or Phased Migration approaches, each tailored to different needs and circumstances. The Lift-and-Shift strategy, which is the most popular among our clients, allows businesses to migrate essential data while archiving less critical information, ensuring a streamlined transition.

Katarzyna Dorosz-Żurkowska

Head of Atlassian Services at Deviniti
A quotation by Katarzyna Dorosz-Żurkowska, Head of Atlassian Services at Deviniti.

The Lift-and-Shift approach

The Lift-and-Shift migration strategy involves transferring an existing instance of Atlassian products to the Cloud with minimal changes. This approach typically entails migrating all data, users, and configurations in a single downtime window. This allows you to maintain your current setup.

Usage

The Lift-and-Shift strategy is best suited for situations where:

  • You need to migrate quickly without extensive reconfiguration of your existing systems.
  • You would like to retain all historical data and workflows in the cloud environment.
  • You have a large number of users (typically over 10,000) and significant data volumes (more than three million issues/attachments per app). These call for a comprehensive migration approach.
  • You are looking to move to the cloud while minimizing operational disruptions.

Main benefits

  • Migrate fast. Get a quicker transition to the cloud by moving all components at once. Reduce downtime compared to other strategies.
  • Retain your data. Preserve all historical data and workflows. Providing continuity for users accustomed to existing processes.
  • Simplify the process. Reduce the complexity of migration by avoiding extensive redesigns or data audits. Make it easier for teams to adapt post-migration.
  • Immediately access cloud features. Take advantage of Atlassian Cloud features from day one. This includes automatic updates and enhanced security features.

Potential challenges

  • Downtime risks. The need for a single migration window can lead to extended downtime if issues arise during the process.
  • Legacy data issues. Migrating all existing data may include unnecessary information. This can potentially clutter your new environment.
  • Limited optimization. You may miss the opportunity to streamline workflows or improve processes. After all, you are only replicating your existing setup without changes.

Best practices

  • Conduct a pre-migration audit. Assess your current instance usage. Identify any redundant data or configurations that can be left behind during migration.
  • Utilize migration tools. Apply tools such as the Cloud Migration Assistant (CMA). Support the transfer to ensure data integrity.
  • Plan for testing. Implement a test migration phase. Find potential issues before executing the final migration. Eliminate risks associated with downtime.
  • Engage stakeholders early. Involve key stakeholders in the planning process. Ensure alignment on expectations. Minimize possible disruptions during the migration.

Sample scenario

Consider this scenario:

  • A company has been operating its Jira instance on-premise for several years. It has over 15,000 users and millions of issues stored in its database.
  • The company decides to migrate to Atlassian Cloud using the Lift and Shift strategy. First, it conducts a pre-migration audit. Thanks to this, it identifies some outdated projects but chooses to migrate everything for continuity.
  • They utilize the Cloud Migration Assistant to facilitate the process. It also conducts a test migration beforehand.
  • The migration takes one week and is completed successfully. Afterward, the company can immediately utilize new cloud features. It also helps retain their historical data and workflows.

The Phased Migration approach

The Phased Migration strategy involves breaking down the migration process into smaller, manageable phases. This approach allows you to migrate your data and users incrementally. This often means transitioning individual servers, business units, or smaller teams.

Usage

Phased Migration is best suited for situations where:

  • You have a complex environment with multiple applications or services. They need to be migrated separately.
  • You must minimize downtime by migrating components in stages. You need to ensure continuous operations.
  • You want to test your cloud environment’s performance with smaller groups before a full rollout.
  • You are managing many users and vast data. A single migration window is impractical for you.

Main benefits

  • Reduced downtime. Migrating in phases allows you to maintain operational continuity. It also minimizes disruptions during the transition.
  • Incremental testing. Each phase allows for thorough testing of configurations and workflows. It means you can identify and resolve issues before moving on to the next phase.
  • Flexibility. You can adapt your migration strategy based on feedback and performance from earlier phases. In other words, you can gradually optimize the process.
  • Easier change management. Phased migrations allow your teams to adjust gradually to new systems and processes. Consequently, you can reduce resistance to change.

Potential challenges

  • Complex coordination. Managing multiple phases requires careful planning and coordination among your teams. This can complicate the migration process.
  • Possible inconsistencies. Different phases may lead to discrepancies in data or user experiences. You must exercise caution when managing them.
  • Extended migration timeline. Phased migrations reduce immediate downtime. However, you need to establish a prolonged migration timeline compared to other strategies.

Best practices

  • Develop a detailed migration plan. Outline each phase clearly. Include timelines, responsibilities, and objectives. Ensure all stakeholders are aligned.
  • Engage stakeholders throughout. Keep communication open with all affected teams. Manage expectations and gather feedback during each phase.
  • Test after each phase. Validate functionality and performance before proceeding to the next phase. Ensure a smooth transition.
  • Utilize migration tools. Apply tools like the Cloud Migration Assistant (CMA). Support data transfers and minimize errors.

Sample scenario

Consider this scenario:

  • A company has a large on-premise Jira instance that supports multiple departments with various workflows. To migrate efficiently to Atlassian Cloud, it chooses a Phased Migration strategy.
  • It starts by migrating the marketing department first as a pilot phase. This allows them to test the new environment’s capabilities. They can also gather user feedback before proceeding with the finance and operations departments in the following phases.
  • By using this approach, the company successfully transitions each department without significant downtime or disruption to their ongoing projects.
Comparison of cloud migration approaches

Aspect	Similarities across all approaches	Differences by approach
Planning and strategy	
All approaches require clear goals, objectives, and success metrics.
Assessing the current infrastructure and workload dependencies is critical.
Choosing a suitable cloud provider and deployment model is a shared step.
Rollback plans are essential for risk mitigation.
Fresh Start: Focuses on designing a new cloud-native architecture.
Phased: Requires detailed prioritization of workloads and phase segmentation.
Lift-and-Shift: Minimal changes, focusing on replicating existing infrastructure in the cloud.
Security and compliance	
Establishing cloud governance frameworks (IAM policies, encryption, compliance checks) is common.
Continuous monitoring for security threats is critical.
Compliance with regulations such as GDPR or HIPAA is necessary.
Fresh Start: Emphasizes building security into new cloud-native solutions.
Phased: Security considerations evolve as phases progress and integrate with remaining on-premises systems.
Lift-and-Shift: Mirrors existing security configurations in the cloud with limited re-architecting.
Data migration	
Requires tools for secure data transfer (e.g., AWS DataSync, Azure Migrate).
Data integrity validation is critical in all cases.
Incremental migration techniques minimize downtime.
Fresh Start: Focuses on data transformation for compatibility with new architectures.
Phased: Splits data migration into stages aligned with workload prioritization.
Lift-and-Shift: Moves data as-is with minimal transformation.
Testing	
Functionality, performance, and integration testing are standard practices.
Testing is necessary to validate the success of the migration at every stage.
Fresh Start: Comprehensive testing of newly built applications and integrations.
Phased: Tests specific phases for partial functionality while maintaining operational continuity.
Lift-and-Shift: Primarily ensures functionality matches the original system with minimal performance optimization.
Post-migration activities	
Monitoring and optimizing cloud resources post-migration is a shared priority.
Implementing backups and disaster recovery plans is essential.
Teams need training to manage and operate in the new cloud environment.
Fresh Start: Iterates and refines new cloud-native designs post-migration.
Phased: Focuses on completing remaining phases and addressing any integration challenges.
Lift-and-Shift: Focuses on stabilizing migrated workloads and shutting down legacy systems.

The Fresh Start Cloud migration process – a step-by-step guide

The Fresh Start migration involves setting up a new cloud instance and designing a modern, cloud-native architecture from scratch. The aim here is to optimize workflows, scalability, and security. This approach requires rethinking legacy systems, redesigning data storage and workflows, and implementing robust training and change management strategies.

Fresh Start Cloud migration steps

This detailed guide provides an actionable roadmap for executing a Fresh Start cloud migration. It can help you with catering to both IT professionals and business stakeholders.

Define goals and objectives

  • Determine business needs. Understand specific business drivers (e.g., scalability for future growth, cost optimization, global expansion, enhanced performance). Engage stakeholders across departments to align technical requirements with business priorities.
  • Set metrics for success. Establish KPIs such as reduced downtime, faster application response times, cost reduction, or improved system reliability. Include technical and business-oriented metrics (e.g., user satisfaction scores, time-to-market for new features).
  • Create a vision statement. Outline the long-term vision for the cloud migration and how it aligns with business goals.

Assess current environment

  • Evaluate legacy systems. Conduct an inventory of applications, workloads, and infrastructure. Consider using dependency mapping tools (e.g., Dynatrace, SolarWinds) to find interdependencies. Identify underperforming or redundant systems to decommission.
  • Document workflows and dependencies. Record the current workflow, integration points, and user interactions. Highlight any bottlenecks or inefficiencies that can be addressed during migration.
  • Analyze technical debt. Quantify existing technical debt and assess which areas require immediate modernization.
Further reading

Learn more about the tools:

Choose a cloud plan

  • Consider the best option for you. Standard is suitable for small teams with basic needs. Premium is ideal for growing teams with advanced needs like unlimited storage and admin insights. Enterprise is best for large organizations with enhanced data residency and compliance needs.
  • Plan for regional data residency. Ensure compliance with geographic regulations when considering data residency.
  • Verify app compatibility. Ensure Marketplace apps and integrations of critical importance to you are available in the cloud.
One approach I’ve worked on extensively is the Fresh Start strategy. This is ideal for companies looking to modernize and leave behind outdated systems. A big part of this strategy is the data evaluation and cleanup phase. This ensures you’re only migrating data that matters, making the process smoother and the end result more efficient.

I once worked with a mid-sized tech company that had years of accumulated Jira projects. Many of these were outdated, duplicates, or simply irrelevant, and they were dragging down system performance.

We started by bringing together project managers, IT admins, and department heads to decide what data was essential. Using JQL and Confluence analytics, we identified inactive projects and low-engagement pages. We also brought in a third-party tool to tag and categorize data more efficiently. Through this, we found dozens of workflows and permission schemes that didn’t reflect how the company operated anymore.

After a thorough cleanup, we reduced the data volume by almost 40%. This sped up the migration, cut costs, and set the stage for a better-performing cloud environment. Post-migration, their Jira Cloud instance ran noticeably faster, and their team found it much easier to navigate and use.

Aljay Ambos

Head of Marketing and AI Expert at Twixify
A quote by Aljay Ambos, Head of Marketing and AI Expert at Twixify.

Plan the new cloud architecture

  • Apply Atlassian Cloud-native solutions. Focus on configuring features like Jira automation, Confluence integrations, and Bitbucket pipelines to align with cloud-native workflows.
  • Select compatible tools and services. Implement tools like Atlassian Guard for centralized user management and Cloud Migration Assistants for streamlined data transfer.
  • Ensure resilience and performance. Use global data residency options and disaster recovery mechanisms provided by Atlassian Cloud to ensure reliability. Include performance monitoring tools (e.g., Atlassian Analytics or Datadog) to meet operational expectations.
  • Optimize processes. Plan for automation features and rules to reduce manual intervention. Apply Infrastructure as Code (IaC) practices via Atlassian-supported APIs or third-party DevOps tools. Maintain consistency and secure updates.
Further reading

Find out more about useful tools:

Set up the cloud environment

  • Establish organization and permissions. Configure your site-level administration. Clearly define environments (e.g., production vs. sandbox). Use project roles, groups, and permissions to manage access and responsibilities.
  • Configure networking and connectivity. Atlassian Cloud eliminates the need for managing VPNs or VPCs. Still, you need to ensure secure connectivity by setting up Atlassian Guard for centralized user authentication. Configure custom domain names for services like Jira and Confluence if required.
  • Implement security best practices. Use multi-factor authentication (MFA) via Atlassian Guard and enforce role-based access control (RBAC). Enable encryption for data at rest and in transit. Configure logging and monitoring using Atlassian’s built-in tools or integrations with third-party security platforms.
Deviniti Insights

Atlassian’s cloud-first approach means that over 90% of new features are developed exclusively for the cloud. It means that migrating businesses will benefit from the latest innovations without the need for manual upgrades.

Migrate data

  • Prepare data. Export and clean up necessary data using Atlassian tools or third-party utilities. Ensure the exported data is formatted correctly. It must be ready for import into the new Atlassian Cloud instance.
  • Transition data. Test small batches of data first to validate that it imports correctly into Atlassian Cloud. Post-import and verify the data’s integrity. Resolve any mismatches or errors.
  • Set up data management practices. Atlassian Cloud manages backend storage. However, you should configure space quotas, access permissions, and data retention policies following your company’s requirements. Use tools like Atlassian Guard for managing sensitive data.

Build or deploy applications

  • Develop new applications. Create lightweight, cloud-optimized applications that enhance your Atlassian ecosystem (e.g., custom Jira workflows or Confluence macros)..
  • Reconfigure or replace existing services. Evaluate existing apps, add-ons, and extensions for Atlassian Cloud compatibility. Use the Atlassian Marketplace to find suitable replacements or alternatives.
  • Adopt DevOps practices. Automate application updates or configurations using Atlassian tools (e.g., Bamboo or Bitbucket Pipelines). Set up monitoring through the Atlassian Statuspage or third-party integrations for performance tracking.

Test the cloud environment

  • Validate workflows and features. Perform functional tests to verify the functioning of Jira projects, Confluence spaces, and custom configurations. Test API integrations for third-party tools or custom apps built using Atlassian Forge.
  • Simulate user scenarios. Use Atlassian-supported tools like Jira Performance Tests (JPT) or third-party load testing tools such as Apache JMeter to simulate concurrent users, project updates, and search queries.
  • Conduct end-to-end testing. Conduct end-to-end testing to ensure smooth user experiences. This includes verifying permission schemes, SSO integrations, and issue transition workflows.

Train teams

  • Cloud knowledge transfer. Conduct hands-on workshops and provide certification opportunities for IT teams.
  • Business stakeholder training. Train non-technical stakeholders on cloud cost management and reporting tools.
  • Ongoing support and documentation. Create runbooks, FAQs, and escalation paths for operational issues.

Launch the new environment

  • Go live. Gradually introduce teams to the new environment. Use the Atlassian Sandbox for pilot testing before enabling the full rollout.
  • Monitor and optimize. Use Atlassian Analytics and third-party monitoring tools (e.g., Sentry or New Relic) to track system performance, usage metrics, and user adoption.
  • Iterate. Collect user feedback through surveys, monitor feature adoption, and review performance data to identify improvement areas. Update configurations, workflows, and permissions as business needs evolve.
Further reading

Consider the tools supporting your migration:

Decommission legacy systems

  • Retire obsolete systems. Shut down and securely dispose of hardware and applications no longer in use.
  • Archive data. Implement secure archiving solutions for compliance and historical data access.
  • Document lessons learned. Create post-mortem reports to improve future migrations.

Additional considerations

  • Compliance and governance. Use Atlassian Cloud’s admin controls and audit logs to enforce data governance and monitor activity. Apply Atlassian Guard for centralized user and policy management Ensure compliance with standards such as GDPR, HIPAA, or SOC 2. Align policies with FinOps principles to balance governance with cost control.
  • Cost management. Use Atlassian Cloud usage reports to analyze license utilization and track app costs. If necessary, remove unused apps or adjust license tiers. Incorporate budget alerts and reports to prevent.
  • Disaster recovery planning. Configure automated backups using Atlassian tools like Backup Manager for Jira or Confluence. Validate restore processes and conduct regular disaster recovery (DR) drills to confirm that critical data and configurations can be recovered quickly.
Deviniti Insights

Migration offers a critical moment for your company to establish data governance practices. Once you conduct a comprehensive data audit, you can identify essential data. Furthermore, you can discover how it should be managed moving forward. This ensures compliance with regulations and enhances data integrity in the cloud environment.

The company I worked for was very worried about the safety of their data during their Fresh Start move to Atlassian Cloud. To fix these issues, we set up strong encryption, restricted who could see private information, and checked the security often. And to make sure they were following the rules, they taught their staff the best ways to keep data safe. This approach not only guaranteed data security but also ensured that every company policy was implemented as advised.

Furthermore, the outcome of the relocation is much different depending on the extra effort one does to safeguard objects and engage the appropriate experts. Following these guidelines made moving for the business safe and simple. This scenario truly emphasizes the need of advance planning in order to maintain private information protected.

Benjamin Tom

Editor and Utility Specialist at Electricity Monster
A quotation by Benjamin Tom, Editor and Utility Specialist at Electricity Monster.

Risks unique to Fresh Start cloud migration

An entirely new working environment after the Fresh Start migration entails issues with design and adaptation. Insufficient design in the pre-migration phase and insufficient training in the post-migration phase can seriously impact your productivity later.

1. Inadequate initial design and architecture

Risk. When you build a cloud environment from scratch, you need to design firm architecture. Otherwise, there’s a risk of poor initial architecture design. This, in turn, could lead to scalability issues, performance bottlenecks, or inefficient resource use.

Why it’s unique. Fresh Start migrations require rethinking and redesigning entire applications or infrastructures. This increases the complexity of the design phase.

Impact. You might suffer long-term performance degradation and higher costs. You also might need to go through the effort of significant rework post-migration.

Solution. There are several ways to minimize these risks:

  • Involve cloud architects early on to ensure the architecture design is optimized for scalability, security, and cost-efficiency.
  • Use cloud best practices such as microservices, containerization, and serverless computing to build a cloud-native environment.
  • Leverage cloud design patterns and proven reference architectures specific to your business needs.

Action. Regularly review design with stakeholders (e.g., developers, security, and business units). Ensure alignment with business goals.

2. Data loss during redesign

Risk. During the rebuild of systems and data structures, there’s a risk of losing critical data due to errors in mapping or transferring.

Why it’s unique. When you need to redesign data storage and workflows from scratch, it increases the complexity of data migration. This makes the instance prone to errors.

Impact. You might have to deal with loss of essential business data, compliance violations, or costly remediation efforts.

Solution. There are several steps you can take:

  • Create a comprehensive data migration plan. Include detailed mapping and validation steps.
  • Implement data backups and snapshots before migrating. Ensure the integrity of legacy data.
  • Use automated tools for data migration. Make sure they validate data integrity during the transfer.

Action. Implement robust error-checking and verification processes. This will allow you to detect and resolve any inconsistencies or data loss early.

3. Longer time to realize benefits

Risk. Cloud migration requires extensive redesign and development. Due to this, your team may not realize the benefits of cloud migration (such as cost savings or scalability) as quickly.

Why it’s unique. The Fresh Start strategy often involves re-architecting from the ground up. This means you might have to add significant time to the migration process.

Impact. You might have to go through delayed ROI or prolonged disruption to business operations. Not to mention potential missed opportunities for early cloud advantages.

Solution. There are some ideas you can implement:

  • Break the migration into smaller, manageable milestones with clear objectives. Deliver incremental value as you progress.
  • Ensure that cloud solutions are built with the business’ long-term scalability in mind. Don’t worry if the initial phases focus on core functions.

Action. Set up clear, measurable success criteria for each migration phase. Prioritize key business objectives early in the process.

4. High initial costs

Risk. You will need a significant upfront investment in redesigning applications and setting up cloud-native infrastructure.

Why it’s unique. Fresh Start migrations often involve high development and testing costs. After all, you must re-architect applications for the cloud.

Impact. A higher upfront financial burden can impact your budget planning. This might delay your migration project.

Solution. Consider taking these steps:

  • Plan and manage your budget carefully. Focus on high-priority applications and services first to avoid unnecessary over-engineering.
  • Use cloud cost management tools to control spending throughout the migration process.

Action. Opt for cloud-native services that reduce infrastructure overheads. Focus on automation to minimize manual intervention.

Comparison of roles across the cloud migration approaches

Role	Fresh start	Lift-and-shift	Phased
Atlassian Administrator	Designs a new system architecture, optimizing workflows, configurations, and permissions.	Focuses on replicating the current environment with minimal changes.	Manages migration in stages, ensuring consistency across environments during hybrid operation.
Business Analyst	Analyzes existing workflows to optimize and tailor the new environment for future needs.	Minimal involvement to ensure workflows and structures remain the same.	Assists in prioritizing and validating each phase’s workflows, ensuring long-term compatibility and optimization.
Cloud Solution Architect	Designs a completely new cloud architecture, leveraging cloud-native capabilities (e.g., SSO, integrations).	Rarely needed as the architecture is directly replicated from on-premises or legacy cloud.	Plays a key role in ensuring the phased strategy aligns with long-term cloud architecture goals.
Data Fidelity Specialist	Ensures that selected, cleaned, and optimized data is migrated to the new cloud environment.	Ensures exact replication of all historical data, configurations, and dependencies without modification.	Validates data integrity in each phase to prevent inconsistencies or data loss during partial migrations.
Change Management Lead	Manages user adaptation to redesigned workflows, permissions, and system functionality.	Limited role since workflows and user experiences remain largely the same.	Coordinates change management in stages, balancing user adoption with system updates.
Training Lead	Provides extensive training for restructured workflows, permissions, and tools.	Minimal training required; focuses on familiarizing users with the cloud environment.	Offers phased training to align with each migration step, ensuring continuous learning and adaptation.
Replication Specialist	Not relevant; focuses on re-architecting rather than replicating.	Handles direct replication of workflows, configurations, and permissions.	Involved in replicating parts of the system during each phase, ensuring compatibility between environments.
Legacy System SME	Provides historical context for understanding which components are necessary in the new system.	Ensures smooth replication by addressing compatibility or dependency issues in the legacy system.	Involved in identifying dependencies and ensuring phased migration doesn’t disrupt ongoing operations.
Process Optimization Specialist	Redesigns workflows, permissions, and overall system configurations for efficiency and scalability.	Rarely involved, as existing processes are replicated without modification.	Balances short-term replication needs with long-term optimization goals.
QA/Test Engineer	Conducts comprehensive testing of new workflows, data integrity, and integrations.	Validates data consistency and functionality to ensure the new environment mirrors the original.	Performs iterative testing for each phase, ensuring compatibility across hybrid environments.

Unique roles for Fresh Start migration

The Fresh Start migration approach is all about designing the instance from scratch. That’s why it requires personnel capable of building the Cloud architecture, creating workflows, and even training other staff members.

1. Cloud Solution Architect

Responsibilities

  • Designs a new cloud-native architecture. This includes integrations with Atlassian Guard, SSO, custom app configurations, and security frameworks.
  • Focuses on creating scalable, efficient, and modernized systems. Ensures they are tailored to future business needs.

Irrelevance in other strategies

  • In Lift-and-Shift, you replicate the existing architecture without redesign. This eliminates the need for re-architecture.
  • In Phased Migration, architecture adjustments are often incremental and limited to specific phases. You don’t need a full redesign upfront.

2. Process Optimization Specialist

Responsibilities

  • Analyzes legacy workflows and processes. Then designs improved solutions that align with cloud capabilities.
  • Ensures the re-architected system improves efficiency, collaboration, and compliance with business objectives.

Irrelevance in other strategies

  • In Lift-and-Shift, you preserve the original workflows and processes. There’s no need for optimization.
  • In Phased Migration, process improvements occur over time and often as a byproduct of iterative changes. This makes the aforesaid role less distinct.

3. Change Management Lead

Responsibilities

  • Develops and executes strategies to manage user adaptation to the new environment.
  • Oversees communication, stakeholder engagement, and support. Ensure smooth transitions to entirely new workflows and configurations.

Irrelevance in other strategies

  • In Lift-and-Shift, user workflows and experiences remain identical. This minimizes the need for change management.
  • In Phased Migration, change management is less intensive. Users adjust to smaller, iterative changes.
Deviniti Insights

A well-structured change management framework is essential during migration. You should develop a clear communication strategy that outlines the benefits of migration It must also address potential concerns, and provide training resources for users adapting to new workflows. This approach can mitigate resistance to change.

4. Training Lead

Responsibilities

  • Creates and delivers training programs. Helps users and administrators adapt to entirely new systems and configurations.
  • Develops documentation and hands-on training materials tailored to the new environment.

Irrelevance in other strategies

  • In Lift-and-Shift, you need minimal training. The user experience remains largely unchanged.
  • In Phased Migration, training is spread across phases. Existing administrators and support teams also take responsibility for this.

The Lift-and-Shift Cloud migration process – a step-by-step guide

The Lift-and-Shift migration involves moving applications and workloads from on-premises to the cloud with minimal modifications to the architecture. This method lets you transition while maintaining familiarity with their existing setup quickly.

Lift-and-Shift cloud migration steps

The detailed guide below is enhanced with additional insights relevant to both IT professionals and business stakeholders.

Define migration goals

  • Set objectives. Define primary drivers for migration (e.g., faster scaling, hardware refresh avoidance, geographical expansion). Establish business priorities, such as uninterrupted service or immediate cost savings.
  • Identify KPIs. Business KPIs include Cost reduction, uptime improvement, and time-to-market enhancements. IT KPIs include Reduced infrastructure maintenance, stable performance, and minimal latency increases.
  • Communicate goals. Ensure alignment between IT, operations, and executive teams.

Assess existing infrastructure

  • Inventory applications and workloads. Catalog applications, services, and their dependencies. This includes databases and file systems. Catalog all Jira, Confluence, and other Atlassian tools, along with associated add-ons, integrations, and user data.
  • Understand workload requirements. Gather detailed information on the computing, storage, and networking needs. Focus on factors such as user load, peak traffic times, and storage volume.
  • Document existing performance metrics. Record key performance indicators (KPIs) like uptime, response time, and throughput for each tool (Jira, Confluence, etc.). Capture user access patterns and latency requirements to monitor how these metrics compare after migration to Atlassian Cloud.

Choose Atlassian Cloud Plan and resources

  • Select the right Atlassian Cloud plan. Evaluate your company needs to choose between Atlassian’s Standard, Premium, or Enterprise plans. Consider factors such as user limits, advanced admin controls, and data residency requirements. Ensure the plan aligns with your operational needs.
  • Identify supporting resources. Inventory critical apps and integrations from the Atlassian Marketplace. Confirm their compatibility with Atlassian Cloud. Plan for user management. Use Atlassian Guard for SSO, user provisioning, and enhanced security controls. Assess storage and performance requirements. Optimize the setup of your cloud environment.
  • Prepare for networking and compliance. Review and configure data residency settings to meet regulatory requirements. Plan for secure network configurations. Support any hybrid or third-party system interactions during and after the migration.

Plan the migration

  • Prioritize workloads. Start with workloads that are less business-critical or have fewer dependencies.
  • Design a migration timeline. Account for data transfer time, application downtime, and post-migration testing.
  • Establish rollback procedures. Define clear criteria for fallback to on-premises systems in case of failure.
During a "Lift and Shift" Atlassian Cloud migration, we faced performance issues due to excessive custom workflows. By auditing the instance pre-migration, we identified redundant schemes and streamlined configurations using Jira's Workflow Optimization tools.

A dedicated team, including a Cloud Architect, Jira Admin, and Migration Specialist, used Atlassian’s Cloud Migration Assistant for automated data transfer. Post-migration, implementing Confluence for documentation ensured smooth user adoption. This proactive cleanup reduced migration time by 20% and eliminated future performance bottlenecks.

Robin Salvador

CEO and Co-Founder at Caffeine Brothers
A quotation by Robin Salvador, CEO and Co-Founder at Caffeine Brothers.

Set up the cloud environment

  • Create cloud accounts. Set up Atlassian Cloud sites for different environments, such as production, development, and staging. Use separate accounts or workspaces within Atlassian Cloud for each environment.
  • Configure networking. Implement VPN or direct connect configurations to ensure secure communication between your on-premises systems (if they remain in use) and the Atlassian Cloud environment. Verify that firewall rules align with your security policies.
  • Provision compute resources. Pre-allocate resources in Atlassian Cloud based on the existing workload requirements you documented (CPU, memory, storage, etc.). Focus on provisioning the necessary cloud resources such as cloud instances that mirror your on-premises infrastructure.
  • Set up storage. Choose the right cloud storage options that match your existing storage setup (e.g., SSD for fast access or HDD for long-term archival storage). For instance, Atlassian Cloud will use cloud storage (such as S3, or Blob storage) for data backup and storage of Jira and Confluence data. You should configure it to match your required performance levels.

Optimize applications (optional)

  • Prepare for cloud readiness. Ensure that the operating systems running on your on-premise instances (e.g., for Jira, Confluence, Bitbucket) are compatible with the Atlassian Cloud environment. Review your applications for any dependency on hardware-specific configurations.
  • Update configurations. Ensure that network settings, such as IP addresses or domain configurations, are updated to reflect the cloud environment. This includes configuring DNS settings or updating any static IP references.

Execute the data migration

  • Select migration tools. Use Atlassian’s migration tools like Atlassian Cloud Migration Assistant for Jira or Confluence Cloud Migration Assistant to move data to the Atlassian Cloud. If you have highly customized data or integrations, consider third-party migration tools (e.g., CloudEndure, Carbonite). They support efficient data transfer for workloads involving complex datasets.
  • Transfer data. Use secure and reliable data transfer methods, whether it’s through online migration or offline data transfer methods. For Atlassian Cloud migrations, this may involve direct API calls or export/import methods. If your data is too large for an online migration, consider utilizing offline tools like AWS Snowball or Azure Data Box.
  • Verify data integrity. Verify the integrity of your transitioned data. Compare checksums or hashes before and after the migration. This ensures no data corruption occurs during the transfer process.
Further reading

Examine the tools supporting your Cloud transition:

Migrate applications

  • Shut down on-premises applications. Coordinate shutdowns to prevent conflicts or data mismatches during migration.
  • Move applications to the cloud. Use the Atlassian Cloud Migration Assistant to deploy your existing Atlassian applications (e.g., Jira, and Confluence) directly to the Atlassian Cloud.
  • Restart applications in the cloud, ensure that they run smoothly, and confirm that users can log into Atlassian Cloud applications without issues.

Perform testing

  • Validate functionality. Perform tests on core and edge use cases. Ensure that your applications are working correctly.
  • Conduct performance testing. Measure key performance metrics, such as response times, application load times, and throughput, to check whether your applications are performing as expected.
  • Run integration tests. Verify that your Atlassian tools are still able to interact with third-party systems, such as authentication servers (SSO), CI/CD tools, or other software integrations.

Optimize cloud resources

  • Right-size resources. Use Atlassian’s built-in tools or third-party integrations such as AWS Trusted Advisor to analyze cloud resource usage. Ensure ensure you are not over-provisioning cloud services, like compute or storage, post-migration.
  • Enable auto-scaling. Auto-adjust resources like storage or compute power based on demand. Provide a smooth user experience even with variable usage patterns.
  • Monitor usage. Track resource consumption and performance metrics. Quickly detect any bottlenecks or issues related to your new environment.

Transition users

  • Update DNS and endpoints. Update DNS settings to point users to the new cloud-hosted instances. Ensure that all relevant URLs are correctly routed to the new environment. These include Jira, Confluence, and Bitbucket.
  • Deliver user support. Provide clear communication to users about the migration process and any changes to workflows. Offer support through FAQs, training sessions, or documentation.
  • Monitor user feedback. Collect data on user experience to address any issues with cloud performance or functionality. Respond quickly to reported problems and optimize for smoother performance.

Decommission legacy systems

  • Shut down legacy systems. Gradually phase out on-premises infrastructure once cloud systems are stable.
  • Archive data. Ensure compliance by securely storing historical data in low-cost solutions.

Post-migration activities

  • Monitor and optimize. Use Atlassian Cloud’s built-in monitoring features or third-party solutions to track performance, and identify any latency issues or service disruptions. Analyze metrics like uptime, response time, and cloud service performance.
  • Cost management. Regularly assess cloud usage costs and optimize resources accordingly. Consider options like reserved instances or commit to savings plans for better pricing on Atlassian Cloud resources.
  • Implement backups and disaster recovery. Set up and verify backup procedures for your cloud environment. Test your disaster recovery plan to ensure it meets your Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO).
Here’s a detailed insight into the "Lift and Shift" Atlassian Cloud migration strategy and a common challenge businesses face during this process.

The key step is data integrity validation post-migration. How it is done? Teams must make sure that workflows, permissions, and data structures are preserved when moving the current Jira, Confluence, or Bitbucket instances to Atlassian Cloud. This entails doing comparative analyses between the cloud and on-premises versions, utilizing plugins such as Configuration Manager for Jira for more intricate validations and Atlassian's migration helper tools for preliminary diagnoses.

People and tools required include a systems administrator with experience with Atlassian technologies, a migration lead, and QA testers are required for this stage. Atlassian Access is one tool that aids with compliance monitoring.

The challenge and solution include custom plugins compatibility. A customer had problems with proprietary Jira plugins that were incompatible with the cloud environment. The group had to examine how each plugin was used, look for alternatives on the Atlassian Marketplace, and provide unique fixes for important plugins. There were no interruptions thanks to a gradual sandbox testing approach.

Arvind Rongala

CEO at Edstellar
A quotation by Arvind Rongala, CEO at Edstellar.

Additional considerations

  • Start with low-risk workloads. Begin by migrating less critical applications and services to build confidence and validate the migration process.
  • Communicate with stakeholders. Regularly inform key stakeholders (such as IT teams, business units, and leadership) about migration progress and any possible challenges.
  • Take advantage of cloud expertise. Consider engaging with Atlassian or third-party consultants to ensure smooth execution. Their experience can help avoid common pitfalls and ensure best practices are followed.

Risks unique to Lift-and-Shift cloud migration

Moving entire instances to the Cloud as part of Lift-and-Shift is demanding in terms of operations. The migrated system might not perform equally well in the new environment. You need to be aware of possible efficiency risks and transition disruptions.

1. Suboptimal cloud performance

Risk. You may face performance issues when migrating workloads without optimizing them for the cloud. These include latency or resource inefficiency, as the applications aren’t fully designed to handle cloud capabilities.

Why it’s unique. This strategy moves applications as-is without reconfiguring or optimizing them for the cloud environment.

Impact. You may face increased operational costs, poor user experience, and reduced benefits of cloud scalability and flexibility.

Solution. There are several ways for you to handle these issues:

  • Conduct a performance audit of existing systems to understand the most resource-intensive workloads.
  • Set up performance benchmarking tools before and after the migration to track performance gaps.

Action. Consider implementing a post-migration optimization phase. Adjust workloads to run more efficiently in the cloud environment.

2. Increased long-term costs

Risk. Lift-and-Shift may result in higher ongoing costs. Especially if the cloud resources are over-provisioned or poorly optimized for cloud architecture.

Why it’s unique. There’s no re-architecting in the cloud. The migrated workloads may not be efficient in terms of resource allocation and cloud-native features.

Impact. Inefficient use of cloud resources, higher ongoing cloud bills, and missed cost savings.

Solution. You can handle the situation in the following way:

  • Right-size resources (VMs, storage) during the initial setup. Ensure that you are not over-provisioning cloud resources.
  • Implement cost management practices like reserved instances or auto-scaling. Optimize cloud spending.

Action. Continuously monitor usage patterns. Apply cost monitoring tools like AWS Cost Explorer or Azure Cost Management. Adjust resources as necessary.

Further reading

Learn more about cost management tools:

3. Security gaps due to incompatible security frameworks

Risk. Your existing on-premise security mechanisms might not map perfectly to the cloud environment. This may lead to gaps in security posture.

Why it’s unique. Lift and shift migrations carry forward legacy security practices and tools that may not be compatible with the cloud.

Impact. Your system can be exposed to security vulnerabilities, compliance issues, and data breaches.

Solution. Consider these ideas to solve these problems:

  • Conduct a detailed audit of existing on-premises security policies and tools. Map them to cloud-specific security solutions.
  • Engage cloud security experts. Implement cloud-native security practices (e.g., IAM, encryption, threat detection).

Action. Create a comprehensive cloud security plan that integrates with existing security tools. Ensure compliance and secure data throughout the migration.

Unique roles for Lift-and-Shift migration

Since Lift-and-Shift is about transitioning the entire instance, you need personnel to ensure the stability of the moved environment. Your staff should ensure data consistency and proper handling of your legacy systems.

1. Replication Specialist

Responsibilities

  • Manages the direct replication of on-premises systems, workflows, and configurations to the cloud.
  • Ensures fidelity in data transfer, configurations, and dependencies without re-engineering.

Irrelevance in other strategies

  • In Fresh Start, the focus is on redesign rather than replication.
  • In Phased Migration, replication happens incrementally and may involve selective or partial migrations, requiring a broader skillset than pure replication.

2. Data Fidelity Specialist

Responsibilities

  • Ensures complete and accurate migration of historical data, configurations, and relationships.
  • Validates that no data is lost, corrupted, or misaligned during the migration process.

Irrelevance in other strategies

  • In Fresh Start, only selected data is migrated, and historical fidelity is less critical since the focus is on new configurations.
  • In Phased Migration, data validation happens incrementally and is often integrated into broader testing roles.

3. Legacy System SME

Responsibilities

  • Provides deep knowledge of the existing system, resolving any compatibility or dependency issues during the migration.
  • Assists in troubleshooting and aligning the replicated environment with the legacy setup.

Irrelevance in other strategies

  • In Fresh Start, legacy systems are often disregarded or analyzed only for reference purposes.
  • In Phased Migration, the emphasis is on selectively transitioning parts of the legacy system, reducing the need for a full-time SME.
Deviniti Case Study

About the company

 The company has been a customer of Deviniti since 2011. Their instance was highly customized, which negatively impacted performance.

Challenge

 Each upgrade required over 50 man-days of work, primarily for adjusting customizations. It was challenging to determine what was truly necessary and what could be addressed with Marketplace Apps.

Customer decision

 The move to the Cloud was seen as an opportunity for a clean-up. Old projects remained on the Data Center (read-only), while the new environment was planned to be built from scratch.

Project story

 Some projects were still ongoing. After analysis, it became clear that leaving them behind was not feasible, necessitating their migration to the new environment. Deviniti faced the challenge of finding ways to optimize these projects, migrating parts of the old instance, and collaborating with the customer on a daily basis to ensure that the business could maximize the benefits of the Cloud when launching new initiatives.

Benefits

 The migration allowed for the departure of outdated practices. Maintenance efforts are now significantly smaller than in the past, and the migration process served as an opportunity to adjust workflows to meet current needs effectively.

Would you like to get similar benefits from migrating to Atlassian Cloud?

The Lift-and-Shift cloud migration approach is the most popular among our clients. Thanks to this, we are qualified not only to quickly transition your environment. We can also build a new Atlassian Cloud strategy that will improve your workflows and team efficiency.
Read more

The Phased Migration to Cloud process – a step-by-step guide

A phased migration involves moving workloads to the cloud in stages, ensuring minimal disruption to ongoing operations while optimizing resources and addressing challenges incrementally.

Phased Migration to cloud steps

Here’s a detailed guide to executing a phased migration successfully. Following these steps will ensure you will avoid disruptions and increase system efficiency.

Define goals and plan the phases

  • Set objectives. Identify why the migration is being done (e.g., cost reduction, scalability, modernization).
  • Prioritize workloads. Categorize applications and workloads based on complexity, dependencies, and business impact.
  • Design phases. Phase 1 should include low-complexity workloads or non-critical systems. Phase 2 should include medium-complexity workloads with moderate dependencies. Phase 3 should include high-complexity, business-critical workloads.

Assess the existing environment

  • Inventory all assets. Document applications, data, dependencies, and infrastructure.
  • Analyze workloads. Determine compatibility with the cloud and identify candidates for specific transition types. The Lift-and-Shift type features minimal changes to migrate as-is. The Re-platforming types feature moderate changes to optimize for the cloud. The Re-architecting type features significant changes to leverage cloud-native features.
  • Performance baselines. Measure current system performance to compare post-migration results.
One key step in the Phased Migration strategy I’d like to highlight is data segmentation and prioritization – a crucial aspect that can make or break the migration’s success. Phased migrations are often chosen by businesses with complex environments, and segmenting data correctly ensures minimal disruption while aligning the migration with business goals.

The process begins with a detailed audit of existing Jira or Confluence instances, identifying active projects, unused configurations, and redundant data. Teams then prioritize migrating high-value or active projects first, leaving less critical data for subsequent phases. This segmentation allows businesses to test the migrated environment with a smaller, controlled dataset while continuing operations in the legacy system for the remaining users.

A critical challenge we encountered during a phased migration was mapping custom workflows and plugins to their cloud equivalents without breaking functionality. Using Atlassian’s Cloud Migration Assistant and third-party tools like ScriptRunner for Cloud helped automate much of the configuration mapping, saving countless hours of manual adjustments. Clear communication and phased user onboarding were also key to reducing friction during the transition.

Hiren Shah

Founder at Anstrex
A quotation by Hiren Shah, Founder at Anstrex.

Choose a cloud plan and resources

  • Select the right cloud plan. Evaluate Atlassian’s available plans (Standard, Premium, or Enterprise) based on your organization’s needs. Standard is suitable for small teams requiring core features and basic support. Premium is ideal for growing teams that need advanced admin controls, unlimited storage, and enhanced performance SLAs. Enterprise is best for large organizations requiring advanced compliance, data residency options, and priority support.
  • Determine resource requirements. Identify the resources needed to support phased migration activities.
  • Specify user licenses. Allocate licenses for test and production environments as migration progresses.
  • Establish storage capacity. Ensure sufficient storage for incremental data migrations and backups during each phase.
  • Check application compatibility. Verify that Marketplace apps and integrations required for each phase are available in the chosen plan.
  • Verify networking. Plan for secure and reliable connectivity between on-premises systems and the cloud during hybrid phases.

Establish governance and security framework

  • Define policies. Set rules for data governance, compliance, and user access. Clearly outline how data is managed, stored, and shared within the Atlassian Cloud environment. Address industry-specific regulations and provide least-privilege access.
  • Implement Security Best Practices. These include identity and access management (IAM), encryption (at rest and in transit), and continuous threat monitoring and response. For instance, you can Encrypt data at rest using industry-standard protocols like AES-256 or Secure data in transit with TLS (Transport Layer Security).
Deviniti Insights

Securing buy-in from key stakeholders is crucial for successful migration. You should present clear benefits of cloud migration. This includes enhanced security and reduced maintenance burdens. You should also address any concerns stakeholders may have about the transition process.

Build the foundation in the cloud

  • Set up cloud infrastructure. Create networks, storage, compute instances and security configurations.
  • Establish CI/CD Pipelines. Enable continuous integration and deployment for efficient operations.
  • Configure monitoring tools. Use Atlassian’s Opsgenie or other cloud-native tools like AWS CloudWatch or Azure Monitor.
One key step in the Phased strategy is carefully planning and executing a pilot phase. This involves migrating a small but representative segment of your systems or teams first. In one case, I worked with a company transitioning from Jira Server to Jira Cloud. We identified one team that heavily relied on Jira workflows but was smaller in size, making it ideal for a controlled test environment.

During this pilot phase, we ensured all necessary tools and resources were in place, including a detailed project plan and the right support team. This phase allowed us to uncover unexpected compatibility issues, such as integrations with third-party tools, that were not initially apparent. By resolving these issues early, we ensured that the subsequent phases could proceed more smoothly and with fewer disruptions.

By the time we moved on to larger groups, we had refined the process and had more confidence in the migration’s success. In this way, the phased approach helped minimize risk while still allowing for the flexibility to adjust the plan as needed. The entire company benefited from a seamless transition with minimal downtime and reduced user frustration.

Jon Morgan

CEO and Editor-in-Chief at Venture Smarter
A quotation by Jon Morgan, CEO and Editor-in-Chief at Venture Smarter.

1st migration phase: non-critical workloads

  • Select workloads. Choose non-critical or standalone systems that are least likely to disrupt operations. Prioritize workloads that offer quick wins.
  • Migrate data. Use Atlassian’s migration tools, such as the Cloud Migration Assistant, to transfer data. Apply third-party tools like AWS DataSync or Azure Migrate for specific data formats if needed.
  • Test applications. Validate the functionality of migrated applications in the Atlassian Cloud environment. Conduct integration testing to ensure compatibility with existing systems and workflows.
  • Go live. Transition selected users or services to the migrated workload. Provide support for early adopters.
  • Monitor and optimize. Use Atlassian analytics tools (e.g., Jira Insights, Confluence Analytics) and third-party monitoring solutions. Gather feedback from users to identify and handle performance issues or inefficiencies.
Further reading

Read more about the tools supporting your transition:

 

2nd migration phase 2: moderately critical workloads

  • Dependency mapping. Map interconnections across applications. Resolve dependencies identified during the assessment phase to ensure seamless integration in the cloud environment.
  • Refactor applications. Make moderate adjustments to optimize performance in the Atlassian Cloud, such as improving API integrations or adjusting workflows. Prioritize efficiency by aligning refactored applications with cloud-native features.
  • Migrate data. Use Atlassian’s Cloud Migration Assistant for incremental data transfer to minimize disruption. Schedule data migration during low-usage periods to reduce downtime.
  • Test and validate. Perform thorough functional, integration, and load testing to ensure all systems perform as expected. Validate critical business workflows, permissions, and configurations post-migration.
  • Transition users. Gradually onboard users to the new cloud-based system in phases, starting with low-risk groups. Provide tailored training and support.

3rd migration phase: business-critical systems

  • Prepare a detailed rollback plan. Develop contingency measures for critical workloads. Use Atlassian’s Cloud Migration Assistant to configure rollback checkpoints and data snapshots for rapid recovery.
  • Re-architect applications. Redesign applications to benefit from Atlassian Cloud’s native capabilities. Optimize performance by implementing cloud-native practices like caching strategies or improved integration pipelines.
  • Execute data migration. Use tools like Bitbucket Cloud Migration Assistant for source code repositories and Jira Service Management Migration Assistant for service desks. Use staging environments for verification before live deployment.
  • Conduct rigorous testing. Perform comprehensive end-to-end testing, validating workflows, permissions, and integrations critical to business operations. Simulate disaster recovery scenarios to test your system’s resilience.
  • Go live. Transition business-critical systems during planned low-traffic periods. Monitor the system with tools like Atlassian Analytics and Opsgenie for real-time performance tracking.

Monitor, refine, and scale

  • Monitor performance. Use native tools like Atlassian Admin Insights (Premium/Enterprise plans), Opsgenie alerts, or Jira Service Management incident tracking. You can also apply third-party tools like Datadog, CloudWatch, or Azure Monitor.
  • Optimize resources. Apply auto-scaling to handle fluctuating workloads. Implement load balancing to distribute traffic across instances to improve reliability and responsiveness. Use Cost Management tools to track and analyze resources, and optimize spending.
  • Iterate improvements. Address bottlenecks or inefficiencies based on user feedback. Detect inefficiencies, such as slow response times, high error rates, or underutilized resources. Resolve specific issues, such as optimizing workflows, refining configurations, or upgrading integrations.

Decommission legacy systems

  • Retire unused systems. Shut down legacy infrastructure once workloads are fully operational in the cloud.
  • Archive data. Securely store historical data for compliance and reference.

Continuous improvement and maintenance

  • Train teams. Ensure IT and operations staff are proficient with cloud tools and processes.
  • Perform regular audits. Conduct periodic reviews to ensure compliance, security, and performance.
  • Adopt new features. Stay updated with advancements in cloud technologies.

Additional considerations

  • Start small, and scale gradually. Avoid overwhelming the team by tackling too much at once.
  • Leverage cloud expertise. Work with cloud architects or consultants to minimize risk.
  • Communicate with stakeholders. Keep all stakeholders informed at every stage.
Deviniti Insights

Remember that migrating to Atlassian Cloud does not render the process complete. Instead, you should establish mechanisms for continuous improvement. Assess system performance and user feedback. This will help you identify chances for further optimizations and enhancements.

Key differences between cloud migration approaches

Aspect	Fresh Start	 Lift-and-Shift	Phased
Architecture design	 Designs a new cloud-native architecture with modern principles (microservices, serverless).	Copies existing architecture with no significant design changes.	Gradually modernizes some systems while others remain unchanged.
Complexity and risk	High complexity and risk due to significant changes in architecture and processes.	Low complexity and risk since minimal changes are made to the existing systems.	Moderate complexity and risk as each phase handles manageable portions.
Migration speed	Slowest due to extensive planning, redesign, and testing.	Fastest because it avoids re-architecting and focuses on replication.	Moderate speed; incremental migration ensures continuity but extends the timeline.
Cost implications	High upfront costs due to re-architecture and development but offers long-term savings.	Low upfront costs but potentially higher long-term operational costs due to inefficiencies.	Moderate initial costs spread across phases; long-term savings vary based on modernization level.
Customization potential	High potential for customization and innovation.	Limited customization as it replicates the existing setup.	Medium; some systems may be modernized while others are simply moved.
Operational impact	May require downtime during transition and retraining staff.	Minimal disruption with a focus on maintaining current operations.	Minimal disruption by migrating in controlled stages.
Technical debt management	Eliminates technical debt by rebuilding systems.	Preserves existing technical debt, potentially complicating future upgrades or optimizations.	Gradually reduces technical debt as legacy systems are modernized.

Risks unique to Phased Migration to the cloud

Phased Migration is a lengthy and incremental process that requires continuous effort on your part. There are several factors related to timelines and expenses that are particularly dangerous and need to be handled with care.

1. Complex coordination across multiple phases

Risk. When you manage the migration of workloads in phases across a long timeline, it can lead to miscommunication and coordination challenges between teams. This creates risks of overlapping or missed migration tasks.

Why it’s unique. The phased approach involves migrating applications over multiple phases. This requires intense coordination to ensure you can handle dependencies correctly.

Impact. You might suffer migration delays, increased complexity, and operational disruptions during the transition.

Solution. You can deal with these issues with the following methods:

  • Develop a comprehensive project plan that clearly outlines the timeline, dependencies, and milestones for each migration phase.
  • Assign a dedicated project manager or migration lead to ensure coordination and execution of each phase.

Action. Utilize tools like Jira Advanced Roadmaps to create visual timelines, assign tasks, and monitor interdependencies across phases. Use Jira dashboards to track progress and flag risks early for proactive issue resolution.

2. Increased risk of inconsistency across systems

Risk. With a gradual shift to the cloud, different systems (some on-premises and some in the cloud) might operate inconsistently. This can lead to integration and compatibility issues.

Why it’s unique. The phased migration approach is staggered in nature. It means that part of the system may be on-premises, while others are in the cloud. You may have a hybrid environment for a while.

Impact. You can face integration challenges, inconsistent user experiences, and higher operational complexity.

Solution. You might want to test these ideas:

  • Implement robust data synchronization and integration mechanisms between cloud-hosted and on-premises systems.
  • Use hybrid cloud architectures that support seamless operation across both environments during the migration period.

Action. Conduct frequent testing and validation during each phase to ensure data integrity and application functionality are consistent across the on-premises and cloud environments.

3. Cost overruns due to extended timeline

Risk. A Phased Migration is a prolonged process by nature. Due to this, you may experience higher-than-expected costs. Especially those related to managing two environments simultaneously.

Why it’s unique. Phased migrations can stretch across months or even years. This forces you to maintain your original infrastructure for longer periods while your new infrastructure is being progressively adopted.

Impact. You must deal with ongoing operational costs and infrastructure management expenses. This can push the total migration cost beyond your initial estimates.

Solution. There are several ways to handle this conundrum:

  • Carefully track and allocate budgets for each phase of the migration. Focus on critical workloads first.
  • Set clear cost control guidelines. Continuously monitor cloud spending throughout the migration process.

Action. Regularly reassess and optimize resources in both environments. Ensure you are operating efficiently.

4. Delayed Return on Investment (ROI)

Risk. A phased migration approach means that the organization won’t fully benefit from cloud advantages until the migration is complete.

Why it’s unique. The incremental nature of phased migrations results in a slower transition to the full cloud environment. This delays your receiving benefits like cost savings, scalability, and performance improvements.

Impact. You must deal with a prolonged timeline to achieve the full financial and operational benefits of cloud adoption.

Solution. There are some ways to limit the impact:

  • Set realistic timelines for each migration phase. Ensure early phases deliver value that justifies the ongoing costs.
  • Focus on quick wins early in the migration to generate visible ROI. For instance, you can migrate non-critical applications first or improve cost efficiency.

Action. Develop a continuous feedback loop to ensure every migration phase provides value and aligns with your business goals.

Different steps for each cloud migration approach

Step	Fresh start	Lift-and-shift	Phased migration
Architect cloud-native solutions	Build new applications or re-architect existing ones to leverage cloud-native features like microservices, containers, or serverless technologies.	Skip architectural redesign entirely; replicate existing systems in the cloud with no changes.	Modernize workloads selectively during later phases while maintaining some on-premises systems.
Prioritize and segment workloads	Not applicable—assumes all workloads will be redesigned and rebuilt.	Not necessary—focuses on migrating all workloads quickly and without segmentation.	Systematically divide workloads into low, medium, and high complexity phases to migrate incrementally.
Iterative integration testing	Requires extensive testing to ensure new systems integrate with cloud-native services and operate as designed.	Limited testing focused on confirming functionality matches the original system, with little emphasis on new integrations or optimizations.	Conduct testing specific to each phase, ensuring that partial migrations do not disrupt the operation of on-premises systems or remaining workloads.
Resource optimization during setup	Design auto-scaling, load balancing, and other efficiency measures upfront.	Optimizations are deferred until post-migration; initial setup replicates existing resource usage, often leading to over-provisioning or inefficiencies.	Introduce optimizations in later phases as workloads are modernized and operational needs evolve.
Modernization efforts	Comprehensive modernization of all systems during the migration.	No modernization; systems are moved as-is, preserving legacy configurations.	Partial modernization occurs during later phases, allowing incremental improvements.
Downtime management	May involve significant downtime during transitions to the newly designed systems.	Minimal downtime by lifting and shifting systems quickly without requiring extensive changes or testing.	Minimizes downtime by transitioning systems in phases, allowing continued operation of critical workloads.
Legacy system decommissioning	Often occurs immediately after migration since new systems are fully operational in the cloud.	Decommissioning happens only after verifying all workloads are running stably in the cloud, often leading to prolonged dual-operation costs.	Happens incrementally, as legacy systems are phased out in alignment with workload transitions.

Unique roles for Phased Migration

Phased Migration often entails working simultaneously in two different environments. For this reason, you might need people who can handle prolonged transitions and maintain steady workflows throughout the process.

1. Hybrid Environment Specialist

Responsibilities

  • Manages both environments during the phased transition.
  • Ensures compatibility and smooth interaction between systems across environments.

Irrelevance in other strategies.

  • In Fresh Start, there is no hybrid period. The legacy system is replaced entirely.
  • In Lift-and-Shift, migration happens in one go, eliminating the need for hybrid management.

2. Iterative QA/Test Engineer

Responsibilities

  • Conducts testing during each migration phase to validate system functionality, performance, and data integrity incrementally.
  • Focuses on maintaining compatibility between phased components and the remaining legacy systems.

Irrelevance in other strategies

  • In Fresh Start, testing is comprehensive but happens at a single point in time after the migration.
  • In Lift-and-Shift, testing is more straightforward, as it primarily focuses on verifying replication fidelity.

3. Change Adoption Strategist

Responsibilities

  • Gradually introduces new features and workflows to users as each phase is completed.
  • Monitors user adaptation and provides feedback loops to refine future phases.

Irrelevance in other strategies

  • In Fresh Start, all changes are introduced at once with the new environment. This requires holistic change management.
  • In Lift-and-Shift, the user experience remains largely unchanged. This reduces the need for phased adoption strategies.

Ready to start your Atlassian Cloud migration?

We have gone through a long journey over the Atlassian Cloud migration topic. You should be fully equipped with sufficient knowledge of what Cloud migration approach is optimal for you and how to execute it. Atlassian Cloud migration can bring you numerous benefits in terms of flexibility, access to new features and futureproofing. However, the migration process can be challenging, so it’s a good idea to handle it in a structured way.

A good idea to support your Atlassian Cloud migration process is working with an Atlassian Partner. Their experience will help you mitigate risk, achieve the most optimal performance, and save costs on mishandled issues. If you are looking for a skilled Atlassian Partner, we are ready to offer our support. Feel free to ask us any question on Cloud migration or any other Atlassian-related topic, and we will answer in no time!

Have you decided on your Atlassian Cloud migration approach?

We can provide you with a smooth migration process and optimize your new cloud environment to your needs. Deviniti is an Atlassian Cloud Specialized Partner which means we have the best expertise on adapting the Atlassian Cloud environment to achieve peak performance.
Read more

FAQ about Atlassian Cloud migration

  • Why migrate to Atlassian Cloud

    1. Advanced reporting

    Atlassian Cloud tools have better access to data, so they can provide you with better work insights. For instance, they can deliver details on developer productivity (team velocity, cycle time, etc.). They can also show dependencies, performance, and progress within various company units.

    2. Automation options

    Atlassian Cloud offers exclusive AI features that allow you to automate routine tasks. The automation options include assigning tickets, updating statuses, or notifying stakeholders within your management tools. When you design knowledge bases, features like predictive text can speed up the creation of articles.

    3. Enhanced collaboration

    Atlassian Cloud is strongly integrated, creating an optimal environment for collaboration. Furthermore, they offer smooth integration options with external tools like Slack or Microsoft Teams. This speeds up communication and increases overall cooperation efficiency.

    4. Efficient workflows

    The cloud environment provides built-in workflows for Agile, Scrum, or Kanban. They allow for detailed tracking of development projects. Atlassian Cloud also offers pre-built workflows DevOps and ITSM, thus shortening the time needed for building stable company processes.

    5. Access to new features without upgrades

    Thanks to this, you can take advantage of continuous improvements made by Atlassian in real time. Stay competitive and efficient by accessing new features without needing manual upgrades or downtime. For those transitioning from the Data Center, it means leaving behind manual upgrade cycles. They can gain immediate access to new features.

  • What are the main benefits of migrating to Atlassian Cloud?

    1. Cost savings

    Moving to Atlassian Cloud removes the necessity for upfront investments in hardware and software. Organizations can opt for a subscription model based on user count, making it a more budget-friendly choice, particularly for smaller teams. This flexibility enables scaling as required without incurring extra hardware expenses.

     

    2. Scalability

    Atlassian Cloud allows for easy adjustment of resources based on team requirements. As organizations expand, they can seamlessly add new users and projects without the concern of infrastructure constraints. Automatic updates guarantee that users always have access to the most recent features.

     

    3. Enhanced collaboration

    The cloud setup promotes remote work and collaboration among team members located in different areas. Users can utilize tools while on the move, encouraging a more adaptable work culture that fits with today’s distributed workforce.

     

    4. Improved security

    Atlassian Cloud features enterprise-level security measures, including two-factor authentication, data encryption, and regular security assessments. It also adheres to various industry standards such as SOC 2 and ISO 27001, ensuring the protection of sensitive information.

     

    5. Faster deployment

    Organizations can implement tools and projects more swiftly in the cloud since there’s no requirement for server configuration or software installation. This efficiency allows teams to concentrate on project setup and customization rather than managing infrastructure.

     

    6. Increased productivity

    Users gain from enhanced reporting and analytics features, which help them monitor project progress and pinpoint bottlenecks effectively. The integration with popular analytics tools further improves insights into team performance.

     

    7. Centralized administration

    Atlassian Cloud provides a centralized control center for administrators, offering visibility and management over the entire Atlassian ecosystem from a single location. This streamlined approach makes it easier to handle user permissions and configurations efficiently.

     

    8. Seamless integrations

    The cloud platform facilitates deep integrations between Atlassian products and third-party applications, minimizing context switching and boosting workflow efficiency across teams. This interconnectedness fosters improved collaboration both within and between departments.

     

    9. Continuous improvement

    Organizations enjoy ongoing access to new features and updates without the need for manual upgrades or downtime. This ensures that teams can take advantage of the latest innovations as soon as they are released.

  • What are the cost savings associated with migrating to Atlassian Cloud?

    1. Reduction in licensing fees

    Organizations can achieve significant savings on Atlassian licensing fees through improved user management and streamlined processes. By cleaning up user accounts and eliminating duplicate or obsolete licenses, companies can optimize their licensing costs.

     

    2. Decreased hardware and maintenance costs

    Migrating to Atlassian Cloud allows organizations to decommission on-premises servers, leading to substantial savings in hardware costs and ongoing maintenance expenses. This includes avoiding costs associated with upgrading and managing physical infrastructure.

    3. Elimination of in-house administration costs

    Many organizations find that they can reduce or eliminate the need for dedicated in-house Atlassian administrators after migrating to the cloud. This reduction in personnel can lead to significant labor cost savings.

     

    4. Consolidation of third-party apps

    The migration process often reveals opportunities to consolidate third-party applications, as many companies discover they are paying for similar tools across departments. By leveraging enhanced native functionality in Atlassian Cloud, organizations can reduce their reliance on costly third-party apps.

     

    5. Faster deployment of features and updates

    The cloud environment allows for the rapid deployment of new features and updates, minimizing the need for extensive manual work or downtime. This results in enhanced operational efficiency and lower costs linked to project delays.

     

    6. Long-term ROI

    According to a Forrester report, organizations can achieve a 155% return on investment (ROI) within three years after migrating, with a payback period of just six months. This long-term financial advantage highlights the cost-effectiveness of moving to Atlassian Cloud.

     

    7. Avoidance of significant incident costs

    Companies that have made the switch report avoiding expenses related to major outages or incidents that can arise with self-hosted solutions, further strengthening the financial case for cloud migration.

     

    8. Flexible pricing models

    Atlassian Cloud provides a range of subscription options, enabling organizations to choose a plan that aligns with their budget and requirements. This flexibility allows companies to start small and scale as needed without incurring extra hardware expenses.

  • How does Atlassian Cloud improve team collaboration?

    1. Unified platform for collaboration

    Atlassian Cloud offers a centralized space where teams can work together effortlessly across different departments. This cohesive environment promotes real-time collaboration, enabling teams to collaborate more effectively, no matter where they are located.

     

    2. Intuitive collaboration tools

    The platform features user-friendly tools like Smart Links, which display rich previews of work from other products, allowing teams to collaborate within a single interface. This minimizes the need to switch between different tools and helps maintain focus on their tasks.

     

    3. Real-time communication

    Atlassian Cloud supports instant communication with features like @mentions, which utilize machine learning to suggest relevant team members for discussions. This ensures that the right individuals are always informed, boosting collaboration efficiency.

     

    4. Cross-product integration

    The capability to integrate various Atlassian products, such as Jira, Confluence, and Trello, enables teams to connect their workflows seamlessly. For example, linking project documentation in Confluence directly to Jira tasks makes all relevant information easily accessible and current.

     

    5. Enhanced visibility and context

    The platform’s cross-product search features allow users to quickly locate information across all tools, providing the context necessary for informed decision-making. This visibility helps teams stay aligned and aware of each other’s work.

     

    6. Improved accessibility

    With the ability to access the cloud from any device, teams can collaborate seamlessly, whether they are in the office or working from home. This flexibility is essential in today’s work environments and boosts employee engagement.

     

    7. Data-driven insights

    The platform provides real-time analytics and dashboards that empower teams to make quick, data-driven decisions. This feature fosters collaboration by ensuring that all team members have access to the same current information.

     

    8. Continuous improvement through updates

    Frequent updates bring new features and enhancements without the need for extensive downtime or retraining. This ongoing improvement keeps teams engaged with the latest tools and functionalities.

  • What are the best practices for migrating user accounts and permissions to Atlassian Cloud?

    1. Conduct a detailed user audit

    Before migration, carry out a comprehensive analysis of user roles and permissions. Identify any inactive users who could pose a security risk if they retain access in the cloud environment. Regular audits not only enhance security but can also improve cost efficiency by reducing unnecessary licenses.

     

    2. Prepare user accounts

    Examine user accounts for issues such as invalid or duplicated email addresses. Resolve these problems prior to migration to ensure a smooth transition and avoid complications during the user claim process in the cloud.

     

    3. Utilize the cloud migration assistant

    Make use of Atlassian’s Cloud Migration Assistant to help transfer users from Data Center to Cloud. This tool offers visibility into existing users and groups, which helps streamline the migration process.

     

    4. Establish an identity migration plan

    Develop a detailed identity management plan that outlines how user groups and permissions will be migrated. Familiarize yourself with new features in Atlassian Cloud, such as how accounts are linked by unique email addresses.

     

    5. Verify domain ownership

    After migration, verify your domain(s) to effectively manage accounts within your organization. This step is essential for ensuring that users can access their accounts after the migration.

     

    6. Review group permissions post-migration

    Once user groups have been migrated, carefully review and approve group permissions. Keep in mind that previously migrated groups will not automatically update their memberships; any changes in the local instance must be manually reflected in the cloud.

     

    7. Adopt a phased migration approach

    Consider migrating users in phases instead of all at once. Start with a pilot group to test the migration process, allowing you to identify any issues before rolling it out to the entire organization.

     

    8. Focus on user experience

    Involve users early in the migration process to collect feedback and address any concerns they may have. Offering training and support during this transition will help users adjust to the new environment more smoothly.

     

    9. Ensure data security throughout migration

    Put in place security measures like encryption during data transfer to safeguard sensitive information. Regular compliance checks are essential to confirm that your cloud environment adheres to relevant regulations.

  • How can companies identify and address potential compatibility issues with marketplace apps during migration?

    1. Conduct a thorough compatibility assessment

    Before migration, evaluate how well the new platform works with existing plugins, integrations, and customizations. This assessment will help pinpoint any potential issues that could impact functionality after migration.

     

    2. Perform a pilot migration

    Carry out a test migration using a small set of data and applications to reveal compatibility issues early in the process. This approach allows teams to tackle any problems before proceeding with the full migration.

     

    3. Engage in application audits

    Perform a detailed audit of current applications to identify outdated technologies, dependencies, and performance issues. This audit should focus on understanding how existing systems interact with marketplace apps.

     

    4. Evaluate dependencies

    Examine the dependencies between applications and marketplace apps to identify potential incompatibilities that may hinder the migration process. Understanding these relationships is essential for a successful transition.

     

    5. Utilize testing and validation

    Before carrying out the migration, conduct thorough testing to confirm that all applications operate correctly in the new environment. This should include usability testing, performance testing, and security testing.

     

    6. Collaborate with experienced developers

    Engage closely with developers and IT professionals who have a background in marketplace migrations. Their knowledge can help navigate technical challenges and ensure that any potential compatibility issues are effectively addressed.

     

    7. Monitor post-migration performance

    After the migration, keep a close eye on the performance of marketplace apps to spot any remaining compatibility issues. This proactive strategy allows for swift resolution of problems as they come up.

     

    8. Establish clear communication channels

    Ensure that all stakeholders are kept in the loop throughout the migration process to manage expectations and promptly address any concerns related to compatibility issues.

  • What strategies can be used to clean up inactive or unused data before migrating to Atlassian Cloud?

    1. Conduct a comprehensive data audit

    Carry out a thorough examination of the current data, which includes projects, issues, and user accounts. Look for inactive users, outdated projects, and applications that are no longer in use, and safely remove them before migration.

     

    2. Remove duplicate accounts and email addresses

    Resolve any duplicate user accounts and verify that all email addresses are valid and unique. This will help streamline user management in the cloud environment and avoid potential conflicts during migration.

     

    3. Eliminate unused apps and trial data

    Evaluate the installed marketplace apps and eliminate any that are no longer being used or have expired trial licenses. This will help reduce clutter and lower licensing costs associated with unused applications.

     

    4. Identify and archive obsolete projects

    Review the existing projects to identify those that are inactive or no longer relevant. Archive or delete these projects to decrease the total data volume being migrated.

     

    5. Standardize custom workflows

    Simplify intricate custom workflows by standardizing them wherever possible. This will help reduce data complexity and ensure smoother functionality in the cloud environment.

     

    6. Review user groups and permissions

    Take a close look at user groups and permission settings to spot any redundancies or unnecessary complexities. Simplifying these can make user management easier after migration.

     

    7. Minimize historical data

    Eliminate outdated content, such as old page versions, blog posts, and large attachments that are no longer necessary. This will help reduce the database size and enhance performance in the cloud.

     

    8. Utilize bulk actions for cleanup

    Think about using tools like Optimizer for Jira to carry out bulk updates or deletions of inactive fields, issues, or users. This approach can save you time and effort compared to cleaning up manually.

     

    9. Backup data before deletion

    Always ensure you create backups of important data before making any major deletions or changes. This step is crucial to protect against the accidental loss of vital information during the cleanup process.

  • How does user acceptance testing (UAT) contribute to the success of an Atlassian Cloud migration?

    1. Validation of everyday tasks

    User Acceptance Testing (UAT) enables users to replicate their daily activities in a cloud environment, confirming that all features operate as intended. This practical testing uncovers issues that might not surface during technical evaluations, such as usability problems or interruptions in workflow.

     

    2. Involvement of diverse user groups

    By choosing testers from different teams and roles, UAT gathers a broad spectrum of viewpoints and experiences. This variety is essential for ensuring that the needs of all user types are addressed, which is crucial for pinpointing potential challenges in the new system.

     

    3. Feedback loop creation

    UAT sets up a systematic feedback process where users can report problems and propose enhancements. This ongoing process facilitates timely modifications before the final migration, minimizing the chances of facing major issues after the launch.

     

    4. Identification of integration issues

    Throughout UAT, users can evaluate integrations with other applications and systems, verifying that all connections operate smoothly. This phase is vital for ensuring uninterrupted workflows and avoiding service disruptions following migration.

     

    5. Documentation of changes

    User Acceptance Testing (UAT) involves documenting any changes that users encounter, such as new features or modified user interfaces. This documentation is essential for creating training materials and communication plans for users moving to the cloud environment.

     

    6. Testing new features and functionality

    During UAT, users have the opportunity to explore the new features offered in the cloud version of Atlassian products. This hands-on experience helps them get accustomed to the updated interface and functionalities, boosting their confidence and satisfaction.

     

    7. Risk mitigation

    By identifying potential issues during UAT, organizations can resolve them before the official launch, significantly lowering the chances of operational disruptions during or after the migration.

     

    8. Preparation for change management

    UAT also prepares both users and management for the changes that come with migration. It offers valuable insights into how workflows might change and what support users will require during the transition.

  • What are the advantages of conducting a comprehensive assessment before starting the migration process?

    1. Understanding the current state

    A detailed evaluation offers a clear perspective on the current IT infrastructure, encompassing hardware, software, and data architecture. This insight enables organizations to identify which components require migration and facilitates a smoother transition by pinpointing dependencies and potential challenges early in the process.

     

    2. Cost estimation

    Evaluations are essential for estimating the costs linked to migration, covering infrastructure, software, and ongoing operational expenses. By clarifying these costs, organizations can assess the financial feasibility of cloud migration and make well-informed decisions about budget allocation.

     

    3. Risk analysis

    A thorough assessment aids in recognizing potential risks tied to the migration process, including data security concerns, service disruptions, and compliance issues. By proactively addressing these risks, organizations can develop mitigation strategies to safeguard their data integrity during and after the migration.

     

    4. Resource planning

    The assessment helps organizations identify the skills and resources necessary for a successful migration. If any gaps in expertise are found, companies can arrange for training or consider hiring additional staff to ensure effective management of the migration process.

     

    5. Workload prioritization

    Organizations can determine which applications and data to migrate first by evaluating workloads and their readiness for migration, focusing on their business impact and complexity. This strategic method helps maximize benefits while minimizing disruptions during the migration process.

     

    6. Enhanced collaboration

    Engaging stakeholders early in the assessment process promotes collaboration across departments, ensuring that everyone is on the same page regarding the migration’s objectives and procedures. This teamwork is crucial for effectively managing organizational changes during the transition.

     

    7. Improved project planning

    A thorough assessment improves project planning by establishing clear milestones and timelines for execution. It also defines roles and responsibilities among team members, which is vital for organized migration management.

     

    8. Increased stakeholder confidence

    Providing a detailed assessment and migration plan fosters trust among stakeholders by offering insights into anticipated costs, benefits, and potential challenges. This level of confidence is essential for gaining support from key decision-makers.