Skip to content

Confluence zu XWiki

Your knowledge stays. The platform changes

ForgeOne supports companies in the structured transition from Atlassian Confluence to XWiki Enterprise – on-premises, in the private cloud or as a managed platform.

Confluence → XWiki

Analysis, test migration, quality assurance and controlled cutover

1. Assess the current environment

Spaces, pages, attachments, macros, apps, users and permissions.

2. Define the target state

Structure, permissions, integrations and operating model.

3. Test migration

Migrate representative content and review it from a functional perspective.

Why switch?

An on-premises alternative with long-term control

XWiki Enterprise enables companies to manage knowledge within their own infrastructure or private cloud while benefiting from vendor support, enterprise extensions and an open platform.

Data sovereignty

You determine the location, operations, backup, access and integrations.

Open platform

APIs, macros, apps and structured data instead of a closed ecosystem.

Enterprise Support

Licensed XWiki instance with vendor support and ForgeOne as a partner.

Migration analysis

Before the import comes the technical and functional assessment.

A reliable migration begins with an analysis of the actual Confluence usage. Not every piece of content, macro or app can be migrated unchanged.

We assess

The next useful step depends on target architecture, maturity and operating responsibility. ForgeOne connects assessment, planning, delivery and operations so projects start clearly and remain sustainable.

We define

The XWiki target state.

  • Target knowledge structure
  • Mapping of content and permissions
  • Identity and SSO integration
  • Operations, backup and update model
  • Acceptance criteria and cutover plan

From proof of concept to production handover

  1. Step 1

    Discovery Workshop

    Clarify objectives, scope, technical constraints and responsibilities.

  2. Step 2

    Analysis and concept

    Assess the current environment and develop a realistic mapping to XWiki.

  3. Step 3

    Test migration

    Migrate representative content, identify risks and validate the effort required.

  4. Step 4

    Production migration

    Data migration, quality assurance, cutover and controlled go-live.

  5. Step 5

    Optimization and operations

    Improve structures, train users and transition the platform into regular operations.

Licensing

Migration and operations based on XWiki Enterprise.

A valid XWiki Enterprise Subscription is required for migrations and XWiki platforms managed by ForgeOne. It provides, among other things, the Migration Toolkit, Enterprise extensions and vendor support.

ForgeOne exclusively supports licensed XWiki Enterprise instances. We handle licensing, renewal, technical implementation, support and, if required, ongoing operations.

Assessing and validating a Confluence migration

A Confluence migration is more than an export and import task. ForgeOne assesses Confluence Cloud or Data Center, data volume, spaces, page hierarchies, attachments, embedded content, internal links, users, groups, permissions, macros, apps and interfaces. The result is a realistic mapping to XWiki rather than a blanket promise that every function can be transferred unchanged.

  1. Inventory content and dependencies: spaces, pages, attachments, macros, extensions, identities and permissions.
  2. Identify functions that cannot be transferred directly and decide whether to replace, adapt or intentionally retire them.
  3. Define the XWiki target structure, permissions, SSO, integrations, backup, update and operating model.
  4. Run a representative test migration and validate content, links, attachments, formatting, search and access rights.
  5. Define the migration window, delta transfer, cutover, rollback and technical as well as functional acceptance criteria.
  6. Secure production launch, training, documentation and subsequent platform operations.

What can be migrated automatically depends on the Confluence version, hosting model, extensions, data volume and permission model. A test migration is required before effort, quality and remaining remediation can be assessed reliably.

In 2025, XWiki documented a session about the European Parliament migration from Confluence to XWiki. This is an external reference for use in a European institutional setting; ForgeOne was not involved in that project. Source: XWiki: Events in autumn 2025.

Where Jira and Confluence are assessed together, OpenProject adds project management and workflow requirements to the evaluation. Each target platform still needs to be validated separately against actual requirements.

Recommended next step

From the product decision, the next step leads into architecture, implementation or operations.

Recommended

Implementation & Migration

Clarify scope, risks, migration and operating model with ForgeOne.

Discuss the project

Align concrete needs, timeline and next appointment.

Are you planning to switch from Confluence?

We assess your environment and show you what a realistic migration path to XWiki Enterprise looks like.