By clicking"Accept all cookies", you agree to the storage of cookies on your device to improve website navigation, analyze website usage and support our marketing activities. For more information, please see our Privacy Policy.

Atlassian Cloud
Migration Guide

Atlassian Server products go end of life in February 2024. Our experts will help you migrate your Atlassian products to the Atlassian Cloud.

Image of Atlassian Cloud Migration ExpertImage of Atlassian Cloud Migration ExpertImage of Atlassian Cloud Migration Expert
linkyard serves over 140
Atlassian Cloud Migration Illustration

Atlassian Server End of life, what now?

Why migrate to the Atlassian

Cross icon that symbolizes the stop of sale of Atlassian Server licenses

Sales stop: Atlassian Server products

Atlassian stopped selling new licenses for its server products such as Jira, Confluence or Bitbucket in February 2021.
Tool icon that symbolizes support for Atlassian Server products

Maintenance: Support and patches

Support and patches will be offered until February 2024 - after that, the server products will definitely no longer be usable.
Cloud icon that symbolizes migration to Atlassian Cloud

Option: Cloud or Data Center

This leaves the two options of cloud and data center in the future. But for many companies, it no longer makes sense to operate applications themselves. The financial and personnel costs are too high to justify it.

Scalability in the Atlassian Cloud

Scale quickly and easily
in the cloud

In the cloud, data can be scaled very quickly and without great effort. Companies with particularly sensitive data such as banks, insurance companies or healthcare data are an exception. These usually have special regulations that they must fulfill.
Comparison chart comparing the administrative effort in the Atlassian Cloud with the on-premise variant

Migrate, but how?

How to migrate to the Atlassian

For migrations of any complexity, it is advisable to create checklists so that nothing is forgotten. We are guided by the following points.
The more of these questions are answered with "yes", the more complex the migration usually becomes.
Icon symbolizing the number of users to be migrated to the Atlassian Cloud

Question 1: Number of users

How many users do the instances to be migrated have?
Plugin icon that symbolizes the plugins to be migrated to the Atlassian Cloud

Question 2: Plugins

Are there plugins for Jira or Confluence that are being used?
Server icon, which symbolizes an AD connection

Question 3: AD connection

Is an AD connection needed if one currently exists?
Code icon symbolizing other customizations for migration to Atlassian Cloud

Question 4: Other adjustments

Are custom fields or other customizations, e.g. automations in use that are worth mentioning?

Attention error!

Complexity of

We also always recommend cleaning up the instances so that no legacy data can be found in the cloud, only relevant data.

Which areas from Confluence should be migrated?

The number of areas helps us to estimate the complexity of the migration.

Which projects from Jira should be migrated?

The more content you migrate, the more likely you are to run into errors.

How long does the migration take?

Migration time horizon

We assume a turnaround time of about 4 weeks.
If errors occur in the plugins during the migration that we have to forward to the manufacturers, the turnaround time can be considerably longer.
Icon symbolizing the test migration to the Atlassian Cloud

Test migration

First, a test migration is performed and any problems are identified and addressed.
Cloud icon that symbolizes the verification of migration to the Atlassian Cloud


The data migrated for test purposes is then tested and released by the customers.
Cloud icon with question mark, which symbolizes the possibility of a second test migration to the Atlassian Cloud

Second test migration

If any other faulty points are found during the tests, a second test migration can be performed.
Icon that symbolizes the productive migration to the Atlassian Cloud

Productive migration

If the faulty points were cleaned up, the productive migration is carried out at the end.

What is the cost of migration?

Since the instances differ, we don't have a fixed price for the migrations, the prices depend on apps used and the general complexity.
Contact us!
Documents with a magnifying glass

Our services

In particular, we specialize in subscription management, training & webinars, consulting & support, and custom system integrations.

Perform and advise on migrations

If you have decided to take the step towards the cloud, we will be happy to assist you. As certified Atlassian partners, we have successfully carried out several migrations and know the stumbling blocks.
Illustration of the migration to the Atlassian Cloud

Trainings: Arrive
in the cloud

Our trainings range from simple end-user
introductory trainings to admin courses. We are also happy to provide training on plugins that are well known to us
Badge icon that symbolizes completed Atlassian Cloud training.

Essential Trainings

In principle, the change from server/data center to the cloud is not a big deal for the users and most of them get along well in the new environment after a short acclimatization period. However, if support is required, we offer Essentials training for the cloud products.
Badge icon that symbolizes completed Atlassian Cloud training.

Refresher for administrators

The administration of the individual products is also similar in the cloud as it is on the server/data center. If you still need a little refresher, feel free to contact us and we will organize a course that fits your needs.
Badge icon that symbolizes completed Atlassian Cloud training.

Atlassian Admin Area

What is new in the cloud is the Atlassian Admin area. This is where, among other things, users and global permissions are managed or licenses are assigned. For many of our customers, we have taken this over to Server/Data Center. If you now want to manage this yourself, you can also contact us and we will organize a suitable course.

Alternatives to Atlassian Cloud

Atlassian Data Center

Data Center offers everything for high-availability operation and meets the highest security requirements


Collaborate with your team, customers, and external partners on documentation, knowledge bases, or QMS.


Creating and delivering your code, scheduling your work, and collaborating with your team - always smooth and enjoyable.

Archiving service

If you want to keep your instance for a longer time or "freeze" it, so to speak, this is the right option for you.

Your contact

Stefan Haller | Managing Partner

Do not trip!

Stumbling blocks in the migration to the Atlassian Cloud

Cloud Migration Assistant

It is very pleasing that Atlassian has developed a Cloud Migration Assistant for Jira and Confluence, which takes care of a large part of the migration. There are certain limitations, but basically the tasks from Jira and the pages from Confluence can be migrated. Global configurations and settings are not migrated (as of January 2023).
However, the Cloud Migration Assistant is also a bit unpredictable in parts. Certain things that were migrated without problems during the test migration, then generate error messages on the production day, or even content could be migrated without errors with previous versions of the assistant, with current versions must be selected for comparable content a different migration procedure and work with workarounds. At linkyard, we have a standardized migration procedure that we use for new migration projects, but we are prepared for unexpected deviations.


A second stumbling block can be the plugins used. There are plugins that are not available in the Atlassian Cloud. Here, alternatives must be sought and a migration of the data into the alternative plugin is guaranteed in the rarest cases. If the plugins also exist for the cloud, it must be checked how the data can be transferred to the cloud. In the best case, the plugin data is migrated along with the Cloud Migration Assistant (e.g. as an attachment with Gliffy). In the second best case, a migration path is offered by the plugin (e.g. with and the data can also be transferred to the cloud with a few clicks. If the data cannot be migrated as in the cases just mentioned, the only option is to manually reconfigure and capture the data (e.g. Scriptrunner), which can be very time-consuming depending on the plugins and how they are used.
When linkyard performs the migration, we are dependent on the support of the customers for the plugins - especially those that we do not use or we do not know how they are used in a company - and we need information on how the teams work and use the plugins.


This brings us to the most important point of the migration: the cooperation between the customers and linkyard. The migration should always be seen as a project in which both sides must reserve time for the work. We do not know all the instances and do not always see the specifics right away. Therefore we depend on explanations, for example if a special plugin is used in the company or how the users are managed. Also, with extensive testing by our customers, errors can be discovered and eliminated before the productive migration, which means that during the productive migration the discovered errors can be avoided or quickly corrected. In this way, the targeted time schedules can be adhered to.

General information about migration to the Atlassian Cloud

Of course, this is not a complete list of the stumbling blocks. For example, there are also Confluence macros that exist on the server/datacenter but do not exist in the cloud. The transfer of users to the cloud is also not necessarily trivial, especially if an AD connection is used or one is to be reused in the cloud.
For every migration, we recommend migrating, analyzing and checking the entire content first for test purposes in order to then be optimally prepared for the productive migration.