Skip to main content
TheDocs
Sign in Book a Demo
Alternative

A Confluence alternative for the documentation with real readers

The advice most vendors will not give you: keep Confluence. Move the pages that customers, partners or auditors read, and leave the wiki doing what it is good at.

Start free trial See the feature comparison
  • Split by audience
  • Macros mapped or flagged
  • Redirects generated

Should you move off Confluence?

Only for the content that has readers who are not the authors. Confluence is a wiki - optimised for capture and collaboration - and it is genuinely good at that. Customer-facing documentation and controlled procedures have different requirements: a branded public portal, SEO, reader-facing versioning, approval before publishing, review cycles, and search that returns an answer. The usual outcome is a split: Confluence keeps project work, TheDocs takes published documentation.

  • Keep Confluence for project pages, notes and internal collaboration.
  • Move: help centres, product docs, SOPs, partner and audited content.
  • Spaces map to projects; page trees map to category hierarchies.
  • Standard macros convert; unsupported ones become flagged callouts.
  • 301 redirect map generated from your Confluence URLs.
  • Cross-linking both ways, so neither system becomes an island.
Process

How the split usually goes

  1. 01

    Draw the line by audience

    Not by team. If the readers include people who cannot edit the page - customers, partners, auditors, new joiners - it belongs in TheDocs.

  2. 02

    Decide what not to bring

    Most Confluence spaces contain years of pages nobody has opened. Sort by view count and be ruthless. This is the step that determines how long the project takes.

  3. 03

    Dry run and read the report

    Import into a draft project. The report lists every unconverted macro and every page needing attention, ranked by traffic.

  4. 04

    Publish with redirects

    Approve the redirect map and go live. Optionally leave stubs in Confluence pointing at the new home for internal readers.

In detail

The parts that need attention

Macros, honestly

Macros are the reason Confluence migrations have a reputation. Here is exactly what happens to them.

  • Converted to native blocks: info, note, tip, warning, code, expand, table of contents, status, task list, table, panel.
  • Converted with adjustment: page tree becomes navigation; include and excerpt become snippets; children display becomes a category listing.
  • Flagged, not silently dropped: third-party macros, Jira issue macros with live queries, and anything rendering dynamic content. Each becomes a callout naming what was there.
  • The report ranks flagged pages by traffic, so you fix the ones people actually read first.

Teams are often surprised by how many flagged items sit on pages with almost no traffic. Those are usually a delete decision, not a migration one.

Living with both

A split only works if neither system becomes a dead end.

  • Confluence pages can link into TheDocs articles and vice versa; internal links are rewritten on import.
  • Stub pages left in Confluence pointing at the new location, for internal readers who bookmarked the old one.
  • A clear rule for the team: if it will be read by someone who cannot edit it, it goes in TheDocs.
  • Content that starts as a Confluence page and matures into documentation gets promoted once it stabilises.

Related

TheDocs vs Confluence

A public-facing knowledge base instead of a wiki bolted onto an intranet.

Import & Migration

Move in from Word, PDF, Confluence, Notion, GitBook or Zendesk Guide.

Internal Knowledge Base

One private home for the answers your team keeps re-asking in chat.

What Is a Knowledge Base?

Types, components and how a knowledge base differs from a wiki or CMS.

How to Structure Product Documentation

An information architecture that scales from 20 articles to 2,000.

Pricing

Flat per-project pricing with unlimited readers on every plan.
Frequently asked

Questions people ask before they start

Usually not. Confluence is good at internal collaboration - project pages, meeting notes, in-progress thinking. The case for moving applies to documentation with external readers or a review cycle. Most teams end up running both, split by audience rather than by department.

Standard macros - info, note, warning, code, expand, table of contents, status - convert to native blocks. Third-party macros with no equivalent become a flagged callout naming what was there, so nothing disappears silently. The import report lists every one, ranked by page traffic.

A space of a few hundred pages imports in under an hour. Budget two to four weeks end to end for a real migration - most of it is deciding what not to bring, which is time well spent.

A 301 redirect map is generated from your Confluence URLs. If Confluence stays live for internal content, you can also leave stub pages pointing at the new location.

Yes - create a Jira issue from a content gap and link articles to the tickets that prompted them. It is not the native depth Confluence has, and if tight Jira coupling is essential, weigh that.

Import one space. Read the report before you commit to anything.

Start free for 14 days. No credit card, no setup fee, and your content is yours to export at any time.

Start free trial Book a 30-minute demo

Questions first? Email sales@thedocs.in or call +91 8585953085.