Moving away from Confluence and Jira involves more than transferring pages and issues. There are years of documentation, carefully configured workflows, user permissions, integrations, and links that people rely on every day. As Atlassian Data Center support approaches its end on March 28, 2029, organizations are preparing to migrate. They need to understand what they can preserve and what they'll need to adapt.
In November 2026, we joined forces with OpenProject for a webinar focused on exactly these challenges. Ștefana Nazare, Product Owner at XWiki, and Wieland Lindenthal, Co-founder & CTO at OpenProject, shared the latest developments in both platforms, demonstrated how they work together, and discussed what's coming in 2027. The webinar also featured a live demonstration of the Jira migration process by OpenProject's Kristine Jetzke.
And you had plenty of questions. Some were about the migration itself: preserving page history, handling Confluence macros, or transferring Jira workflows. Others went deeper into authentication, infrastructure, licensing, and how XWiki and OpenProject connect in practice.
We've brought together the questions submitted during the webinar, along with answers, practical explanations, and links to the relevant documentation. Whether you're comparing alternatives or already planning a migration, we hope this article will help you understand what's possible today. We've also highlighted what still requires preparation and where our teams can help.
Watch the webinar recording
Key takeaways
#1. Migrate Confluence knowledge to XWiki with the Confluence Migration Toolkit
During the XWiki demonstration, Ștefana imported Confluence content and opened the resulting migration report. The report listed the pages and revisions transferred, identified macros in the source content, and flagged the ones requiring attention. It gives administrators a useful starting point for reviewing an import.
The Confluence Migration Toolkit handles supported pages, attachments, comments, history, users, groups, permissions, metadata, and macros. It also supports batch imports and repairing references between separately imported spaces. XWiki's website now reports 230+ Confluence migrations completed with its tools and support.
During 2026, we increased the free Toolkit trial to 200 pages per migration and improved the migration report. We also added support for macros such as ui-button, ui-tabs, and ui-steps, and expanded the handling of Confluence sets and task metadata. The Toolkit also introduced experimental support for Confluence Cloud CSV exports.
#2. Migrate from Jira to OpenProject: a live demonstration and a look ahead
Kristine demonstrated the <ins>OpenProject Jira Migrator</ins> and the improvements introduced throughout 2026. The demonstration was also part of a broader look at OpenProject's continued development as an open-source alternative to Jira. This included a preview of OpenProject 18.0, scheduled for release on December 2, 2026.
The migrator connects to Jira Data Center and allows administrators to select projects for import. With OpenProject 18.0 it supports project information, issues, descriptions, comments, attachments, history, users, groups, statuses, types, and selected custom fields.
After an import, administrators can review the results and decide whether to approve or revert the migration. This makes it possible to inspect real Jira data in OpenProject and identify areas requiring further configuration.
The Jira Migrator was still in beta at the time of the webinar, with OpenProject recommending its use in test environments.
For teams considering a migration, the current tool offers an opportunity to evaluate OpenProject using familiar projects. They can check how their existing data is transferred and identify any workflow or configuration gaps.
#3. Connect XWiki documentation with OpenProject work packages
The integration connects project management and documentation in both directions.
In XWiki, the <ins>OpenProject Integration (Pro)</ins> can display work packages inside documentation and let users create or edit project records. The demonstration included creating several work packages from information in an XWiki table. In OpenProject, users can link existing XWiki pages, create pages, and find references to work packages through the Wikis tab.
On the OpenProject side, users can link existing XWiki pages to work packages, create new wiki pages, and access related documentation through the Wikis tab. References also help teams identify where work packages are mentioned in XWiki.
Each user connects their accounts through OAuth 2.0, while both platforms continue enforcing their respective access permissions.
Since version 17.6, users can link existing XWiki pages or create new ones directly from OpenProject work packages. The Wikis tab provides access to the associated documentation, and references can show where a work package is mentioned in XWiki.
During the webinar, Ștefana demonstrated these workflows and showed how project information and documentation can remain connected as both evolve. You can find the <ins>integration setup guide</ins> in OpenProject's documentation.
#4. Choose how to deploy and manage both platforms
XWiki and OpenProject offer cloud and self-hosted deployment options. Organizations can select the environment that fits their infrastructure, security policies, and compliance requirements.
Self-hosted deployments provide direct control over the environment, including updates, infrastructure configuration, backups, and operational policies. This freedom comes without loss of features, ownership, or extensibility.
For enterprise environments, the teams provide professional support, commercial extensions, and services for implementation and migration.
This flexibility is relevant for organizations with existing infrastructure investments or requirements concerning data residency and operational control.
#5. Get a glimpse of the migration improvements planned for 2027
For Q1 2027, the XWiki team presented work on permission-mapping improvements and converting Confluence Details and Details Summary content into App Within Minutes applications. A Roots App was presented for Q2 2027 to improve content organization after migration.
OpenProject's Q1 2027 plans include more configuration options for mapping statuses, types, users, groups, and project-specific custom fields. The Q2 2027 roadmap covers workflow migration, automation, boards, and closer coordination between Confluence and Jira migrations, especially references between pages and issues. For a complete overview of upcoming features and planned developments, explore the OpenProject roadmap.
Teams planning a migration should check the delivered releases and current compatibility notes when setting their schedule.
Questions and answers
The Q&A brought together several recurring concerns from organizations evaluating XWiki and OpenProject. Participants wanted to understand what can be migrated, how existing workflows would behave, and which capabilities require additional configuration.
Confluence migration
-
What happens to page history, attachment versions, authors, and timestamps in XWiki?
When migrating to XWiki, you can retain previous page versions, including their authors, modification dates, and revision comments. Users can then access the imported revisions through XWiki's page history, allowing teams to trace how documentation evolved before the migration.
Most of this information is preserved automatically, although administrators can adjust certain settings under Advanced migration options:
- Page history: Imported by default. The Import history option can be disabled to skip previous revisions, reducing migration time and storage requirements.
- Authors: Preserved through the migration process. Administrators can optionally configure user mapping when Confluence and XWiki use different account identifiers.
- Timestamps: Original revision dates are preserved when version preservation is enabled. This is handled through an internal import setting and doesn't normally require manual configuration.
- Attachment history: Supported for Confluence XML export format version 9.78.0 or later, provided the required attachment data is included in the export. Attachment import is enabled by default and can be disabled.
-
There still seems to be a gap compared to Confluence. Will XWiki feel familiar to Confluence users?
XWiki and Confluence have a lot in common, but the differences between them are intentional. Both have been around since 2004 and have evolved into established enterprise knowledge management platforms, each with its own approach.
XWiki provides the familiar features people expect from a collaborative wiki: visual editing, real-time collaboration, comments, templates, search, version history, and granular permissions.
Where XWiki particularly stands out is in its flexibility. Its structured data model, built-in scripting capabilities, and App Within Minutes allow organizations to create custom applications, forms, and workflows directly within their knowledge base. Teams also have control over their hosting, infrastructure, and customizations.
We've been helping organizations migrate from Confluence for years. As Atlassian's pricing and deployment changes increased demand for alternatives, we invested further in our migration tools.
Of course, moving to a different platform involves learning its interface and concepts. That's why we help organizations prepare their navigation, templates, and workflows around their users' needs.
Our XWiki and Confluence concepts comparison provides a detailed look at the features, architecture, and customization options available in both products.
-
How does the Confluence Migration Toolkit differ from the Confluence Migrator?
The Confluence Migration Toolkit is our recommended and professionally supported solution for migrating from Confluence to XWiki. It includes the Confluence Migrator (Pro) and the additional tools needed to preserve and manage your content throughout the migration.
It provides capabilities such as batch migration, detailed migration reports, user and group mapping, permission migration, and tools for fixing links between imported spaces. The package also includes applications such as Pro Macros and Task Manager App (Pro) to help maintain Confluence functionality in XWiki.
Professional support is included, covering the migration tools, XWiki itself, and the applications provided with the Toolkit.
You can try the Confluence Migration Toolkit before purchasing a license. The free trial allows you to migrate one space with up to 200 pages per run.
-
Can I choose the parent page or space where Confluence content will be imported?
The Confluence Migration Toolkit lets you choose the destination wiki or space using the Root parameter under Advanced migration options.
The Root parameter defines the starting location for the imported content. For example, you can import a Confluence space under Documentation.Engineering in your main wiki or into a dedicated subwiki.
There are a few things to consider:
- The original hierarchy is preserved: The Toolkit places imported Confluence spaces beneath the selected root, retaining their page structure. The Root parameter doesn't let you assign a different destination to every individual page.
- Multiple destinations require planning: If you're importing several Confluence spaces into different locations, configure the appropriate destination for each migration.
- Existing content is protected according to your settings: The Toolkit provides overwrite protection and space-renaming options to handle naming conflicts.
- Subwiki imports require correct user references: If your users and groups are managed in the main wiki, configure the Users wiki parameter accordingly.
You can also reorganize imported pages after migration if you want to change their structure further.
The Confluence Migration Toolkit documentation explains the Root parameter, destination formats, and overwrite protection settings.
-
Can I choose Confluence spaces for import without generating a backup?
The Confluence Migration Toolkit works with Confluence exports, so you'll need to export your content before importing it into XWiki. You can, however, choose exactly which spaces to migrate.
There are several options depending on the size of your Confluence instance:
- Individual space exports: Export and migrate specific spaces.
- Batch migration: Organize several space exports in batches and let the Toolkit process them sequentially.
- Full-site backup: Export the entire Confluence instance and select the spaces you want to import in the dedicated Toolkit screen. This approach is generally more suitable for smaller instances.
The Toolkit supports XML exports and has introduced experimental support for Confluence Cloud CSV backups.
For larger environments, we generally recommend working with individual space exports or batches. Keep in mind that space exports don't include user and group information, so identities may need to be imported or mapped separately.
You can find more information in our Confluence migration guide and the XWiki migration FAQ, which covers space exports, batch imports, and migration planning.
-
What happens to Jira mentions, embedded issues, and Jira charts in Confluence pages?
The Migration Toolkit preserves Jira macro calls and XWiki provides partial support for embedded Jira macros and charts. The result depends on the macro parameters and whether your organization plans to keep Jira or migrate to OpenProject.
Confluence user mentions can be associated with XWiki accounts through identity mapping. Standard Jira links can remain clickable after migration.
For embedded Jira content, the Toolkit provides partial support for both the Jira and Jira Chart macros. This means that some configurations can be migrated, while unsupported parameters or display options may need adjustments. You can check the details in our Jira Chart macro migration documentation.
If you're keeping Jira, XWiki provides an open-source Jira integration that can display issues, JQL search results, issue counts, and charts inside wiki pages. Our Jira Application (Pro) adds per-user authentication and the ability to create Jira issues directly from XWiki. It currently supports Jira Server and Data Center, with Jira Cloud compatibility under development.
If you're migrating Jira to OpenProject, our OpenProject Integration (Pro) lets you display and manage OpenProject work packages from XWiki pages. Existing Jira macros may need to be adapted to reference the corresponding OpenProject work packages.
We recommend including pages with embedded Jira issues and charts in your test migration. This will help identify which macros migrate successfully and which need additional configuration.
If you'd like us to review your existing Jira macros, contact our team. We can help assess their compatibility and identify the best approach for your migration.
-
Do links survive the move, including cross-space links, short URLs, and links from outside Confluence?
XWiki supports migrating internal Confluence links and can also redirect old Confluence URLs to their corresponding pages in XWiki.
The Confluence Migration Toolkit converts links between pages, including links across different spaces. If 2 linked spaces are migrated separately, the Toolkit's reference-fixing feature can resolve missing references once both spaces have been imported. Administrators can preview the changes before applying them.
For links shared outside Confluence, such as bookmarks, emails, or links in other applications, XWiki provides a Confluence URL Mapping extension. It supports redirects for common Confluence URL formats, including page links, page IDs, /x/ short URLs, and attachment links.
Keeping these external links working requires additional server configuration. You'll need to maintain access to the old Confluence domain or subdomain and configure your reverse proxy to direct requests to XWiki. The extension uses a dedicated URL prefix to process the old links.
Our URL Mapping setup guide explains the configuration. We recommend testing a representative sample of internal links, short URLs, and external bookmarks before switching to XWiki.
-
Is there a maximum import size for a Confluence space?
There is no single published GB limit for every installation.
The available memory, disk space, attachment limits, and export structure affect what the target XWiki instance can handle. The Toolkit can run migrations for single spaces, full backup exports, or in batches. For a large installation, these options help organize imports into manageable groups.
Its free trial permits one space and up to 200 pages per migration, but no limit is enforced in production environments. Production sizing depends on the infrastructure.
-
Which native Confluence macros and Marketplace add-ons will migrate?
Almost 200 Confluence macros are automatically handled by the Confluence Migration Toolkit. Others may require an XWiki application, additional configuration, or custom development.
The Toolkit generates a macro report showing which macros are used, how frequently they appear, and whether they are supported. Common Confluence macros and a selection of Marketplace macros have supported conversion paths. Add-ons with their own workflows, stored data, or business logic may require a separate assessment.
You can explore the available options on our Confluence macros documentation and in the Toolkit documentation.
If a macro is not supported, the imported XWiki page displays an error message where that macro appears. The affected content won't render as it did in Confluence, making the issue visible to anyone viewing the page.
However, the original macro syntax is imported and accessible in wiki edit mode, so the migration team can examine it and determine how to reproduce the functionality in XWiki. Depending on the macro, this might involve configuring an existing alternative or developing a custom solution. No content is lost.
-
Can draw.io diagrams embedded in Confluence pages be migrated?
The Confluence Migration Toolkit supports draw.io content, and the Diagram Application (Pro) provides diagram creation and editing in XWiki.
The Toolkit also supports conversion for Gliffy diagrams. When possible, converting Gliffy content to draw.io format in Confluence can improve the result. Check a sample of your diagrams after import, particularly those that use unusual shapes or application-specific settings.
XWiki features and infrastructure
-
Can XWiki Standard create templates, reports, and PDFs?
These 3 capabilities are available and Confluence templates are migrated.
You can create reusable page templates for documentation, meeting notes, and procedures. For reporting, XWiki supports structured data, queries, and macros, allowing teams to build custom reports and dashboards. With App Within Minutes, you can also create applications to organize and report on information without coding.
XWiki also supports exporting individual pages or entire page hierarchies to PDF, with options to customize layouts, branding, headers, and footers. You can find more details in our PDF export guide.
XWiki's documentation covers the export and application options.
-
Can XWiki power an intranet with features like Linchpin?
XWiki is already used by numerous large organizations to run intranets, employee portals, and internal knowledge bases.
Linchpin provides a predefined intranet experience built on Confluence. XWiki offers a flexible platform where organizations can customize the navigation, interface, content structure, and applications to match their needs. Its structured data and application development capabilities also allow organizations to create custom features tailored to their internal processes.
You can explore our XWiki and Confluence webinar recap, where we also address this question and share examples of customized XWiki implementations.
-
Can XWiki create BPMN diagrams and handle content from Confluence BPMN Modeler?
XWiki supports BPMN diagrams through its Diagram Application (Pro). The application integrates draw.io, allowing users to create, edit, import, and embed process diagrams directly in wiki pages. Diagrams are versioned, so teams can track changes over time.
For organizations migrating from Confluence BPMN Modeler, compatibility depends on the original diagram format and the features used. Existing models may require conversion, particularly if they include BPMN 2.0 XML definitions, validation rules, or connections to workflow engines.
We can help assess your existing diagrams and identify the appropriate migration approach.
-
Is an Asset-DB application planned for XWiki?
We have no confirmed release date for a product equivalent to Asset-DB, but XWiki can already model asset registers, ownership, locations, relationships, and associated procedures using structured applications.
With App Within Minutes, organizations can create asset management applications to track equipment, software, ownership, locations, maintenance records, and related documentation. These applications can include custom forms, searchable and filterable records, and granular permissions.
-
Do companies need a commercial license to use XWiki?
XWiki Standard is free and open-source software, and companies can use it commercially without purchasing a license.
XWiki is distributed under the LGPL 2.1 license. Organizations can download, install, customize, and use it on their own infrastructure, with no per-user licensing fees.
Commercial offerings are available for organizations that need professional services such as managed cloud hosting, technical support, migration services, or user and admin trainings.
-
Does XWiki clustering guarantee zero-downtime upgrades?
XWiki supports high-availability clustering, but zero-downtime upgrades aren't supported natively and currently need at least a maintenance window where the instance is read-only.
In a clustered deployment, multiple XWiki nodes operate behind a load balancer, helping maintain service availability if a node becomes unavailable.
For a zero-downtime upgrade, the process can be performed on a clone of the instance including the database and any other resources while the original instance is switched to read-only mode. After the upgrade of the clone has been completed, the load balancer can be switched to the clone.
For organizations with strict availability requirements, our team can help assess the upgrade path and plan the deployment accordingly.
See the XWiki upgrade documentation for the steps and prerequisites involved.
-
Can Solr be deployed in a highly available cluster with XWiki?
Currently, XWiki does not support SolrCloud or clustered Solr instances. However, it does support running it as a separate, standalone service.
By default, XWiki uses an embedded Solr instance. For larger installations, we recommend running Solr externally to improve resource management and search performance. This allows Solr to use dedicated memory and computing resources.
XWiki also supports high-availability clustering at the application level. However, this should not be confused with Solr clustering. Even when XWiki runs across multiple application nodes, the external Solr service remains a separate component without supported SolrCloud replication or automatic failover.
If you require SolrCloud support, contact us to discuss your exact requirements and deployment timeline so we can see if we can add SolrCloud support in time for your deployment.
You can find configuration instructions in our external Solr deployment guide.
-
Can an AI search node use a read-only PostgreSQL replica and its own Solr instance?
PostgreSQL and a dedicated Solr instance are supported but permission checks must be handled outside the database and Solr.
Using our MCP server extension with its built-in search guarantees that each user can only access exactly the documents the user has access to.
An alternative approach to keep the AI search node's load off your main XWiki instance would be to use the Replication extension. You can thus synchronize the content you want to make accessible to AI search to a separate instance. Here, you can install XWiki's MCP server extension.
Our technical team can help assess this architecture and determine the appropriate configuration for your deployment.
Jira migration and OpenProject capabilities
-
Is the Jira Migrator ready for production, and which records does it move?
At the time of the webinar in November 2026, the OpenProject Jira Migrator was still in beta, with OpenProject recommending its use in test environments.
The migrator supports importing Jira Data Center projects, issues, descriptions, comments, attachments, history, users, groups, statuses, types, versions, and selected custom fields. It also preserves Jira issue identifiers, helping teams maintain familiar references after migration.
OpenProject continuously extends the migrator with each release, improving the range of supported data and configurations. With the release scheduled for Decmber 2nd, 2026, relationships between issues, labels, resolutions and worklogs are migrated as well. Organizations should review the current field mapping before planning a production migration.
The Jira Migrator is available free of charge, including in OpenProject Community. Enterprise subscriptions, hosting, consulting, and migration support are available separately.
For the latest information, see the Jira Migration documentation.
-
What happens to Jira workflow schemes, permissions, screen configurations, automations, and JSU or ScriptRunner logic?
OpenProject provides configurable workflows based on work package types, roles, and statuses, as well as custom actions, APIs, and webhooks for extending and automating processes.
Rather than reproducing Jira's complex configuration schemes exactly, OpenProject aims to offer a more straightforward approach to managing workflows and project-specific requirements.
The Jira Migrator does not yet automatically recreate complete Jira workflow schemes, screen configurations, permission schemes, or Marketplace automation scripts. Organizations should therefore review their existing configurations, identify the underlying business requirements, and determine how best to implement them in OpenProject.
Further improvements to workflow configuration, automation, and migration capabilities are planned for the beginning of 2027. See the OpenProject roadmap for details.
-
Can Jira Advanced Roadmaps hierarchies be migrated?
OpenProject provides comprehensive planning capabilities, including project and work package hierarchies, dependencies, Gantt charts, agile backlogs, resource and capacity management, and programs and portfolios.
These features allow organizations to connect strategic planning with day-to-day project execution, combining classic, agile, and hybrid project management in one platform.
However, the Jira Migrator does not yet automatically recreate complete Advanced Roadmaps plans. Custom hierarchy levels, scenarios, dependencies, and capacity assumptions may require additional configuration or reconstruction.
OpenProject recommends evaluating your existing planning structures and reporting requirements using a representative project. Improvements to issue relationships, hierarchy migration, and other Jira-specific configurations are part of OpenProject's ongoing development.
-
Can teams track time in OpenProject, and will Jira work logs migrate?
Time tracking is available in OpenProject. Historical Jira work logs will be imported with the upcoming 18.0 release (scheduled for December 2nd, 2026).
OpenProject lets users log time against work packages, maintain budgets, and review time and cost reports.
The time-tracking guide covers everyday use.
-
Can XWiki and OpenProject cover Jira Service Management, including its customer portal, SLAs, and Assets?
OpenProject and XWiki can already support several IT service management use cases, with additional functionality planned.
OpenProject provides configurable work packages, workflows, custom fields, and permissions to manage incidents, service requests, and changes. XWiki complements this with knowledge bases, technical documentation, and runbooks.
OpenProject's roadmap also includes further IT service management capabilities, such as a dedicated service portal, service level agreements (SLAs), improved incoming-email workflows, and asset management.
However, OpenProject and XWiki are not yet a complete drop-in replacement for every Jira Service Management feature. Organizations should evaluate their specific requirements, including customer portals, queues, SLA calculations, asset relationships, email channels, and permissions.
For upcoming developments, see the OpenProject roadmap.
-
Will SquashTM be integrated with OpenProject like Xray is integrated with Jira?
The first version of the SquashTM integration will be delivered with the upcoming 18.0 release, scheduled December 2nd, 2026. The future integration's exact scope and licensing have yet to be confirmed.
It is also possible to use OpenProject directly for leightweight test management as described in this article.
The Jira Migrator currently has no generic Xray or Zephyr data import, so existing test cases, execution evidence, and automation results need their own migration plan.
-
How does OpenProject compare with Microsoft Project?
OpenProject combines classic project planning with agile and hybrid project management in one collaborative platform.
Like Microsoft Project, OpenProject offers Gantt charts, milestones, task dependencies, work package hierarchies, and scheduling capabilities. It also provides resource and capacity management to help teams plan workloads and availability.
Beyond traditional project planning, OpenProject includes agile boards, backlogs, issue tracking, time and cost management, team collaboration, and portfolio management.
A key difference is that OpenProject is open source and can be self-hosted, giving organizations greater control over their data, infrastructure, and deployment.
For organizations relying on specialized Microsoft Project scheduling features, we recommend comparing their specific workflows and requirements before migrating.
-
What integrations does OpenProject offer for Git?
OpenProject has build-in integrations with GitHub and GitLab.
Teams can connect pull requests or merge requests with work packages and follow development activity alongside project tasks.
The GitLab integration guide explains the available links and configuration.
These integrations connect project records with development activity. They do not copy an entire Git repository into OpenProject.
For another Git host or a specialized CI workflow, OpenProject's API and webhooks provide extension points.
-
Can OpenProject manage requirements and their traceability?
Yes. Requirements can be represented as work packages with types, statuses, custom fields, relationships, and hierarchies.
A team can connect requirements to delivery work and use filtered views to monitor progress.
XWiki can maintain the detailed specification, design decisions, and supporting documentation. The integration then connects those pages to the work packages responsible for implementation.
For regulated processes, validate the required approvals, traceability reports, and audit records using a representative project.
-
Can Jira remain active while we import changes incrementally, or synchronize with a partner's Jira?
The Jira Migrator is a one-way import tool. It is not a built-in continuous 2-way synchronization service.
It recognizes some records across repeated runs, such as previously imported users, but this does not establish safe incremental imports for every changed issue, comment, attachment, or relationship.
For a staged migration, set a clear cutover plan and validate what happens to records changed after the pilot import.
If Jira needs to be used indefinitely, a separate integration is required. OpenProject's API and webhooks can support this, with mapping rules for identifiers, ownership, updates, and conflicts.
-
Can the Jira Migrator import more than one project?
Yes. An import run can select multiple Jira projects.
The migrator retrieves the available projects from the connected Jira instance and lets an administrator choose the scope.
OpenProject's migration guide covers selection, import review, approval, and rollback.
Pricing, licensing, and the integration
-
What does a longer evaluation cost, and how many OpenProject Enterprise licenses are required?
You can evaluate both platforms for free. Longer trials and larger migration pilots can be discussed with our teams.
XWiki Standard and OpenProject Community are free to use on your own infrastructure. The Confluence Migration Toolkit also offers a free trial covering one space and up to 200 pages per migration.
OpenProject offers a 14-day Enterprise trial. Its standard Enterprise subscriptions start at 5 users for Cloud and 25 users for on-premises deployments.
For the native XWiki integration, OpenProject requires the Corporate Enterprise plan, which starts at 250 users and is priced on request.
If you're evaluating the integration with a smaller team or need more time to test a complex migration, contact the respective sales teams to discuss an appropriate trial. OpenProject also provides trial options for evaluating Enterprise features from higher subscription tiers.
See the OpenProject pricing and trial options for details.
-
What exactly can the XWiki and OpenProject integration do, and what do we need to buy?
XWiki and OpenProject work together in both directions, connecting project documentation with the work packages, people, and activities managed in OpenProject.
On the XWiki side, our OpenProject Integration (Pro) lets users display, filter, create, and edit OpenProject work packages directly from wiki pages. Work packages can appear as tables, cards, individual items, charts, or calendar views.
You can also link documentation to project work while writing. In XWiki's visual editor, simply type # followed by at least 3 characters to search for a work package and insert it directly into your page. You can even select text from a document and turn it into a new OpenProject work package.
The integration goes beyond work packages. XWiki provides macros for displaying project details, members, subprojects, news, time spent, and tasks assigned to the current user. Administrators can also create reusable filter presets, so teams can display consistent project information across multiple wiki pages. Several OpenProject instances can be connected to the same XWiki installation.
On the OpenProject side, the native XWiki integration lets users link existing wiki pages to work packages or create new XWiki pages directly from OpenProject. Work packages also show which XWiki pages reference them through the Wikis tab, making it easier to find related requirements, specifications, or technical documentation. The integration uses REST APIs to create pages and retrieve linked information.
Each user connects their own accounts through OAuth 2.0. XWiki and OpenProject continue enforcing their respective permissions, so users see only the documentation and project information they are authorized to access.
What about licensing? The XWiki OpenProject Integration (Pro) starts at €95 per year, depending on the number of users and support level. It's also included in the XWiki Pro and Confluence Migration Toolkit packages. On OpenProject's side, the native XWiki integration requires the Corporate Enterprise plan, starting at 250 users, with pricing available on request.
You can explore the features in our XWiki integration documentation and the OpenProject setup guide.
-
Do embedded work packages refresh automatically while an XWiki page stays open?
The integration retrieves work-package data directly from OpenProject, but automatic refresh behavior depends on the component being used.
XWiki can display OpenProject work packages through tables, charts, calendars, and dashboards. Users can also edit supported work-package properties directly from the wiki.
For a page that remains open while project information changes elsewhere, we haven't established a universal automatic refresh interval across all these components.
See the available components in the OpenProject Integration (Pro) documentation.
-
Is there an integration with iTop as well as OpenProject?
XWiki provides a ready-to-use integration with OpenProject. For iTop, an integration can be developed using XWiki's APIs and extensibility.
We don't currently offer a dedicated iTop integration with the same functionality as our OpenProject application.
However, XWiki can connect with external applications through its REST API and scripting capabilities.
For example, an organization could connect configuration items maintained in iTop with technical documentation, procedures, or maintenance records stored in XWiki.
The implementation would depend on the information you want to exchange and whether you need one-way access or synchronization between both systems.
-
Can different customers be isolated so that they cannot discover each other's spaces, users, or email addresses?
XWiki and OpenProject can restrict access to customer-specific content.
In XWiki, permissions per user directory and per space or subwiki can be set using the universal granular rights system.
OpenProject provides more specific user visibility controls. Users can discover others based on shared projects, groups, and global permissions. For example, members of a public project may be visible to users outside their own organization.
When the 2 platforms are connected, each continues enforcing its own permissions for accessing content.
If your requirement is complete separation of customer content, identities, and contact information, separate instances may be the appropriate approach. Our teams can help assess the options based on your security and privacy requirements.
-
Where should an experienced Jira and Confluence administrator or plugin developer begin?
Start with a test environment containing a representative Confluence space and Jira project. This gives you a practical way to explore both products using familiar information.
For XWiki, begin with the official documentation to learn more about spaces, permissions, templates, and macros, then explore App Within Minutes, scripting, and the extension framework.
For OpenProject, start with the official documentation and familiarize yourself with work packages, types, statuses, workflows, custom fields, roles, and permissions. Administrators and developers should also explore OpenProject's API and integration capabilities.
The Jira Migrator documentation provides guidance on importing existing projects and understanding which configurations may require adaptation.
You can then compare XWiki with Confluence and check the Jira Migrator roadmap to see how your existing content and configurations are transferred.
If you also want to evaluate the integration, the setup guide explains how to connect both platforms. Access to the native integration requires OpenProject's Corporate Enterprise add-on.
Getting started with XWiki and OpenProject
Thinking about moving away from Confluence and Jira? A good place to start is with the content and projects your teams already use.
One thing we appreciated about this webinar was the level of detail in your questions. From preserving years of document history to handling complex Jira workflows, many of you are already looking closely at what a migration would involve.
Every organization has its own way of managing knowledge and projects, often built around years of configurations, integrations, and accumulated content.
We've been helping organizations move from Confluence to XWiki for years, and our collaboration with OpenProject is bringing that experience to teams looking for an alternative to the wider Atlassian stack. The integration already connects documentation and project work, and both teams have more migration improvements planned for 2027.
If you're considering a move, we'd be happy to look at your particular setup, including the tricky parts. You can contact us or schedule a call with our team to discuss your migration requirements and explore what XWiki and OpenProject could offer your organization.