Prevent vendor lock-in when migrating from Confluence?

[Mali]

Hi, how can I migrate Confluence pages to a XWiki page in the general XWiki 2.1 syntax?
I know about the options to import backups with Confluence Migrator Toolkit. The problem I see is that the migrations extensions create pages in a new confluence page syntax it provides.
I am aware that not every page element and style has an equivalent in the XWiki syntax. This is the reason bridge macros exist.
But in my opinion, you are going from a vendor lock-in from Atlantassian to XWiki SAS when you rely on a subscription of the Confluence Migration Toolkit to have your “migrated” Confluence pages in XWiki.

What are the options except from manual migration (copying texts and images by hand)?

[vmassol]

@Mali

Hi, how can I migrate Confluence pages to a XWiki page in the general XWiki 2.1 syntax?

Are you sure it doesn’t convert to XWiki 2.1 syntax?

@Mali

But in my opinion, you are going from a vendor lock-in from Atlantassian to XWiki SAS when you rely on a subscription of the Confluence Migration Toolkit to have your “migrated” Confluence pages in XWiki.

Several points:

1. There’s no reliance on any subscription if you don’t want to (except if you use the Pro Confluence migrator from Confluence Migration Toolkit - XWiki Store). The default confluence migrator is open source and free. See GitHub - xwiki-contrib/confluence: Various Atlassian Confluence related tools · GitHub
2. The confluence syntax is also open source and free. It’s a contrib extension. See GitHub - xwiki-contrib/confluence: Various Atlassian Confluence related tools · GitHub

Note that this forum is for xwiki.org. If you need information about Confluence Migration Toolkit - XWiki Store (which is not part of xwiki.org), please contact the XWiki SAS company.

Hope it helps

[CycleSEC]

@Mali

What are the options except from manual migration (copying texts and images by hand)?

That largely depends on which macros and plugins are used in your Confluence instance. In many cases, it’s not just about migrating the visible content, but also the underlying business logic implemented by plugins or custom code. Bridge macros are therefore often only one part of the overall effort.

You can also create your own bridge macros (we’ve done this for more than 30 Confluence macros already). For many layout-related macros, a simple macro that mainly renders the contained content using {{wikimacrocontent/}} is often sufficient.

The overall effort depends on how many macros need to be migrated and how complex their parameters and behavior are.

[tmortagne]

@Mali

Hi, how can I migrate Confluence pages to a XWiki page in the general XWiki 2.1 syntax?

I think you are mixing two different things here. Confluence syntax is converted to xwiki/2.1 syntax, but some Confluence macro that don’t have equivalent (or at least for which the equivalent have a different behavior) in XWiki Standard are just converted to placeholders that someone has to implement at some point. You are free to implement them. See more details regarding the macro aspect of things in https://www.xwiki.org/xwiki/bin/view/documentation/extensions/dev/confluence/write-macro-converters/.

XWiki SAS has put a lot of effort into providing various implementations for very Confluence specific macros, not to mention stuff coming from Confluence addons, and they are charging for that.