Wikinest Confluence Import

What it is for

Moving a team wiki is mostly about keeping the content intact. You want the page tree, the info and warning panels, the code blocks, the tables and the links between pages. This tool reads the HTML export of a Confluence space, or the HTML of single exported pages, and turns every page into Markdown in the Wikinest dialect. It also rebuilds the tree from the breadcrumbs.

The result is a list of pages with their parents and word counts, the Markdown of all pages and a Wikinest project file you can open in the app. The tool does not connect to Confluence. It only reads the files you give it.

To get the files in Confluence, open the space and choose Space settings → Export space → HTML. You get a ZIP file with one HTML file per page and an attachments folder.

Worked example

The built-in example is a small team space with three pages: a home page, a release checklist and a decision log. The tool answers:

Imported 3 pages of “Orbit Team” from Confluence into Wikinest Markdown.

The metrics show 3 pages, 5 panels and expand sections, 1 code block, 1 table, 3 tasks, 2 links between pages, 2 mentions and 1 image. One macro has no Wikinest equivalent. Its text is kept, and a warning says so. The Pages table shows that Release checklist (60 words, 1 image) and Decision log (26 words) sit under Orbit Team Home.

The home page begins like this in Markdown:

Welcome to the **Orbit** team space. Start with the [[Release checklist]].

{{toc}}

The Confluence link to the checklist became a [[Release checklist]] page link. The table-of-contents macro became {{toc}}.

How to read the result

• Pages lists every page with its parent. An empty parent (—) means the page is at the top of the space.
• The mapping table shows what each Confluence element became. Info, note, tip and warning macros become info, warning, success and error panels. Code macros become fenced code with the language, and status macros become {status:colour|TEXT}.
• Unmapped macros counts macros the tool did not know. Their text stays in the page so nothing is lost, but check those places by hand.
• Images are listed as attachment references. The project file does not contain image files. Import the ZIP in the app instead to attach them.

Tips and common mistakes

• Upload the whole ZIP rather than single pages. Only then can the tool rebuild the tree and turn links into page links.
• If you paste HTML, paste the complete page files one after another, including the title. The tool splits them at each new document.
• Page titles come from the export, without the “Space name :” prefix Confluence adds.
• Comments, page history and permissions are not part of a Confluence HTML export, so they cannot be imported.
• Use Space name to give the new space a different name than the one in the export.

FAQ

Do I need a Confluence account or API token?

No. The tool only reads the export files. Nothing is sent to Atlassian.

What happens to images?

The tool lists them as attachments. In Wikinest, choose Import → Confluence export and pick the ZIP. The app then attaches the image files from the export to the pages, within your storage quota.

Can I import into an existing space?

In the app, yes: the import dialog lets you choose an existing space or a new one. The tool always creates one new space in its project file.

Is the mapping lossless?

Text, structure, tables, code and the common macros come through. Layout details such as column sections, colours of panels and page-specific styling are simplified to plain Markdown.