Confluence: bring knowledge to order

Spaces nobody maintains. Pages nobody finds. And a move that takes along everything you wanted to get rid of. We help with the sorting.

What Confluence customers tell us

Five situations almost every grown Confluence instance knows.

Every project, every team, every person has a space. Many have been untouched for years, and nobody knows whether they are still needed.

Space permissions, page restrictions and groups overlap. Confidential material lies open, public material is locked.

The right page exists, but it sits at position forty behind meeting minutes from 2019. Search does not know about upkeep.

What must be retained belongs in an archive, not in a wiki. The export from Confluence delivers HTML or PDF, but no evidence.

Macros, templates and add-ons do not all come along. Pages look different at the target, and some content survives only as text.

Four steps, each with a result you can check.

Spaces, pages, access, macros, add-ons. What is read, what is maintained, what just lies around.

Cloud, Data Center or replacement. And for every space: keep, archive or delete.

Retention material into the DMS, living content to the new location, the rest gone. With a trial run and acceptance.

Monitoring, updates and support, in Switzerland. And rules for how spaces are created and retired in future.

We are building a knowledge base that follows Confluence's layout, with search, versions and filing in the DMS. It runs as a pilot with us.

doc.handel is a pilot, not a finished product. Whoever joins now helps decide what gets built next.

Send us a few sentences about your instance. We will come back with questions, not with a quote.

Atlassian, Jira and Confluence are trademarks of Atlassian Pty Ltd.