Picking an Atlassian Cloud Migration Path

And Next Steps for a Successful Migration

There are so many reasons to consider a migration to Atlassian Cloud as it allows you to accelerate and scale the full potential of your team’s work in Jira or Confluence software. You’ve probably heard them all, but just in case you haven’t, here are just a few of the reasons that might have you thinking about making the switch.

Quick Start
Atlassian will get you up and running in minutes with no need for your team to worry about manual setup.

Cost Savings
You can cut your expenses on storage, support, and maintenance of physical hardware that you’d otherwise incur with a Server or Data Center solution.

Automatic Upgrades
When new features or product versions are available, updates are immediate and don’t require any manual work from you.

Remote Access
On the go? You can continue to collaborate with your team even when you’re not with them through remote access to your Atlassian product suite.

Security
Atlassian employs rigorous security protocols and extensive testing for vulnerabilities so you can be sure your data is never compromised.

Scalability
Experiencing outages or down time due to periods of excessive resource depletion? Atlassian Cloud helps you auto-scale whenever traffic or resource demand spikes.

So, if you’ve decided to make the move to Atlassian Cloud, the next step you’ll have to take is planning your migration path. Not all migrations are the same, nor should they be. It’s important to carefully plan out a path that will work for your organization and result in the least amount of down time possible.

Is Your Organization Atlassian Cloud Ready?

Not sure where to start? Come on out on February 12, for a webinar designed to teach you everything you need to know to plan your migration to Atlassian Cloud. We’ll have our IT consultants and Atlassian experts available to walk you through all of the considerations you need to make and answer all your questions.

For now, we’re going to take this opportunity to review the different types of migration paths, as well as the steps you need to take to ensure a successful migration.

The Atlassian Cloud Migration Types

The best migration path for your organization will depend on a few variables: what products you’re migrating, how your users and groups are currently managed in server, and if you plan to use Atlassian Access for SCIM (user provisioning). Here are the most common scenarios.

Type 1 – All at Once
For those who are confident to just lift and shift their data in one fell swoop from server to cloud. With this option, you will move everything at once and enjoy a fully cloud environment.

Type 2 – Merge
For those who have multiple server or cloud sites and want to merge them into a single cloud instance, Atlassian tools can enable you to consolidate your sites and streamline your work.

Type 3 – Hybrid
For those who feel that they should migrate in stages to avoid downtime, or wish to maintain both server and cloud to keep data segregated and enable collaboration with anyone.

Type 4 It’s Complicated
For many, the right type of migration path is clear, but not everyone will fall into a single category. For some complex enterprise organizations, there’s not a simple straight answer.

At Coyote Creek, it’s these types of scenarios that we encounter everyday. Not only are we IT veterans ourselves, but we are also Atlassian Platinum Solutions Partners which means we have the expertise and the skill set to walk you through a migration from plan to launch and optimize your instance for best practices along the way.

If you’re looking for an expert to come alongside your organization and offer a white glove approach to your migration, please contact us to set up a consultation. We’d love to help you through this process and get you started, confidently, in Atlassian Cloud.

Jira Migration Steps

After you’ve determined your user migration strategy, here are some steps you’ll want to take to begin the process of migrating from Jira Server to Jira Cloud. These steps aren’t meant to be a one-size-fits-all approach, but rather a guideline to know where you’ll need to begin. For an expertly handled, white-glove migration service, we’re here to help!

Step 1: Back up your Jira Server database

  1. Log in as a user with the Jira System Administrators permission.
  2. Click Jira Settings > System.
  3. Select Import & Export > Backup System to open the Jira backup page.
  4. In the File name field, type a name for your backup file.
  5. Click the Backup button and wait while your Jira data is backed up. Jira will save your backup as a zipped XML archive file within the export subdirectory of the Jira application home directory (jira-home for short). Check that Jira has the necessary file system permissions to write to this location.
  6. When the backup is complete, you’ll see a confirmation message. You can now retrieve the file from your server.

Step 2: Back up your Jira Server attachments, project avatars, and logos

Create a ZIP archive of the /data/attachments, /data/avatars/, and /logos/ directories. Make sure it uses the following structure:
Step 3: Import your server database backup into Jira Cloud

  1. Log in to your new Jira Cloud site with site-admin permissions.
  2. Click Jira Settings > System.
  3. In the Import and Export section, click Restore system.
  4. Select Import data and select the ZIP file you downloaded in Step 2: Back up your Jira Server database.
  5. We’ll check your file for errors, and ask you to choose settings for how you want your data imported.
    1. First, select your outgoing mail setting. Whichever option you choose, you can manually change after you migrate in the outgoing mail settings.
      1. You can choose to Enable outgoing mail, which allows Jira to send automated emails for interactions – for example, new comments on issues or issue transitions.
      2. If you choose to Disable outgoing mail, Jira won’t send automated emails for interactions.
    2. Next, select whether you want to overwrite or merge users from your server site with the users on your cloud site.
      1. Choosing to overwrite will completely replace all users from Confluence and Jira with the users in your backup file.
      2. Choosing to merge users will also merge groups. This means that if we find a group on your server instance with the same name as a group on your cloud site (in either Jira or Confluence), we will merge the users from the server group into the cloud group. The server group users will receive the permissions of the cloud group. Make sure you check for possible permission escalation before choosing this option.
  6. Click Run import. This will take you to a page where you can track your import progress. It may take a while for your import to finish, depending on the size of your backup.
  7. When the import is complete, you’ll be taken to a confirmation screen.
  8. From here, if you still need to import your media (attachments, logos, and project avatars) choose Import media. You’ll need to return to the Import and Export page before managing application access. If you’ve already completed this step, or aren’t planning to import your media, you can skip to step 6 by clicking the link to Grant application access.

Step 4: Import your Jira Server attachments, project avatars, and logos into Jira Cloud

  1. (If not already) log in to your new Jira Cloud site with site-admin permissions.
  2. Click Jira Settings > System.
  3. In the Import and Export section, click Restore system.
  4. Choose Import media and then find and select the media ZIP you created and downloaded in Step 3: Back up your Jira Server attachments, project avatars, and logos.
  5. This will take you to a page where you can track your import progress. It may take a while for your import to finish, depending on the size of your file.
  6. When the import is complete, you’ll be taken to a confirmation screen.
  7. From here, if you still need to import more media, repeat this step until all media files are imported. Note that you may want to test that all media was imported successfully in a new tab before importing the next batch of media.

Step 5: Review and grant access to groups imported from server

  1. Log in to your new Jira Cloud site and click Jira Settings > User management.
  2. In the Site settings section, choose Product access.
  3. Choose Review imported groups to review and confirm the default groups’ access.

Step 6: Re-add yourself to groups imported from server

You can do this two ways, either from the Groups section or the Users section at https://admin.atlassian.com.

From the Users section

  1. Go to https://admin.atlassian.com
  2. If you have multiple cloud sites, you’ll need to select the cloud site you’ve just migrated to.
  3. In the User management section, first choose Users.
  4. Find your profile.
  5. Click the … icon
  6. Choose Add user to group.
  7. Select the group(s) you need to be added to.
  8. Click Add to Groups.

From the Groups section

  1. Go to https://admin.atlassian.com.
  2. If you have multiple cloud sites, you’ll need to select the cloud site you’ve just migrated to.
  3. In the User management section, first choose Groups.
  4. Then, select the group you need to be added to.
  5. Choose Add members, and add yourself to the group.
  6. Repeat as needed for the rest of your groups.

Step 7: Complete post-migration checks

Depending on the type of migration you chose, there will be some final quality assurance steps to take once your migration is finished to ensure that everything went as intended. For a full list of post-migration recommendations, refer to this migration planning guide.

Confluence Migration Steps

For users wanting to migrate their Confluence Server instance to Atlassian Cloud, the recommended method is employing the Confluence Cloud Migration Assistant application.

In just one simple process, this app will allow you to move any or all of your Confluence spaces and migrate your users and groups from Atlassian Server to Atlassian Cloud. In addition, this app will check for common errors or conflicts prior to migrating so you can resolve them before migrating.

Please note that you will need an existing Confluence Cloud site set up before you can migrate. If you’re new to Atlassian Cloud, you can try a free extended cloud trial to get started. In addition, to use this application, your Confluence Server site must be running on version 5.10.0 or later.

This method is best for those who are migrating their entire Confluence Server site to a new Confluence Cloud site, or migrating Confluence Server spaces or users and groups to an existing Confluence Cloud Site.

Get Started with Atlassian Cloud

If you’re the type that really has to see it for yourself and get a feel for how it runs, you’re in luck. Atlassian offers a free extended cloud trial to explore and assess cloud over time to make sure that it’s the right fit for your organization before planning your full migration path.

Again, if you’re looking for expert assistance during your migration, we’d love to help you. Please contact us to set up a cloud migration consultation.

At Coyote Creek, as an Atlassian Platinum Solution Partner, we know it’s the human connection that makes the difference in all that we do.