Migrate from Confluence to XWiki

XWiki SAS sells Confluence Migrator Pro as a paid extension, and its XWiki Store listing gives a starting price of 2000 EUR. The listing also offers a trial limited to 30 pages per migration, which lets you test mapping on a sample before buying. Confirm with XWiki SAS whether the quoted price covers one migration run or a license for a set period, whether it scales with the number of spaces, pages or attachments, and whether re-runs for cutover or delta imports are included. The license is a one-time purchase for the migration tooling, so it does not recur on its own.

The open-source XML filter stream is the component that Confluence Migrator Pro builds on, so it is free to use under XWiki's open-source licensing. The trade-off is effort: your team or a partner must script the import, map users and groups, handle attachments and permissions, and verify the results without the paid extension's packaged workflow. Estimate the internal engineering time for that work before comparing it with the license fee. Ask any integrator to state in writing which parts of the migration they will build and which they will test.

XWiki SAS lists consulting at 1200 EUR per day, and that rate requires a Business or Enterprise support plan. The support tier therefore becomes a precondition for this rate, so its recurring fee should be added to the consulting estimate. Ask XWiki SAS to confirm the number of consulting days needed for your spaces, macros, user directory and permission model, and whether the day rate applies to remote work, on-site work or both.

XWiki SAS lists training at 1500 EUR per day. Training is one-time for the people who will administer the wiki, but its value depends on how many administrators, content owners and power users you need to onboard. Teams with strong Java, Tomcat and database skills may need less formal training than teams who will build XWiki applications. Ask for a course outline that covers administration, permissions, macros and the migration workflow, and confirm whether training can be delivered on your own infrastructure.

Hosting is the main recurring infrastructure cost. It covers compute for the Tomcat application, a database (MySQL, PostgreSQL or MariaDB, depending on the official image variant you choose), storage for attachments, backups, monitoring, TLS certificates and network access. Costs rise with user count, attachment volume, the number of environments (staging and production are usually both needed), and availability targets. Get the hosting assumptions written into the quote, including whether they run in your cloud account, your data center or a provider's infrastructure.

Internal time is often the largest cost and is easy to underestimate. Your team must decide which Confluence spaces, pages and attachments to keep, assign owners, rebuild or review macros and Marketplace app content, confirm group and permission mapping, test sample pages and train authors. Content cleanup is one-time work, but it recurs in smaller amounts when old content is archived or re-imported. Ask any partner to list which cleanup tasks are in scope and which fall to your staff.

One-time costs include the migrator license, migration engineering, content cleanup and initial training. Recurring costs include the XWiki support subscription, hosting, backups, upgrades, security patching and the admin time to run the wiki. A written quote should separate these lines, state the scope in writing, name the Confluence edition and backup formats covered, list the spaces and page counts assumed, explain what is excluded (such as attachment history, which the migrator does not preserve), and give payment and change-request terms. Ask for the upgrade path between XWiki release lines, since stable and LTS versions follow different schedules.

The cost has three parts: the XWiki software, the migration tooling, and the people who do the work. XWiki Standard is free and open source under the LGPL 2.1, so there is no licence fee for the core platform. The Confluence Migrator Pro from XWiki SAS is a paid extension, and the XWiki Store lists it from 2000 EUR, with a trial limited to 30 pages per migration. Open-source XML filter use avoids that fee but shifts more work to your team. Ask any quote to separate one-time migration effort from recurring hosting, support subscriptions and admin time.

The duration depends on the number of spaces, pages, attachments and users, how many macros and custom apps need rework, and how many test cycles your business requires. None of those factors has a fixed duration in the sources we rely on, so no single timeline applies. Ask for a timeline tied to a written scope that lists the spaces in wave one, a pilot space, and the acceptance criteria for each cutover step.

Your team needs to supply a Confluence export or backup, access to the source site for user and group data, and business owners who can confirm which spaces, permissions and pages must stay. Engineers should be ready to check macros, Marketplace apps and internal links, which rarely convert without review. Plan for an identity contact who can map users and groups to the new directory or sign-in method, and a named owner who signs off on each space.

Yes, if your team has administrators comfortable with Tomcat, the chosen database, and XWiki's import tooling, and time to test. XWiki publishes official Docker images in MySQL, PostgreSQL and MariaDB variants, which helps a self-managed build. Teams without that experience often bring in an implementation partner for the migration, hardening and backup setup. DeployOpen plans, implements and supports self-hosted open-source platforms in your own infrastructure under a written, fixed scope, and can quote that work separately from any XWiki SAS services you choose.

No. The Confluence Migrator Pro keeps page history but does not preserve attachment history, so older versions of attached files are not carried into XWiki according to the XWiki Store. Confirm this against your Confluence edition and export format before cutover. If older attachment versions matter for audit or records, keep a copy of the source backup and the original files in archive storage, and agree in the written scope how those files will be retained and found.

It can be enough for simple content, but it is a component rather than a finished migration tool. The XWiki Confluence Migrator Pro builds on the open-source Confluence XML filter stream and adds the packaged import workflow, support, and coverage of pages, spaces, attachments, permissions, blog posts, and users and groups. Use the open filter if your team can write and test its mapping, and compare its output against a Migrator Pro trial on a representative space before deciding.

Confluence stays in place until you decommission it, so plan the retirement as its own step. Atlassian ends support for Confluence Cloud XML site and space export on December 1, 2026, and recommends CSV export after that date, so any XML backup you rely on should be taken and archived before then. Data Center licences expire and become read-only on March 28, 2029. Confirm with Atlassian which export and retention options apply to your edition, and agree in writing how read-only access, archives and user redirects will be handled.