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

In this webinar, recorded on November 12, 2026, the XWiki and OpenProject teams demonstrate how organizations can migrate their existing knowledge and projects from Atlassian while maintaining connections between documentation and project work.

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.

  • 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.

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.