Bridging the Clouds: The Basics of a Cloud Copy Plan

[#1]

Hi everyone!

With all the craziness that is preparing for Team’24, the premier teamwork conference, we didn’t get to post last week. So this week you’ll get two posts back to back! You’ve already heard about "What is cloud to cloud?" and "How have customers been using cloud to cloud." Now we’re going to talk about how you too can harness the power of copy product data tools to move data between cloud sites.

How do I create a cloud to cloud copy plan?

You’ll want to start off by visiting admin.atlassian.com, where you can choose the organization from which you'd like to copy your data.

To start copying product data, you'll navigate to the Settings tab and then the "Data management" section on the left panel, where you'll be brought to a screen where you can "Start copying product data."

You'll be directed to a screen where you can create and view your copy plans, enabling you to effectively manage all your copy plans within your organization.

The following articulates the basic flow of how you'll copy product data once you've identified your source. Each plan consists of a collection of projects (or spaces), users, groups, and related data such as pages, configurations, and settings.

First, choose the product for which you want to copy the data. Currently, we provide support for Jira and Confluence, with intentions to broaden our support to encompass other products in the near future. Keep an eye out for upcoming updates!

Next, you’ll define your source and destination, that is, the location from which you are copying data and the location to which you are pasting it. You’ll also give a name to your Copy Plan, e.g., "Engineering Re-Org Data Transfer."

Once you've designated the copy plan, you can proceed to choose the specific project for duplication. Here, you will access valuable metadata pertaining to your projects, such as the number of issues, attachment sizes, last update timestamp, and an estimated duration required to complete the project copying process.

You have various options when it comes to users and groups. You can choose to either copy all users and groups, or specifically those associated with the projects you are duplicating. Additionally, you have the flexibility to copy users and groups separately, ensuring that users are not automatically added to your groups upon duplication, or alternatively, copy users along with their respective groups, allowing for both user addition to their corresponding groups and subsequent duplication.

And before executing your copy plan, we conduct thorough checks to ensure everything functions as expected. For instance, we verify the presence of identical apps on both the source and destination systems, a crucial requirement for accurately linking your data.

Once you have accessed the dashboard, you will be able to track and monitor the progress of the copy plan. After the copying process is finished, simply go to your destination site, EMC in this case, refresh the page, and you will find that the copied project is now available there along with all associated issues.

For a complete walkthrough of what creating a simple copy data plan looks like, Avishekh Das, our Senior Content Designer, put together a video of just that!

Now, it might seem straightforward and in some cases it can be, but what would a community post be without some tips & tricks for you:

• Ensure the destination site has a license for the products that you intend to move and that it accommodates new users who will be added as part of the copy. (While this may seem straightforward, you’d be surprised how many folks forget this step!)

• Be mindful that migrating users to the cloud could result in additional costs based on your licensing arrangement with Atlassian. If you are on A La Carte licensing plans, paying for users monthly but aiming to federate into multiple sites, utilizing scoping is a prudent approach to ensure that only necessary users, groups, and permissions are transferred to the selected projects. In most cases, it's advisable not to migrate any unnecessary components.

• Using this knowledge base article, you can understand not only how your data is being moved but also what data is being moved.

• Post migration, download the report to check on what has been moved!

Later this week, we’ll take a peak behind the curtain to see what’s coming up in cloud to cloud and how we’ll be showing up at Team’24! Feel free to drop your questions or thoughts in the comment section below.