A common setup: engineering lives in Azure DevOps (boards, repos, pipelines, plus the ADO wiki), while product, support and leadership live in Confluence. Sooner or later someone asks: should we migrate the ADO wiki into Confluence?
Before you start a migration project, it's worth asking what problem you're actually solving.
Why a full migration often disappoints
- The wiki keeps changing. Engineers keep editing in ADO because it sits next to their code. After the migration you have two versions.
- Links break. Work item links, query links and images need rewriting.
- Work items don't migrate at all. The real question is usually "how do non-engineers see what's happening in ADO?", and a wiki export doesn't answer it.
Migrate if you're retiring ADO wiki for good. If both tools stay, consider bringing ADO content into Confluence pages instead.
Bringing Azure DevOps content into Confluence
With an app like Azure DevOps Connector for Confluence (made by our team), you can add live Azure DevOps content with macros:
- Wiki pages: show an ADO wiki page inside a Confluence page, optionally with the wiki's page tree, so engineers keep editing in ADO and everyone else reads it in Confluence.
- Saved (shared) queries: for example "open bugs for release 4.2", optionally using the columns configured on the query in ADO.
- Single work items, showing the fields your Confluence admin configures.
- Pipelines and releases: current build and release status on a release page.
- Pull requests and source files for technical docs.
A pattern that works well
- Keep the engineering wiki in ADO.
- Create a Confluence "release hub" page per release.
- Add the saved query for that release, the pipeline status and the relevant wiki page.
- Share the Confluence page with stakeholders. It stays current because the data comes from ADO.
Things to know
- An admin connects Azure DevOps once with a personal access token, at global or space level, and pages render for everyone using that token's access. If you want each reader to see only what their own ADO permissions allow, turn on personal connections: each user then adds their own token.
- If you're truly consolidating on Confluence, a one-time migration is still the right call; embedding doesn't replace that.
Are you running both tools long-term, or planning to consolidate? Curious how other teams decided.
Further reading: How to use the macros, Get started for admins