General App Documentation
General App Documentation
Breadcrumbs

Cloud Migration Hub: Translations for Confluence

Cloud Migration – Translations for Confluence

Atlassian is ending support for Confluence Data Center by March 2029.
This page explains how Translations for Confluence will be migrated from Confluence Data Center to Confluence Cloud, what you need to prepare, and what you can expect.

🔎 Quick overview

Question

Answer for Translations for Confluence

Migration effort and automation level

Low to Medium - Usually one migration run with some manual validation and content adjustment due to nesting macro limitations.
Partially automated – The Atlassian Migration Assistant handles most app data, but you may need to adjust nested macros and page titles manually.

Main risks/limitations

  • Page titles translations are not supported in Cloud, and any translated titles in DC will not be migrated.

  • Complex nested macros may fail or require manual restructuring due to the Cloud's stricter nesting rules.

  • Some functional differences remain between DC and Cloud (e.g., real-time translation via Atlassian Intelligence vs no native auto-translation in DC).

Feature comparison between Translation DC and Cloud

Key prerequisites

  • Install Translations for Confluence in the destination Confluence Cloud instance before migrating.

  • Use the Atlassian Migration Assistant (Cloud Migration Assistant) to run the migration.

  • Assess pages for nested macros within language macros; simplify as needed before migrating.

  • Validate any content that uses special macros or rich body macros that might not be Cloud-compatible.

Best practice

  • User impact during migration:
    We recommend that pages be set to read-only for authors during the migration to prevent conflicting edits and ensure consistent language macro structure.

  • Typical duration:
    From a few minutes up to several hours, depending on the number of pages and the extent of macro nesting that requires adjustment.

  • Best practice:
    Perform the migration during a maintenance window / off-peak hours. Review pages with complex nested macros in advance, and consider a small pilot first.

Available Cloud types

Translations for Confluence is available on Commercial Cloud.

info What Translations for Confluence does

Translations for Confluence Cloud enable users to add, edit, and display multilingual content on one page. It supports over 40 languages via language macros, automatically showing content in users' preferred language, eliminating duplicate pages and improving global knowledge sharing.


This section explains how your Translations for Confluence data and configuration move from Data Center to Cloud.

🔄 How to migrate

Please unfold the sections below to view the complete, detailed instructions for the upcoming migration.

By expanding these folders, you will gain access to all the necessary steps and guidelines for a smooth, successful migration.

Before you start

Use this checklist before planning the migration.

Supported versions

  • Minimum Translations for Confluence version on Data Center: 7.0.0

  • Supported Confluence Data Center versions: 10.0.1 - 10.2.6

  • Translations for Confluence on Cloud: Link to Marketplace

Preparation

  • Create a full backup of your Confluence instance.

  • Update Translations for Confluence to the latest Server/DC version.

  • (Recommended) Use a test/staging environment to trial the migration.

  • Inform users about possible read-only mode or short downtime during migration.

  • Review known Cloud limitations regarding macro nesting.

  • Link to feature parity / known limitations

How the migration works

📖 Migration approach

Using Atlassian migration tools (recommended)

  • Use the Confluence Cloud Migration Assistant (CCMA) to migrate pages that include language macros (translations).

  • App-specific export/import: Not necessary – translation macros and content are stored in the page content and are migrated with standard content migration.

  • Recommended option for most customers:
    Use the Cloud Migration Assistant with translation macros included. This automates transferring macros and content. Only content with nested unsupported macros may need review or manual restructuring before/after migration.

🔢 Step‑by‑step

Step 1 – Prepare on Data Center

  • Check Confluence and Translations for Confluence versions; update if needed.

  • Create and verify a Confluence backup.

  • (Optional) Run a test migration in a staging environment.

  • Communicate migration timing and impact to users.

Step 2 – Run the migration

  • If using Atlassian migration tools:

    1. Start the migration wizard.

    2. Select spaces and include content with translation macros.

    3. Start the migration and monitor progress.

  • If manual export/import is needed (rare):

    1. Migrate pages via standard content export/import.

    2. Install Translations for Confluence on Cloud.

    3. Verify pages and translated content post-migration.

Step 3 – After the migration in Cloud

  • Check that language macros and translated content are present and correctly rendered.

  • Adjust Cloud-specific settings if needed (e.g., macro layout, display options).

  • Inform users that translations in Cloud are ready to use.

After Migration

🎉 Congratulations! You have successfully migrated Translations for Confluence from Data Center to Cloud.

Reference / Blog:

🤝 Support & resources

❓ FAQ for Translations for Confluence migration

  • Can users continue working while the migration runs?
    We recommend read-only mode for affected spaces/pages during the migration to prevent inconsistent edits and structural issues with nested macros.

    What is not migrated automatically?

    • Translated page titles (not supported in Cloud).

    • Complex nested macros may require manual restructuring.

    What are the biggest changes compared to Data Center?

    • No support for page title translations in Cloud.

    • Nested macro structures are more constrained in the Cloud and may require manual adjustments.

    • Auto-translation support differs. Cloud relies on Atlassian Intelligence features.

  • Are you a solution partner and have questions about licensing during migration?
    Contact us via Partner Fast Lane