How do I migrate from Confluence Data Center?
Huddo Wikis is a self-hosted wiki you can migrate to without going to cloud. ISW provides a fully managed migration service — technical migration, change management, and training. You are not doing this alone.
Most organisations evaluating alternatives are not doing so because they dislike Atlassian.
They are doing so because Confluence Cloud is not available to them — or because the cost of going there does not make sense. The most common reasons:
If any of these apply to your organisation, Confluence Cloud is not a migration path. It is a constraint. You need an alternative.
A self-hosted wiki built for organisations that cannot go to cloud.
Huddo Wikis is a self-hosted wiki platform developed by ISW, an Australian software company with 30+ years of enterprise software experience. It runs on your infrastructure — on-premises, in a private data centre, or on any hyperscaler of your choice.
No American cloud required. No US Cloud Act exposure. No vendor controlling access to your organisation's knowledge base.
It integrates natively with HCL Connections and Domino for organisations in the HCL ecosystem. For organisations with no HCL footprint, it runs as a standalone platform.
Watch Huddo Wikis in action.
The editing interface, space structure, access control, and a real Confluence migration — in under five minutes.
What migrates from Confluence DC to Huddo Wikis?
This is the question every technical evaluator needs answered before anything else. Here is an honest answer.
- Pages and page content
- Page hierarchy and space structure
- Attachments
- Page and space permissions
- User accounts and group memberships
- Macros — ISW documents which migrate automatically, which need manual substitution, and which have no equivalent
- Custom themes and design elements
- Third-party app data
- Confluence-specific analytics and reporting
- Page ratings and reactions
- Marketplace app configurations
The goal is that your team lands in Huddo Wikis with their content intact and structured the way they recognise it — not a flat file dump they have to reorganise from scratch.
What does ISW's migration service include?
This is where ISW differs from a migration tool you run yourself.
Before anything moves, ISW audits your Confluence environment: space count, page count, attachment volume, macro usage, custom integrations, and user count. You get a written scope document that tells you exactly what will migrate, what will need manual work, and what the timeline looks like.
ISW runs the migration. Content, structure, permissions, and user accounts are transferred. You are not handed a tool and a documentation page.
After migration, ISW validates the output against your Confluence environment. We check that spaces are intact, pages are structured correctly, and attachments are accessible. Issues are resolved before you go live.
Your team needs to switch platforms. ISW provides guidance on the transition: communication templates, training materials, and a go-live plan that accounts for how your teams actually work.
ISW delivers end-user training for Huddo Wikis. We cover the editing experience, navigation, search, and space management for the users who will use it daily — not just the administrators.
ISW is available for questions and issues after go-live. You are not handed off to a ticket queue.
How long does a migration take?
Depends on the size and complexity of your environment. ISW scopes each migration individually — these are typical ranges.
If your environment is large, starting the scoping conversation early gives you enough runway to migrate cleanly before the March 2029 deadline, without a last-minute rush.
The Huddo product family — Wikis, Boards, and Ideas — is used by organisations in government, education, healthcare, and financial services across Europe, Australia, and North America. Every product runs on the same infrastructure standards and is built and supported by the same ISW team.
How does Huddo Wikis compare to the alternatives?
Frequently asked questions
No. Huddo Wikis runs as a standalone platform. HCL Connections integration is available for organisations already in the HCL ecosystem, but it is not required. If your only requirement is a self-hosted wiki to replace Confluence DC, Huddo Wikis works without any other HCL product.
You keep running Confluence DC while the migration is in progress. There is no forced cutover until you are ready. ISW's migration runs in parallel — your team continues working in Confluence, and the migration is validated before anyone switches over.
Yes — if you can run Kubernetes, you can run Huddo Wikis. The deployment requires:
- A Kubernetes cluster with an ingress / reverse proxy (on-premises, private cloud, or managed K8s service)
- An identity provider for SSO — Microsoft AD and Auth0 are confirmed working today via pre-built connectors
- Optionally an SMTP gateway for email notifications
Installation is a Helm chart. If your organisation already runs Confluence DC on-premises, you almost certainly have the infrastructure required.
ISW has partners in Europe. ISW's support team covers European business hours. Contact us to discuss support availability in your region.
Yes. Book a demo with the ISW team. We will show you the product, walk through a migration scenario relevant to your environment, and answer your technical questions. No commitment required.
Migration is scoped and priced per engagement. The main factors are environment size (pages, spaces, attachments), macro complexity, and the level of change management and training required. Contact ISW for a scoping conversation — we will give you a written estimate before any work begins.
What you need to know before migrating from Confluence DC.
Ready to evaluate Huddo Wikis for your migration?
The research phase is now. We are ready when you are.