Migrate Translations for Confluence to Cloud
Please refer to our main documentation for the Migration Assistant for general instructions on how to migrate bitvoodoo apps.
The following information is specific for the app "Translations for Confluence".
Before you migrate: Assess macro usage within language macros
The app Translations for Confluence is completely cloud-ready. However, Confluence Cloud has limitations regarding nesting macros (rich body & 3rd party macros).
For details on nesting of all Confluence macros, please consult the page nesting macros in language macros.
We strongly recommend that you address the following points before starting the migration:
Are you using other macros (standard or 3rd party) within language macros?
Will you use the old (Legacy) editor or switch to the new Cloud editor in the future?
Based on this assessment, you might have to rework the content on your Server/DC instance before the migration. Use as few “fancy” macros as possible on your pages. Also, use the remaining macros separately on the page instead of nesting them within language macros. See our Best Practices guide.
Migration process
Migrating Translations for Confluence to Confluence Cloud is easy.
Install Translations for Confluence in your cloud instance.
Use the Atlassian Migration Assistant as described on this page.
That's it! The different language macros and their content are now in the cloud. For differences in the functions and UX, see the table below.
Feature comparison between Translation Server/DC and Cloud
Feature | Server/DC | Cloud | Notes |
|---|---|---|---|
>40 languages | More than 40 language macros at your disposal | More than 40 language macros at your disposal | |
Translate page title | Possible with our built-in tool | Not possible | For technical reasons, it's not possible to translate page titles in Cloud. Nobody regrets this as much as we do 🙁. |
Nested macros | Complex nesting structures are possible | Very restricted in Confluence Cloud; necessary to restructure and simplify pages | See Nesting macros in language macros and Best Practices when using Translations for Confluence Cloud |
Change language | Language dropdown in the page header  | Language dropdown in the page header  | The Cloud dropdown will only appear if there are at least 2 language macros on the page. |
Language detection | The app will choose which language to display in this order:
For details, see this page. | The app will choose which language to display in this order:
For details, see this page. | The Cloud logic is very similar to Server/DC since June 2021. |
Connection to JSM | Fully translated knowledge base: content and titles For details, see this page. | Content is translated, page title remains For details, see this page. | |
Export to PDF/Word | Possible to export language-specific content or all languages. | Possible since June 2021, see this page. |
Translated page titles will not be migrated to Cloud. See