Server/DC to Cloud Migration with CCMA
This document explains how Baseline data is migrated from Jira/Confluence Server or Data Center to Cloud using Atlassian CCMA.
It outlines supported components, expected behaviors, and important notes you should consider before performing the migration.
Important Prerequisite
CCMA migration is supported only if your Data Center instance runs Baseline version XXX or later.
Please make sure to update your app before starting the migration.
What is Migrated?
Baseline Definitions
Baseline Permissions
All migrated items must appear in Cloud exactly as they exist on the Server.
Access Settings
Group-based access settings of Baseline defined in the Data Center environment are migrated to the Cloud.
If a group from the original access settings does not exist in the Cloud environment, the data will still be migrated, but a warning will be logged in the Baseline migration log indicating the missing group.
Baseline Definitions
Baseline definitions include all core attributes that describe a baseline.
During migration, CCMA transfers the complete baseline definition exactly as it is on the Server/DC instance. This includes:
Baseline name
Description
Created date
Created by
Content scope configuration
Include all pages: all pages under the space
Select individual pages: manually selected subset of pages
Associated pages and page hierarchy
These details are recreated in Cloud without recalculation or modification.
After migration, the baseline visible in Cloud should mirror the Server baseline in name, structure, and configuration.
Baseline Permissions (User & Groups)
Baseline permissions determine which users and user groups can access a baseline.
The permission model is simple: a user either has access to the baseline or does not.
If a user (or group) has access:
They can view the baseline
They can create new baselines
They can edit/update existing baselines
Baseline permissions are migrated as-is from Data Center to Cloud.
This includes which users/groups can view a baseline and any additional baseline-related actions (such as creating, editing, or deleting) that the same permission configuration allows, CCMA migrates this permission as a single unified permission set.
During migration:
Users/groups who have access on Server will retain the same access on Cloud.
If a user/group cannot be matched in Cloud, CCMA will report this during the assessment phase.
After migration, the same set of users/groups will be able to view, create, and edit baselines exactly as they could on the Server/DC environment.
Repeated Migrations & Overriding Behavior
Component | Override Behavior |
|---|---|
Baseline Definitions | Overwritten only if a baseline with the same name exists same space in Cloud. If no baseline with the same name exists, the Server baseline is created as a new baseline in Cloud. |
Baseline Permissions | Always fully overwritten by the latest permission configuration from Server/Data Center. Users/groups with access on Cloud are replaced by Server/DC configuration. |