• Documentation

We’re renaming ‘products’ to ‘apps’

Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change

What migrates with the Confluence Cloud Migration Assistant

The Confluence Cloud Migration Assistant will add data to a Confluence Cloud site without overwriting any existing data. This means you can migrate data to a new cloud site or a cloud site with existing data. Not all data can be migrated yet with the latest version of the Confluence Cloud Migration Assistant.

What is migrated

What isn't migrated

  • Spaces including the default classification level, personal spaces, blogs, and items in trash

    • Custom templates created by users within a space

    • Pages including page restrictions, page classification level, page history, labels, tags, comments, and shared drafts

    • Tasks

    • Attachments, except when added to a page as a link address

    • Space shortcuts: If you have space shortcuts leading to pages in other spaces, they won’t appear in the cloud. Known issue: MIG-1608

    • Team Calendars

    • Watchers: Users watching a page or the content in a space

    • Save for later: Pages which have Save for later selected

  • Users and groups

  • App data: Marketplace Partners (also known as app vendors) need to provide an automated migration path for the Confluence Cloud Migration Assistant to migrate app data. Learn more about Confluence apps with migration paths

  • Global templates: Only global page templates and custom system templates are migrated. Learn how to migrate global templates

  • Macros: Some of the macros are migrated to the cloud.

  • Global settings and permissions: These will need to be configured manually in your cloud site.

  • Application links: If you plan to use Atlassian server products with your Confluence Cloud site, you can create two-way links between your Server and Cloud products. Learn how to link Atlassian products

  • User avatars: Users will need to update their avatars after migrating

  • Passwords: Unless you've set up SSO, users will need to reset their passwords after migrating

  • Personal drafts: Shared drafts are migrated, but not personal drafts.

  • Custom Emojis: You’ll have to recreate them in the cloud

  • Attachments when stored through the Confluence Mail Archiving plugin: You'll need to manually download and re-upload these attachments to your cloud site after the migration.

  • Attachments when added as a link address: When you copy the link address of an attachment from the Confluence server and add this copied address to a page, the attachment won't be migrated.

  • Activity Stream/'Recently Updated' view: Recently added or modified content, including pages, blog posts, mail messages and comments won’t be migrated.

  • Analytics data

  • Global PDF stylesheets

  • Profile information:

    • Personal: Phone, IM, Website

    • Company: Position, Department, Location

  • Audit logs: The audit logs on server instance are not migrated to the cloud.

  • Macros

The section Macros in the legacy editor only in the What are macros? topic shows the list of macros that are supported only in the legacy editor of the Confluence Cloud. These macros, if migrated from the server or Data Center, are only supported in the legacy editor of the Confluence Cloud. They’ll not work in the new editor of Confluence Cloud. Therefore, you’ll need to use alternative macros with similar functionality supported in the new editor of Confluence Cloud.

Team Calendar components that are not migrated

  • Internal subscriptions: In Confluence, a Team Calendar is linked to a specific space. Internal subscriptions lets a team view events from a different space's calendar, right inside their own Team Calendar. Internal subscriptions are not migrated. After migration, your Team Calendar will still have all its own events, but won't show the events from other spaces' calendars that you had subscribed to. To get those events back, you'll need to set up the internal subscriptions again in the cloud.

  • Jira linked Team Calendar events : Your Team Calendar can include events linked to Jira projects, these events help you visualize key dates from Jira. However, during the migration process, these Jira-linked events are not migrated correctly. The connection between your calendar and Jira changes in the migration process, and there events do not appear in cloud.

More information and support

We have a number of channels available to help you with your migration:

Still need help?

The Atlassian Community is here for you.
Ask the Community
On this pageWhat is migratedWhat isn't migratedMore information and support
CommunityQuestions, discussions, and articles