Cloud
-
What will my cloud subscription cost?
Our cloud pricing starts at 1 €/user/month at the starter level. The pricing varies depending on the number of users and the service level.
Please check out the pricing page to see the exact cost for your needs. Note that Confluence migrations are available only for the Business and Enterprise plans.
-
Can I try XWiki Cloud for free?
Sure. You can try an XWiki demo by going to try.xwiki.com and create a free test instance (no credit card required). You have 4 hours to validate the instance in order to have a 10-day trial. You can also extend your trial 2 more times. This way, you get a total of 30 trial days.
-
Can I extend my cloud trial?
You can extend your trial another 2 times. You get a total of 3 trials, 10 days each.
-
Can I convert my trial into a paid instance and keep my data?
Yes. When you make a purchase, you'll have the possibility to click a checkbox saying "I want to keep my DEMO data".
-
What is a user and how are users counted towards billing?
A user is any user that can log in to XWiki and exists in the Users Administration. Logged out visitors or inactive/disabled users are not counted towards the number of users.
-
How can I purchase a cloud instance?
To purchase a cloud instance you should
#1 Create a cloud demo from the XWiki website. You will get an email to validate your cloud instance.

#2 You will be directed to the shop, from which you can select the cloud offering.

#3 After that you can select the number of users and the support level.

#4 After clicking “Buy” you will be able to make the purchase.
After the purchase, you will receive a confirmation for your order (and the receipt) by email.
-
If XWiki is free and open-source, why should I pay for an XWiki Pro package?
XWiki Standard, the community version, is great for people who can install, run and customize the wiki all by themselves. With the XWiki Pro package, you enjoy both the benefits of open-source and the customization, support, and stability that your enterprise needs.
- It comes with a full set of productivity and business-oriented applications that extend the product functionality.
- Where the Standard version relies on forum-based help from the community, XWiki Pro includes expert technical support and patches for both your wiki and the licensed applications.
- If you opt for the Cloud, you also benefit from hosting, updates, upgrades, and backups.
- Last, but not least, by purchasing XWiki Pro you support our sustainable open-source cycle. Revenues go towards improvements in the open-source product which are then brought back to our clients through upgrades.
-
What payment methods do you accept?
You can pay by credit card via Stripe or Paypal, in which case online (30% discounted) pricing applies.
We also accept payment via wire transfer, for which standard prices apply. We recommend this second option only if the payment exceeds your country's or company's financial legal limit or if you'd like to discuss additional or different contract clauses.
-
Can I set up subscriptions (recurring payments)?
Yes, recurring payments are available through Stripe and PayPal. Make sure that the account that you want to use has sufficient funds.
When you are placing an XWiki Cloud order, you need to select the "Subscription" box and continue with the purchase steps. Note that PayPal supports subscriptions with a maximum renewal frequency of 1 year, while Stripe supports multi year subscriptions.
-
Can I get a refund?
Yes, you can get a refund for XWiki Cloud during the first month for monthly subscriptions and within 30 days of payment for annual subscriptions.
-
How can I cancel my subscription?
There are several situations when you would need to cancel your current subscription:
- you don't want to renew your XWiki Cloud instance,
- you want to switch to a manual renewal process,
- or you want to change the PayPal account through which you want to manage your wiki's automatic renewal.
You can cancel your subscription by going to your XWiki Network account from your wiki instance (from the top right menu icon "?"), on the Subscriptions tab.
There, access your current active subscription and click on the "Cancel Subscription" button.
If you wanted to not renew, you don't need to do anything else. Your wiki will expire and it will not be renewed automatically anymore.
If you wanted you to switch to a manual renewal process, then, make sure to renew before the expiration date. Check out the renewal dedicated entry: How can I renew a cloud instance?
If you need to change the PayPal account through which you want to manage your wiki's Cloud automatic renewal, after you cancelled the current subscription, you need to access the Shop, select "XWiki Cloud", pick the support level and duration and continue the purchase process.
These steps are also described in the usual XWiki Cloud purchase process described in the section How can I purchase a cloud instance?
Don't forget to select the Subscription option in the generated order so that you set your new subscription. Then, finish the purchase process following the needed steps (for example, you will be required to fill in the data of the PayPal account that you want to use).
If you need assistance with cancelling a subscription, don't hesitate to contact us or create a ticket on the XWiki Network.
-
How can I renew a cloud instance?
If you need to renew your cloud instance and you don't have automatic payment through a subscription, you just need to click on the "?" icon at the top right of your instance, on the "Buy or Renew" option.
You will be then directed to the XWiki Network portal where you will see a shop page with your latest paid order, usually helpful when you want to renew with no change in plan.
Then follow the regular purchase process.
-
How can I upgrade / downgrade my plan?
If you already have a cloud plan, but your needs have changed and you wish to upgrade or downgrade your plan, you can make a new purchase according to your needs.
The remaining time from your prior plan will be converted to the price of the new plan that you select. This will result in the extra days being added to the expiration date of the new plan.
Steps to follow:
#1 Click on the "?" button in the top right corner of your wiki and then choose "Buy or Renew".
You will be then directed to the XWiki Network portal where you will see a shop page with your latest paid order, usually helpful when you want to renew with no change in plan.
However if you need to change either the level of support or the number of users, you would need to click on the "remove item" to first remove this order from the cart and start a new order with the desired options.

#2 Then you are invited to go to the Shop where you can choose the new plan.

#3 Select the desired support level, the number of users and the duration of the hosting

Please note that as a protective measure, when needing to upgrade or downgrade your plan and you have an active subscription, you would first need to cancel it before ordering a new subscription with the desired plan options.
This step is not currently automatic as a client protective measure imposed by PayPal in order to avoid providers (in this case XWiki SAS) having direct access to your bank account. See the How can I cancel my subscription? in case of need
-
My business is based outside France. How to I avoid being charged for VAT?
As a VAT registered business in France, we charge VAT to non-VAT customers in the EU.
We don't charge customers in the EU who are VAT-registered. To avoid being charged please fill in your VAT Registration Number in your Company information, in the XWiki Shop Profile.
-
How do I transfer my XWiki Cloud subscription to another user?
To tranfer your XWiki Cloud subscription to another user (XNNG account), you'll have to go through the following steps:
- Log into XNNG: Access the XWiki Network Management interface (XNNG) using your current account credentials.
- Subscribe: If you haven’t already, subscribe to the XWiki Cloud service.
- Create a new user on the XWiki instance: In your XWiki instance, create a new user account that will receive the subscription transfer.
- Add the new user to the Network Paying group: Make sure the new user is added to the Network Paying group to grant them the necessary permissions.
- Cancel the subscription: Cancel the current subscription associated with your old account.
- Log into XNNG with the new user: Use the "?" button on the XWiki instance to log into XNNG with the new user account, which is part of the Network Paying group.
- Create a new subscription: When you access the "Buy/Renew" section from the "?" button, the new order will be pre-generated based on your existing plan. You just need to continue with the purchase process.
- Pay for the new subscription: Complete the payment process for the new subscription. Note that the new subscription will be charged immediately, and the days remaining from your previous order (if existing) will be added to your subscription.
-
Do you offer any special discounts?
Yes! We offer a 50% discount for all of our services for NGOs and open-source projects. Moreover, we offer free Starter level Cloud instances and free Pro Apps licenses (without support) for open-source projects. If you're an NGO or an open-source project looking to use Pro Apps, please get in touch with us.
-
How can I benefit from the free offer for open source projects?
Open source projects that request a cloud wiki, will be able to host their wikis with XWiki SAS at the Starter level and receive regular updates (technical support not included).
Open source projects may also request free licenses for XWiki Pro apps. Projects that wish to create a cloud wiki or ask for Pro app licenses, should meet the following criteria :
- the project should be licensed under a license listed on the Open Source Initiative website
- the project source code should be available for download
- the wiki instance on XWiki Cloud should be accessible to the public
- the request should be made by the project lead or a committer
To apply for a cloud wiki all you have to do is fill in the form on the Try XWiki page and create a new cloud demo instance. In the form, you should specify the following information:
- the project name, URL and a short description
- the open source license used
- a link from where the source code can be downloaded
Once you've filled in the information and created your instance, we'll reach out to you as soon as possible to validate your request.
-
What is the difference between cloud support and the open source community support?
Community support is given by the XWiki community members in their free time. There is no guarantee you will receive an answer or that the answer you receive will be the best course of action for your situation. Choosing professional support services guarantees that your issues will be tacked by the XWiki SAS team in a timely manner, under a SLA.
-
How can I contact the XWiki Support Team?
To contact XWiki Support, you should create a ticket on XWiki Network (click the question mark icon at the top of your wiki as seen below, then click "Report an issue").

You can also send us an email to support@xwiki.com.
When reporting an issue:
- Prepare a minimum reproducible case (steps to reproduce)
- Include error messages and the events or actions leading up to the problem
You should also provide:
- The link to the affected page
- A screenshot highlighting the issue
- The full error-message (if one is displayed)
- Browser details
-
How do I report a product bug or a feature request?
For XWiki related bugs or feature requests, please use the XWiki open source project's Jira tracking software.
For Pro Apps, you can use either GitHub issues or the feedback form found on the XWiki Store page for that particular Pro App.
If you have an active subscription (XWiki Cloud, individual Pro Apps or support on premise) please report bugs through the XWiki Support Network.
-
How do I get a license for Pro Apps if I'm a Basic+ customer?
XWiki Cloud does not come with Pro Apps installed by default. We prefer to give our clients the choice of whether they want to install them or not on their wiki. To get the license for all Pro Apps please install XWiki Pro, then contact our support team to activate it.
-
What does support for XWiki Pro include?
Support for XWiki Pro includes:
- Technical support for the Pro Apps
- Technical support for your XWiki instance
-
How often will my wiki be upgraded to a recent version?
We upgrade cloud wikis proactively once per year. If you're interested in an earlier upgrade please contact our support team. The upgrade might still be feasible, but we would need to do an analysis before we can confirm it.
-
How do I set up my custom server name if I'm a Basic+ customer?
Our Basic+ XWiki Cloud users benefit from custom server names. When setting up a custom server, the first thing to consider is purchasing a security certificate. It's important to note that you own this custom domain, which is why we request from you the security certificate that will be used to provide a secure connection.
After you send this to our support team, there is one setting you'll need to add to your instance (your wiki's CNAME should point to "cloud.xwiki.com." - the final dot is important :) ). Finally, please recontact the support team so we can make the final settings.
-
How do I clear storage on my Cloud wiki?
There are cases when the storage available with the purchased Cloud plan is exceeded and in that case, actions on the wiki could be limited to only viewing wiki pages.
In this situation, there are several options to obtain more storage:
A. Go to Page Index > Deleted Pages and delete those pages, either one by one or with a click on Delete All button. Repeat this step on subwikis, if existent.
B. Go to Page Index (https://yourwiki/xwiki/bin/view/Main/AllDocs) > Deleted Attachments and delete those files. Repeat this step on subwikis, if existent.
C. Go to Page Index (https://yourwiki/xwiki/bin/view/Main/AllDocs) > Attachments and check the largest files currently attached to your wiki pages and add compressed versions of large images and videos, delete large image or video versions (including from Deleted Attachments).
Also, make sure to not keep the same video file, for example, on multiple locations on a wiki. Repeat this step on subwikis, if existent.
D. If you have subwikis, go to Wiki Index (https://yourwiki/xwiki/bin/view/WikiManager/) and delete the subwikis that you no longer use.
If none of the above steps offer enough storage, there is also the option to purchase more by selecting a higher user tier or a higher support level in the XWiki Network portal's shop.
Check the section How can I upgrade / downgrade my plan? to see how to switch to a different support level or user tier.
-
How do I import existing data from my on premise instance to cloud?
When you do an import to your cloud instance please import only the content from your exported package, so you don't overwrite standard XWiki pages.
To achieve this you should:
- Go to Administration > Import
- Upload the backup package
- Click on the package, then click "select none"
- Check only the content pages that you need to migrate from one wiki to the other
- From the XWiki space, select only the users and groups
- Click "Import"
After doing the import you should test that the wiki works as expected (e.g. look at whether you can view/edit the imported pages, whether they look OK, check if the users section in the global administration displays the users properly etc.)
For more complex imports from XWiki or other tools we also offer dedicated data import services.
-
How is my data hosted and secured?
Our cloud services are hosted with OVH, in France. OVH is ISO 27001, SOC 1, SOC 2 and GDPR compliant. Security fixes will also be applied to your wiki, either on instance upgrade or through security patches. Additionally, instances come with the Antivirus app preinstalled, which protects attachments uploaded to XWiki pages by scanning them for viruses and malware infections.
-
What is the Admin Tools Pro Application?
The Admin Tools Pro Application works for on premise and Cloud instances and offers advanced administration features within a friendly user interface.
Among the main features you will find: easy access to configuration files and logs, information about the environment in which XWiki is hosted, basic instance usage statistics and the ability to initiate health checks.
-
What is the Analytics Pro Application and how does it work?
The Analytics Pro Application is a tool that provides real-time statistics about the usage of your instance. In order to use the Analytics Pro Application you must setup your own Matomo server, on premise or in their cloud.
For XWiki Cloud Demos, a trial Matomo server will be provided by XWiki SAS for testing purposes. After conversion from XWiki Cloud Demo to Production instance, the trial Matomo server is discontinued and you need to create and manage your own.
Pro Apps
-
How can I install Pro apps from the XWiki store?
You can install the apps from the Extension Manager in your XWiki instance. More information on how to install applications is displayed on each app page in the "Installation" tab. Some applications might require additional configurations, which are usually detailed in the same tab.
-
What if I already have an old non-Pro app installed?
If you already have an old non-pro app installed, you may need to uninstall it before installing the new pro app. We recommend that you contact us, so we can help with your specific use case.
-
Are the apps on the XWiki store open-source?
The applications on the XWiki Store are open-source, but not all of them are free. You can build them from the source with the appropriate technical knowledge. You can find the sources linked on the store from each app page.
The extension repository is maintained by XWiki SAS, not by the XWiki open-source project. XWiki SAS decided to introduce pro apps in order to help sponsor the development of the open-source project.
-
How much do Pro apps cost and how are users counted?
The pricing is listed on every app page in the "Pricing" tab and varies according to the number of users. The apps are sold as a yearly license.
They are billed/counted based on the number of active users (with a user account that's not set as disabled/inactive) in your wiki. The app tier should match the user tier in the XWiki administration, even if fewer users will want to use the app.
For clients who already have an XWiki support plan (on cloud or on-premise), the apps are free starting with the Silver level.
-
What is included in an individual Pro app purchase?
In addition to the app you also get support for the app at the Silver or Gold level, depending on your purchase. By buying an app, you are helping sponsor the development of the open-source project.
-
If XWiki is free and open-source, why should I pay for an XWiki Pro package?
XWiki Standard, the community version, is great for people who can install, run and customize the wiki all by themselves. With the XWiki Pro package, you enjoy both the benefits of open-source and the customization, support, and stability that your enterprise needs.
- It comes with a full set of productivity and business-oriented applications that extend the product functionality.
- Where the Standard version relies on forum-based help from the community, XWiki Pro includes expert technical support and patches for both your wiki and the licensed applications.
- If you opt for the Cloud, you also benefit from hosting, updates, upgrades, and backups.
- Last, but not least, by purchasing XWiki Pro you support our sustainable open-source cycle. Revenues go towards improvements in the open-source product which are then brought back to our clients through upgrades.
-
How can I purchase a Pro app?
To make a purchase go to your XWiki instance in XWiki Administration > Extensions > Licenses. Click on the "Buy" button corresponding to the app you're planning to buy. You will be directed to the store. From there you can create the "Purchase order" and make the payment through the shop.
-
How do I renew a Pro app subscription?
To renew an app subscription in your XWiki instance, please go to XWiki Administration > Extensions > Licenses. Click on the "Buy" button corresponding to the app you're planning to renew. You will be directed to the store. From there you can create the "Purchase order" and make the payment through the XNNG shop.
-
How do I upgrade a Pro App to the latest version?
To upgrade a pro app please go to the XWiki Global Administration > Extensions and search for your app. If you do not have the latest version installed, you will see an "Upgrade" button next to "Show details". Click "Upgrade" and "Continue" and you should be done.
If you see the "Uninstall" button next to "Show details", it means your application is already up to date. If you encounter any issues upgrading your application please contact us.
-
How do I get support for Pro Apps?
To get support for an application you can either create a ticket directly in XNNG (The XWiki Network) , or write an email to support@xwiki.com as long as you have a valid license for a Pro App.
-
How can I suggest improvements or leave feedback for Pro apps?
To suggest improvements or leave feedback, please go to the XWiki Store page of the specific application. There, you can either use the "Description" section to find a link to the GitHub Issues for that specific application, or you can use the "Feedback" section to access a feedback form directly on the page.
-
Pro Macros license issues
Up until August 2024, the Pro Macros module contained both generic Pro Macros and Confluence Bridge Macros to be used in the context of Confluence Migrations.
Due to the growing number of macros and the different usecases that they addressed, the two sets of macros were split into "Pro Macros" = generic pro macros, to be used for any knowledge management need in order to enhance the creation and presentation of data, and "Confluence Bridge Macros" = macros inspired by their Confluence counterpart, to be used to display data migrated from Confluence.
Confluence Bridge Macros should not be used post migration and their XWiki alternative is preferred for further creation and edition of content.
If you have purchased the Pro Macros module before August 2024, you will see it appearing in your Administration - Extensions section under the name "Pro Macros Legacy". You can continue to renew the license for this module, as it is being kept up to date.
If you are a new client and wish to use the generic Pro Macros, please install and obtain a license for "Pro Macros".
If you are a new client that intents to migrate from Confluence to XWiki, please install the Confluence Migration Toolkit, which contains all apps and dependencies required for this need, including the Confluence Bridge Macros. The Confluence Bridge Macros can not be purchased individually.
If you have any issues with your Pro Macros or Pro Macros Legacy license please contact us via the dedicated support platform or e-mail.
-
Security Policy
If you have found security issues related to any of our XWiki Pro Applications, please follow the procedures outlined in the Security Policy to safely disclose said issues to our team.
-
I'm running an older version of XWiki that is no longer supported by a Pro app. How can I ask for a bug fix?
The recommended way to benefit from the bug fix is to upgrade XWiki to a supported version, then update the app. If upgrading the wiki is not an option, you should contact our support team through the methods outlined above to discuss about backporting the fix for your application version.
-
Can I customize Pro Apps?
Pro Apps are standalone, standard extensions, that are ment to be used out of the box, and not customized.
Customizing a Pro App will result in the loss of proffessional support on the extension and potential issues while upgrading to a new version of the app or the core product.
If you would like to recommend a new feature or an improvement, please open a ticket in the application's repository or fill in the feedback form present in the "FEEDBACK" tab of each application page on our store. If you are unsure on how to achieve a certain behaviour, or if a feature exists, please open a support ticket through the dedicated support portal.
-
Can I copy or edit Pro App pages?
Due to the architecture of the product, administrators are able to copy the homepage and other code pages of Pro Apps. This action is not part of the expected and normal usage of Pro App and is, therefore, not supported.
Any unexpected behaviour that results from copying or modifying Pro Apps pages will not be covered by our support services (individual app license or full support plan).
If you are unsure on how to achieve a certain behaviour, or if a feature exists, please open a support ticket through the dedicated support portal.
Migrate from Confluence
-
Do you have intranet functionality alongside the wiki, similar to Linchpin for Confluence?
Yes, but the approach is different. XWiki is frequently used to build intranets as a configurable platform.
Linchpin is a packaged intranet on top of Confluence, while XWiki is a platform you shape with applications, structure, governance, and UI customization.
-
Can Jira–Confluence links be preserved as OpenProject–XWiki links after migration?
This needs to be assessed and tested as part of the migration. We cannot guarantee that existing Jira–Confluence links will automatically become OpenProject work-package-XWiki page links in every environment.
The result depends on how the links are stored in Jira and Confluence. They may be standard issue or page links, URLs inside page content, macros, custom fields, comments, Marketplace-app data, dashboards, or custom scripts. It also depends on whether the related Jira issue and Confluence page are both migrated and whether their identifiers can be mapped reliably.
The practical approach is to make link preservation an explicit migration requirement. We would review representative Jira issues and Confluence pages, identify the link types that matter, test them in a pilot migration, and agree on what can be migrated directly, what needs mapping or custom handling, and what should be reviewed manually.
-
Atlassian is introducing roles in Confluence. Is something similar planned in XWiki?
XWiki already models roles through groups and rights (admin, editor, reader, etc.) at wiki/space/page level. The roadmap focuses on making rights easier to manage rather than introducing a separate roles layer mirroring Atlassian’s UI.
-
Our Confluence uses Oracle DB. We want PostgreSQL for XWiki. Is that a problem for the migration?
All the migrations we do are based on Confluence XML exports, so it is not a database to database migration. The source database engine (Oracle in your case) does not matter much as long as you can produce a clean Confluence export. The import happens from the XML plus attachments into XWiki running on your target stack, including PostgreSQL.
What does matter is the quality and completeness of the export and what is inside it: macros, permissions, links, templates, and any app-specific content. That is why the safest path is still a representative pilot export, import, and validation on your most complex spaces before you commit to the full plan.
-
What if my Confluence instance is complex?
For complex migrations, XWiki conducts an analysis to define the migration scope and develop a clear and achievable roadmap. A proof-of-concept migration can also be used to test the process on a limited scope before scaling.
-
We use Jira Service Management with Confluence linked as a knowledge base. Can XWiki provide the same functionality?
You can migrate your Confluence content into XWiki, but handling the Jira Service Management depends on your needs and context. You can choose to keep Jira Service Management and replace only Confluence, in which case you will have to create or sponsor the development of an integration between XWiki and JSM.
If your goal is to move off Atlassian and keep a service management and knowledge base setup, there is an already more established path: You can pair XWiki with a dedicated work or service management tool.
We are working closely with OpenProject GmbH, and service management is on their roadmap.
If you would like to test the two products, you can also try out the Beta version of our integration: OpenProject Integration (Pro).
-
Should we migrate one Confluence space into one XWiki subwiki, or group multiple spaces in one wiki?
Most teams group multiple Confluence spaces into one XWiki wiki. Subwikis are “buckets” when you need stronger separation.
In practice, we usually collect multiple Confluence spaces in a single XWiki wiki. When we do use subwikis, it is typically to create a small number of “buckets” that match real boundaries, like a department, business unit, region, or security domain. Creating one subwiki per Confluence space rarely makes sense at scale.
It is also completely possible to migrate all Confluence spaces into XWiki’s main wiki. The choice between "only a main wiki" versus **"a few subwikis as buckets"**depends on the kind of content you are migrating and how much separation you actually need in day-to-day operations.
If you are considering subwikis, read how multi-wiki is designed and operated.
-
Is there a list of Confluence macros supported in migration?
XWiki maintains a Confluence macro alternatives page that compares commonly used Confluence macros with their XWiki equivalents and shows whether migration is supported.
-
How much does the migration assessment from Confluence to XWiki cost?
There is no flat public price because it depends on instance size and complexity. You can reach out to sales@xwiki.com for a free assessment and quote.
If you want to migrate on your own, see the pricing of the Confluence Migration Toolkit (Pro).
-
How long does a Confluence-to-XWiki migration take?
The biggest factor in a migration is usually the amount of page history to migrate. An instance with relatively few pages can still take longer than expected when those pages have many historical versions, large attachments, complex permissions, custom macros, or extensive user and group mappings.
For example, an instance with 10 pages that each have 100 versions (resulting in 1000 versions) can take longer to migrate than an instance with 100 pages that only have two versions each (resulting in 200 versions). Attachments, macros, permissions, customizations, user and group mapping, and the level of testing required also affect the timeline, especially in terms of operations, not technical execution.
As an indication from our migration experience:
- A smaller instance of around 50 GB with a few thousand pages can often be migrated in about a week or less.
- Larger environments with hundreds of GB or several TB of data, many historical versions, complex permissions, or extensive macro use need more preparation and staged execution.
- One of the largest instances XWiki has migrated was around 3 TB with roughly 1 million versions. Including preparation, batch execution, testing, and validation, that project took around 6 months.
A migration is therefore not just an import step. It usually includes an initial assessment, source-data preparation, compatibility checks for macros and custom content, test migrations, validation with key users, and a final production migration.
The most accurate timeline comes after a gap analysis of the Confluence instance, so the best way to estimate a timeline is through an initial migration assessment. This looks at page and version counts, attachments, macros, permissions, users, integrations, and any content that needs special handling. That makes it possible to define a realistic migration plan rather than giving a guess based only on page numbers.
-
How do you approach training and onboarding for power users, and resistance from users invested in Confluence?
Treat it as change management, not as a documentation problem. The fastest path is hands on training with real content and real workflows, especially for power users who manage structure, templates, macros, and permissions. Your key takeaways are exactly right here: XWiki is not Confluence, and the gap needs active management.
A good structure is: Pilot with power users, role-based live sessions, clear internal procedures about XWiki usage, and a tight feedback loop during the first weeks after go-live.
-
How does XWiki performance compare to Confluence or other CMS at scale?
Each translation is a separate page so in practice the size of HLS is around 3 times the number of articles in terms of pages, which means around 105,000 pages. (As Romansh is not used in a lot of pages yet.) Other XWiki clients run millions of pages. Performance tuning (like adjusting caching and using external Solr search) keeps the system responsive. Cold caches can slow initial page loads, but warm caches deliver solid performance.
-
How can I achieve a similar restrict page concept for subpages, like in Confluence, without giving every user admin rights?
In XWiki, rights are defined at higher levels, typically at the wiki level. These rights apply by default.
Then on subpages or subpages and children, you can define overrides to grant or deny specific permissions.
Administrative rights granted at a higher level cannot be denied at a lower level. If a user is defined as an administrator for a given scope, those rights remain effective throughout that scope. This differs slightly from Confluence’s permission model.
Unlike Confluence, in XWiki you can open view rights defined in a parent page for certain subpages.
Learn more in our XWiki vs. Confluence comparison.
-
Does XWiki have keyboard shortcuts similar to Confluence?
Yes. XWiki includes by default keyboard shortcuts for common page actions, navigation, editing, comments, history, and administration tasks.
For someone moving from Confluence, an equivalent example is the E shortcut: when hit in view mode, it opens the page in the default editing mode. XWiki also provides shortcuts to open the wiki or object editor, access page comments, attachments, history, page information, or rename a page.
While editing, users can save, preview, or cancel without returning to the mouse, for example with Alt + S to save and view the page or Alt + Shift + S to save and continue editing.
Some view-mode shortcuts are intended for advanced users and need advanced-user mode enabled, which helps prevent accidental actions while browsing. XWiki also supports standard editor shortcuts, plus shortcuts for mentions and links. Administrators can also add further shortcuts through the editor configuration.
-
Does XWiki have a solution for secure collaboration with external clients, similar to Confluence’s “Space Privacy”?
Yes, you can use sub-wikis (wiki farm) or strict page-level rights to provide client-specific private spaces. Sub-wikis allow nearly full isolation per client; a single wiki with nested pages and groups lets you manage access per client area.
XWiki is well-suited for extranet scenarios: Extranet and communities.
-
Can Jira–Confluence links be preserved as OpenProject–XWiki links after migration?
This needs to be assessed and tested as part of the migration. We cannot guarantee that existing Jira–Confluence links will automatically become OpenProject work-package-XWiki page links in every environment.
The result depends on how the links are stored in Jira and Confluence. They may be standard issue or page links, URLs inside page content, macros, custom fields, comments, Marketplace-app data, dashboards, or custom scripts. It also depends on whether the related Jira issue and Confluence page are both migrated and whether their identifiers can be mapped reliably.
The practical approach is to make link preservation an explicit migration requirement. We would review representative Jira issues and Confluence pages, identify the link types that matter, test them in a pilot migration, and agree on what can be migrated directly, what needs mapping or custom handling, and what should be reviewed manually.
-
Does XWiki support database-like structures similar to Notion, Airtable, or Confluence databases?
XWiki can model structured information through classes, objects, properties, forms, and views.
This is one of the things that makes XWiki different from a simple document-only wiki. A page can contain text, but it can also carry structured data that can later be displayed, searched, filtered, or reused.
It is not a direct clone of Airtable or Notion, but it can support similar structured knowledge use cases when you need more than plain text pages. For example, you can create AWMs for procedures, contacts, assets, project records, client information, internal directories, or other reusable business records.
-
Does the Confluence XML export end-of-life mean migration to XWiki will no longer be possible after December 1, 2026?
No, but you may face difficulties if you are using Confluence Cloud. Atlassian's announcement applies to Confluence Cloud only for now. XML site and space exports support will be discontinued on December 1, 2026, which means that a severe bug could prevent you from exporting your data. Atlassian states that the XML site and space export features will still be present, but they will no longer fix bugs, accept support tickets, or provide SLAs for them.
On the other side, CSV export remains supported. We are currently evaluating using the CSV export with our migration tools and we will publish the results of our evaluation soon. You can also reach out to us to discuss your needs and timeline.
In short, migration remains possible, but customers should plan early and assess the available export paths.
-
Can we run the migration assistant to migrate various Confluence spaces at once, or must we migrate each space separately?
Yes, you can organise your space exports in batches, which will trigger the migration of each space one after the other. Also, if you have a fairly small instance, you can use Confluence's backup export, export the whole confluence site, and migrate the full site in one run in XWiki. All three options (single space, batch, and backup export) are available in the Confluence Migrator (Pro).
-
How do permission migrations work? Does the Confluence space permission and page restriction model map? Should we migrate permissions?
Yes, permissions do map and can be migrated from Confluence to XWiki using the Confluence Migrator (Pro) integrated in the Confluence Migration Toolkit.
XWiki rights are hierarchical and more granular compared to Confluence.
The official reference for how Confluence permissions are converted is the Confluence permission handling page. It explains what maps, what is ignored, and why.
To understand the target model, start with Access Rights and permission precedence.
If continuity matters on day one, migrating permissions is often the right call. Many teams then simplify and modernize rights once the new structure is stable and governance is agreed.
-
How can we figure out which Confluence macros were used to plan the migration?
On the Confluence side you can use built-in macro usage tools (Settings → Data management → Macro usage) or custom reporting queries.
As part of a free evaluation, XWiki analyzes your Confluence export and produces a macro-usage report showing which macros are supported and how to handle each one.
There is also a comparison page: comparison of commonly used Confluence macros and their equivalents or solutions in XWiki.
-
Could you explain the Confluence-to-XWiki migration process?
Most commonly, organizations plan migration per team/department: set Confluence spaces read-only, export them, migrate to XWiki, then cut over.
The Confluence Migration Toolkit (Pro) uses Confluence’s native export (space XML or site backup), imports content, attachments, comments, users/groups, permissions and more. After import, it provides a report of imported elements and issues detected (e.g. unsupported macros or broken links) so you can correct them.
XWiki can handle very large imports (including TB-scale sites) with the right environment sizing and parameters.
Toolkit: Confluence Migration Toolkit (Pro).
-
Do I need the XWiki team to migrate from Confluence?
Not mandatorily. For standard migrations, customers can proceed independently using the Confluence Migration Toolkit. They can also contract consulting hours for specific technical needs. For more complex migrations, XWiki can provide support throughout the migration.
-
Can XWiki replace Confluence?
XWiki is often used as an open-source alternative to Confluence, especially by organizations that need more control over hosting, data, customization, and long-term ownership. Support can help teams adopt XWiki and handle questions after migration.