Data from Confluence (Data Center) can be automatically imported into Phonemos. We have a migration plugin that can be added to Confluence.
Do you need to migrate data from Confluence (Cloud)? This is possible, too, please reach out to us.
For each Confluence space you may select what pages to migrate and whether the number of historic revisions should be limited or complete.
Migration will preserve most of the formatting, page history, users in the change history, attachments and embedded media fiels. For each import into Phonemos, content is first kept in an isolated area that is not visible to non-admin users. There, the migration result can be reviewed, manually adjusted and committed (made visible for users) once everything looks right.
Migration path per Confluence (Data Center) artifact
The following table gives an overview of the current migration support. Please reach out to us if you require additional support.
We distinguish between feature and migration support. Feature support means, that we have replacement functionality in Phonemos that does the same or similar functionality for that purpose. Migration support means, that the migration of these Confluence artifacts into the replacement functionality in Phonemos is automatic, semi-automatic or manual.
Confluence Artifact | Phonemos Feature Support | Phonemos Migration Support |
|---|---|---|
Confluence Standard Features |
|
|
Space configuration (Permissions etc.) | ℹ️ permissions very similar, other space configuration deviates 💡Phonemos supports a custom menu navigation configuration; this is not possible in Confluence 💡Phonemos supports multiple language schemes to choose from; this is not possible in Confluence | 🛠️ these settings need to be reconfigured manually |
Page incl. history | ✅ Page incl. history ℹ️ we currently do not store a commit comment per version ℹ️ we currently have no visual diff between page versions | ✅ automatic |
Calendars and calendar entries | 🚫 not supported | 🚫 not supported |
Page templates | ✅ 💡Phonemos supports entire page trees as template, not just single pages | 🛠️ manual transfer required |
User macros | 🚫 | 🚫 |
Personal space | ✅ ℹ️ personal note areas in Phonemos are always private | 🛠️ Migration as a standard space possible, pages can then be moved manually into personal note areas if they shall be private |
Comments | ✅ | 🛠️ We currently convert them just into text and add them to the end of the page content |
Use as Jira Service Management knowledge base | 🚫 as this is now bundled into the Jira SM subscription at no additional price and the technical integration is tight, we cannot easily implement this and probably there is no demand (since free with Jira SM) | 🚫 |
Notifications | ℹ️ support coming with Phonemos Workflows & automation | 🚫 |
Confluence Companion (easier way to open office files) | 🚫 proof of concept ready, but not yet a priority in our roadmap | 🚫 |
Analytics for page views | 🚫 statistical data already collected, but reporting not yet a priority in our roadmap | 🚫 no analytics data is transferred |
Confluence built-in macros |
|
|
Embedded pictures | ✅ 💡Phonemos will automatically OCR pictures and make pictures searchable; this is not possible in Confluence | ✅ sometimes some sizing issues when Confluence does not save sizing information, but has different defaults |
Embedded videos | ✅ | ✅ |
Embedded Office files And PDF | ✅ | ✅ |
Children | ✅ | ✅ |
Page properties and page propertiy reports | ✅ with metadata and data table gadget (requires Plan business) 💡metadata is much more structured in Phonemos and we have additional tools to work with metadata | ✅ automatic 🛠️ as page properties are plain text, there can be typos or inconsistencies in Confluence that you might want to fix before or during migration. We can support with a custom migration script. |
Panel | ✅ with Note ℹ️ does not exist as an own gadget separate from Note | ❓needs checking |
Section and column | ✅ | ✅ works for Confluence layouts 🛠️ does not work for legacy section and column macros |
No format | 🚫 no specialized gadget | ✅ Will just migrate the text |
Code block | ✅ | ✅ |
Expand | ✅ ℹ️ we cannot embed all content types in expand | ✅ |
Quote | ✅ | ✅ |
Anchor | 🚫 does not exist, but every heading automatically has an anchor | 🚫 |
Table of contents | ✅ Every page has automatically a table of content in the right side pane ℹ️ we cannot embed a table of contents in the page itself | 🚫 not needed |
Page tree | 🚫 no support planned | 🚫 |
Page tree search | 🚫 no support planned | 🚫 |
Include page | ✅ | ❓needs checking |
Attachments | ✅ | ✅ |
Blog posts | ✅ Announcement | 🛠️ Currently migrated to pages, not into announcement posts |
Content report table | 🚫 no support planned | 🚫 |
Recently updated | ✅ | ❓needs checking |
Live search | ✅ through standard search 🚫 no support for embedded search field in page | 🚫 |
Status | ✅ | ✅ |
Jira issues | ✅ (Requires plan Business) | ✅ |
Gallery | 🚫 | 🚫 |
User profile | 🚫 | 🚫 |
User list | 🚫 | 🚫 |
Task list | ✅ | 🛠️ will need manual configuration as filtering works different |
Create page from template | ✅ | 🛠️ manual |
Third-party Confluence plugins |
|
|
✅ through diagrams.net | ✅ | |
Gliffy | ✅ through diagrams.net | ✅ Yes, but indirectly |
Easy translator | ✅ requires plan Business | ✅ no additional data needs to be migrated |
Stagil Navigation | ✅ | 🛠️ needs to be set up manually |
Page tree creator | ✅ | 🛠️ needs to be set up manually with templates |
PDF export for pages | ✅ | ✅ no migration required |
Scroll Viewport | ✅ as a paid option | 🛠️ needs to be set up manually |
Comala Metadata | ✅ requires plan Business | 🛠️ needs to be migrated manually |
Community Forums | ✅ requires plan Business | 🛠️ needs to be migrated manually |
Scroll Word Export | ✅ | 🛠️ templates need to be set up manually |
Scroll PDF Export | ✅ | 🛠️ templates need to be set up manually |
Scroll Document Management | ℹ️ partial support added with Workflows for Phonemos | 🛠️ needs to be set up manually |
Youtrack issue integration | ✅ | 🛠️ manual |