Back to Blog

    SharePoint

    Migrating Confluence to SharePoint, including on-premises

    How we migrate Confluence content to SharePoint Server 2019 and SPSE with our own framework: process, pilot, rework and limitations.

    July 5, 20253 min read
    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    marcel.haas@cnext.ch
    CNEXT SharePoint
    In this article

    Atlassian ended support for Confluence Server on 15 February 2024. If you want to keep running your content in your own data centre, you can migrate it to SharePoint Server 2019 or SharePoint Server Subscription Edition (SPSE). We do this with our own automated migration framework. It is still not a lossless copy: macros, permissions and links need a mapping and a pilot.

    Our migration framework

    The framework grew out of our project work. It is based on PowerShell, REST interfaces and SharePoint PnP, and it is built for organisations that are replacing Confluence but want to stay with SharePoint on-premises.

    • Target platforms: SharePoint Server 2019 and SharePoint Server Subscription Edition
    • Scope: Confluence spaces, pages and components, including wiki pages, documents and attachments
    • Presentation: Page content is converted into modern SharePoint web parts so that it can use SharePoint's collaboration features.
    • Automation: The transfer is automated to keep manual work and downtime low.

    The framework is aimed mainly at organisations with strict regulatory requirements, for example in financial services, healthcare or public administration, that want to keep their data in their own data centre.

    Confluence migration to SharePoint with the CNEXT framework

    What is automated and what is checked

    AreaApproach
    Spaces, pages and componentsAutomated transfer, page content as SharePoint web parts
    Documents and attachmentsAutomated transfer to SharePoint
    Macros and extensionsMapping per macro: matching SharePoint building block, customisation or retirement
    Permissions and user groupsDefine the target structure with SharePoint groups, check the mapping in the pilot
    Links, URLs, version history, commentsCheck in the pilot and record in the acceptance criteria

    How a migration runs

    1. 1Analysis and planning: We analyse the structures, content and requirements of your Confluence environment. The inventory covers spaces, page types, macros, attachments, user groups, external links and integrations. From this follows which content stays active, is archived or is deleted, and how sites, libraries, pages, metadata and groups are structured and governed in SharePoint. The Confluence version, licence status and available export options also belong in this phase.
    2. 2Pilot: We recommend migrating representative spaces first and recording what was transferred, skipped or needs manual work. Acceptance criteria for content, links, permissions, search and usability are agreed beforehand.
    3. 3Automated migration: The framework transfers spaces, pages and components into SharePoint web parts. Cutover needs a change freeze or a delta transfer, plus a tested rollback plan.
    4. 4Rework and testing: We check that all content has been migrated correctly, rework whatever cannot be mapped automatically and help optimise the new SharePoint environment.
    5. 5Training and support: We train your staff and provide ongoing support so that SharePoint is adopted in daily work.

    Why SharePoint Server as the target

    SharePoint Server 2019 and SPSE provide document management, collaboration and workflow automation in your own data centre. SPSE also supports sign-in via OpenID Connect and upgrades from earlier SharePoint Server versions. In return, you are responsible for infrastructure, patching and security yourself. Choose the target platform, data location and operating model against your technical and legal requirements.

    What to keep in mind

    • A migration is not a lossless copy. Content may look different in SharePoint, and a Confluence macro does not automatically become a native SharePoint web part.
    • Only the pilot with your data shows how much is automated and how much rework remains. Ask every migration provider, including us, for a written mapping of supported content types, known limitations, the test logs from the pilot, and the pricing and schedule assumptions.

    Sources

    SharePointAgentic AI
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    6x Microsoft Applied Skills

    Discuss replacing Confluence

    In a no-obligation conversation, we work out how your Confluence content gets to SharePoint.