Skip to main content
TheDocs
Sign in Book a Demo
Feature

Bring your documentation with you

Migration is where most knowledge base projects stall. Structure, images, internal links and redirects come across - and the import report tells you exactly what needs a human.

Start free trial Book a demo
  • Nine source formats
  • Redirect map generated
  • Honest import report

How do I migrate documentation to TheDocs?

Connect the source or upload an export, map the source structure onto TheDocs categories, then run the import. Headings, lists, tables, code blocks, images and internal links are converted to native content; images are downloaded into your media library rather than hotlinked; and internal links are rewritten to their new destinations. The importer produces a redirect map from your old URLs and a report listing everything that needs manual attention before you publish.

  • Sources: Confluence, Notion, GitBook, Zendesk Guide, Help Scout, Markdown, Word, Google Docs, PDF.
  • Structure mapped to categories, with a preview before anything is written.
  • Images downloaded and re-hosted; internal links rewritten.
  • Redirect map generated from your old URLs, editable before publish.
  • Import report lists unconverted macros and anything needing a human.
  • Dry run first - nothing is published until you say so.
Process

How a migration runs

  1. 01

    Connect or upload

    Authorise Confluence or Notion directly, or upload an export file. Nothing is written to your workspace at this stage.

  2. 02

    Map the structure

    Preview the source tree and map spaces, collections or folders onto TheDocs projects and categories. Exclude what you do not want to bring.

  3. 03

    Dry run

    Import into a draft project. Read the report, spot-check the conversions, and fix the mapping. Repeat as often as you like.

  4. 04

    Publish with redirects

    Approve the redirect map and publish. Old links resolve to new articles from the moment you go live.

In detail

What actually happens to your content

Per-source specifics

Every source has its own quirks. Knowing them in advance is the difference between a two-day migration and a two-month one.

  • Confluence: spaces map to projects, page trees to category hierarchies. Standard macros - info, note, code, expand, table of contents - convert to native blocks. Unsupported third-party macros become a flagged callout rather than silently vanishing.
  • Notion: databases become categories with properties preserved as metadata; toggles become accordions; synced blocks become snippets.
  • GitBook: near-native, including versions and multi-language sets where they exist.
  • Zendesk Guide and Help Scout: categories, sections and articles map directly, and article IDs are kept in the redirect map.
  • Markdown: front matter becomes metadata, relative links are rewritten, and directory structure becomes categories.
  • Word and PDF: headings become structure where the source used real heading styles. Visually-formatted documents need the most review.

The import report is deliberately blunt. We would rather tell you about 40 pages needing attention up front than have you find them in production.

Not losing what you have earned

A documentation site that has been live for years carries search rankings and thousands of external links. Migration should not reset that.

  • A 301 redirect map generated from every source URL, editable in bulk or as CSV.
  • Redirect hit reporting after launch, so you can see anything you missed still being requested.
  • Canonical tags and sitemap regenerated on publish and submitted automatically.
  • Optional parallel running: publish to a staging domain, compare, then switch DNS.

Thinking about switching?

TheDocs vs Help Scout Docs

Workflow, versioning and localisation that a lightweight docs add-on skips.

Confluence Alternative

Move customer-facing pages out of the wiki without losing internal docs.

GitBook Alternative

Keep Git-style authoring, add the help-centre features GitBook leaves out.

TheDocs vs Notion

Purpose-built publishing instead of a workspace pressed into service.

TheDocs vs Zendesk Guide

A help centre you can keep even if you change your ticketing vendor.

Built-In SEO

Clean URLs, structured data, sitemaps and metadata on every article.
Frequently asked

Questions people ask before they start

Confluence (Cloud and Server), Notion, GitBook, Zendesk Guide, Help Scout Docs, Markdown repositories, Word documents, Google Docs and PDFs.

Yes. The importer builds a redirect map from your old URLs to the new ones. Review and edit it before you publish, then it goes live with the content so external links and rankings survive.

Confluence macros with no equivalent - some third-party macros in particular - become a callout flagging what was there. Complex page layouts simplify. PDFs with heavy visual layout need the most manual work. The import report lists every one of these so nothing is a surprise.

A few hundred articles usually import in under an hour and need a day or two of review. Thousands of pages, or a Confluence space with heavy macro use, take longer. We scope it before you commit.

Guided migration is included on Business and managed migration on Enterprise. On smaller plans we still run the first import with you on a call and hand over a repeatable process.

Send us twenty pages and we will import them before your demo.

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.