Data Center migration guides

No organization is the same and neither is your migration journey. The key to any good migration is planning.

Guide 2: Plan your migration

Now that you’ve looked over and chosen your migration path, you’re ready to start planning your move to Data Center.

Build your team Required

One of the most important parts of this journey is assembling the right team and doing so as early as possible. The launch of Data Center will impact multiple teams across your organization and requires everyone’s collective involvement.

Once your project team is assembled, it’s important to align the team on shared goals and build your timeline with an agreed-upon target date.

There’s no definitive answer to which roles and how many people should be included on the team. However, it’s important to consider the following areas of expertise when assembling your team:

Application admin


The application admin handles the day-to-day administration. They have in-depth knowledge of the product, care about performance, reliability, and evaluate and maintain Marketplace apps. They may also work closely with end users to understand their needs and provide assistance or training.

  • Verifies functionality and performance during testing to ensure that Data Center is operating properly.
  • Determines whether or not to keep apps that are not Data Center certified when upgrading.
  • Verifies that the users and permissions are maintained, or changed, correctly throughout the transition.

System admin


The system administrator handles everything from the infrastructure to the product interface. They are concerned with backups, storage, network, and performance.

  • Gathers the hardware (physical or virtual) needed.
  • Performs the actual Data Center installation.
  • Ensure that all components are working properly if you choose to deploy in a cluster.
  • Pipes logs from on-disk to log aggregator to enable monitoring and security strategy.

Project lead


The project lead has a deep relationship with the business and knows how and why the product is used to meet company objectives. They also know how to make the right tradeoffs to maintain governance across products.

  • Keeps the project on track with key milestones and estimated dates to achieve them.
  • Owns the schedule, ensures task completion, and resolves cross-functional issues.
  • Communicates project updates to stakeholders and announcements to end users.
  • Works with primary stakeholders in the purchase of Data Center.

If you’re deploying Data Center in a clustered architecture, you may want to also consider having team members with technical expertise in the following areas:

  • Network engineering: Review spec and build out your infrastructure.
  • Database administration: Confirm database integrity and smooth operations.
  • Site reliability: Establish instance uptime, performance, and disaster recovery operations.
  • Security: Ensure compliance with security standards (VPN, firewall, etc).

Need additional team members

Atlassian offers support if you need help with your migration.

Free with Data Center

Priority Support (for your first six months): Submit a request to Atlassian Support and your issues will route directly to our most Senior Engineers, who are committed to delivering higher SLAs, faster triage, and faster resolutions. We currently offer this service to customers with a Data Center license for Jira Software, Jira Service Desk, or Confluence.

*This will be included in your Data Center subscription effective February 2, 2021.

Atlassian Community: Prefer to crowdsource? Find answers, support, and inspiration from other Atlassian users. We recommend that you join the Enterprise community group for stories, tips, and best practices for using Atlassian products at scale.

Paid support resources

Technical Account Managers: Want an experienced Atlassian advisor with product and industry knowledge? Think of a Technical Account Manager as your strategic partner for all things Atlassian. They’ll help guide your journey by providing expertise and asking the questions you wouldn’t think to ask yourself.

Premier Support: Looking for an elevated level of service? Atlassian Premier Support offers our highest level of support with 24/7 access to a dedicated Senior Support Team.

Enterprise Partners: Looking for a one-stop-shop? Enterprise Partners conduct hands-on system integrations, deployments, and upgrades. Enterprise Partners are a great option for organizations with complex requirements or that are looking for onsite help. Visit our Partner Directory to find a partner that is right for you.

Build a timeline Required

Here are the basic timelines that you can use to gauge how long your migration should take.





0-2 weeks

1 month +


0-1 week

3 - 6 months

Go live

0-1 week

~ 6 - 9 months

Information icon

The timelines included are based on a number of our customers who have successfully installed Data Center, but it is important to note that the actual timeline will vary based on factors unique to your environment including, but not limited to, environment size, complexity, and preparedness.

Review your server instance and and optimize your infrastructure

Regardless of how you choose to deploy Data Center (non-clustered or clustered), you want to take the time to review your server instance and understand if there are any areas that you want to optimize during your migration.

Upgrade to the latest LTS release Recommended

Completing an upgrade and a migration at the same time can we challenging, so we recommend that you first upgrade your products to that latest LTS release if you aren’t already on one. This will help your migration run more smoothly.

Evaluate the size of your instance Required

Data Center is built to support the needs of teams at scale. To ensure that you set up your infrastructure for a successful migration, review the sizing of your current server instance and adjust based on profile size recommendations. As you adjust your size, consider their rate of growth so that you can scale accordingly.

Benchmark your server instance Recommended

Take a baseline measurement of your system’s existing functionality and performance. That way, if you choose to use features like custom field optimizer or archiving, you can measure the performance improvement between Data Center and your existing server instance.

Fine-tune your server instance Recommended

Even if you plan on immediately taking advantage of our capabilities (like archiving and custom field optimizer) to cool your instance down, you should fine tune your server instances before you move. Look at your current server instances and take the time to identify and correct any suboptimal configurations. Spending this time early on will help set up a stronger foundation for your Data Center instance.

Assess and update governance Required

How users interact with the products also affects the performance. Before deploying Data Center, assess these usage characteristics and determine whether you need to establish any restrictions on things like scripts that make REST calls or other integrations to protect performance.

Document current processes Recommended

After instance tuning, it’s time to document your server environment. This documentation can help guide configuration decisions in your Data Center migration, influence process modifications, and determine whether issues found after migrating are new or already existing.

Audit your current apps

Using a large number of apps may degrade the performance of your instance. It’s critical that you audit and remove apps that aren’t crucial to system functionality to increase overall system performance. You’ll also want to make sure your apps are compatible with Data Center, as your apps will need to be upgraded to a Data Center version if one is available.

If there currently isn’t a Data Center version of your app, you can continue to use your server app, but you will be required to upgrade once one becomes available.

You'll want to consider both the current and future price of your apps as part of your Data Center total cost of ownership. To learn more, see our total cost of ownership page.

Evaluate technology decisions

Getting ahead of your technology decisions will speed up the design of a production-ready environment for your Data Center products that is tailored to your organization’s needs. Whether you’re going to deploy your Data Center products in a clustered or non-clustered environment, look at the infrastructure you’re currently using to run your products and consider if it makes sense for you to deploy on AWS, Azure, or your own hardware. If you decide to deploy in a clustered environment, you’ll need to start assessing the additional components you will need, such as a load balancer, file system, and application nodes. Take a moment to determine what you have available or what you may have to purchase.

For additional recommendations and resources that can help you evaluate your technology decisions, download our deployment checklist.

Understand environment changes if you’re using a cloud provider

Browser grid icon

Application layer

Instances and locations

  • Do you want to federate or consolidate your instances?
  • What does your future growth look like?
  • Do you need to have any data isolation?
  • How many environments does your team have, such as staging or production environments?

Instances profiles

  • How many people are going to be accessing your instance?
  • Where are your teams going to be located?
  • How much data is currently in your instance and how much data do you plan to add to your instance?

Apps, integrations, and customizations

Do you need all of them, or is this an opportunity to simplify?

Server icon

Infrastructure layer

Instance sizing

  • What are your future growth projections?
  • Are there times when you have lower levels of user traffic?
Information icon

Looking at your user traffic can help determine your organization’s scale patterns. If there are times when you have more teams accessing your products, you can also consider setting up a scaling schedule.

For more information, here’s our node sizing overview.

Account structure

  • Which accounts should your environment be deployed on?
  • Do you want different accounts associated with each of your environments?
  • Do you want your Data Center products to use the same account as your other CI/CD or collaboration tools?

Governance model

  • What does your governance model look like?
  • What are your minimal system standards?
  • Are you using centralized logging?
  • What are your user management needs?

Consider using AWS landing zone and AWS System Manager as part of your governance model.


  • Do you want to use a new virtual private cloud (VPC)?

Information icon

Whether you want to deploy in a new VPC or use an existing one, you can leverage the Atlassian Standard Infrastructure (ASI) template.

  • Are there any network principles that you want to change, such as limiting public internet access and internal IP addressing for office and VPN network routing?
  • Should you use TLS certificates?


  • If using an existing VPC, have you come up with a plan for office and VPN network access?

Information icon

We recommend that you allow access from all offices and VPNs as your product usage will most likely grow over time.

Direct Connect

  • Do you want to use Direct Connect to help with performance and security?
  • How much data do you need to move from your server instance to Data Center?
Information icon

AWS Snow Family may be a resource that you may want to consider if you’re moving large amounts of data.

Safe icon

Business continuity and disaster recovery


What does your backup strategy look like?

Information icon

We recommend that you use a combination of both your existing backup strategy and backup capabilities built into AWS. For more information, see:

AWS provides infrastructure services that are less prone to singular outages. Our Quick Start templates use some of those services to provide high availability for your instance:

Regional failover

Do you need to implement cold, warm, or hot sites in different regions?

Typically, your disaster recovery needs are met by having your services run over multiple availability zones, but you may want to mitigate regional outages too. As you’re deciding if you want to implement these sites in different regions consider the following:

  • Cost of infrastructure and data transfer
  • Speed of recovery vs AWS
  • Time spent maintaining and testing the recovery site
  • Cost of running the site