Documents from Confluence and your intranet wikiask your work instructions instead of clicking through spaces.

Wiki content sits in a database, not in folders. The plan is therefore an agreed, scheduled export of the chosen areas including attachments, sent encrypted and over outbound connections only to your instance; the page tree comes along as the origin, and a person confirms the suggested document type. Whether and how this can be automated — whether an interface exists, is enabled and reachable, and whether the account used is allowed to export spaces — we check with you before we start, depending on version, licence and hosting model. Until then you can upload exports by hand, as files or whole folders; a wiki in SharePoint can instead come across via a Microsoft 365 connection, which is likewise set up and billed by effort.

Once set up, synchronisation runs automatically: new and changed documents from Wiki and intranet are added by themselves, without anyone having to upload anything.

Set-upWe estimate the effort once it is clear which areas are to come across and which export route is available, and discuss it with you before anything is set up — ideally together with your wiki administrator. Billed by effort.

A connection is set up for you, not activated in one click. Every source comes with its own logins, permissions and folder logic — whether and how it can be connected at your company, we check together beforehand. Set-up and maintenance are billed by effort; how much that is depends on the source and is discussed beforehand.

Until then, and independently of it, you can upload files, whole folders, emails, photos and voice memos. Before we start, we go through real questions with you to see how the answers look.

Beforehand we look at which pages are outdated: many wikis carry older versions along, and the 2019 instruction often looks just as valid next to the current one. You decide which version applies — outdated content can be left out of the export or flagged in the collection; nothing in the wiki itself is touched. We also check how dynamically assembled content — embedded lists, status overviews, diagrams from add-ons, links into other tools — arrives in the export; depending on the add-on, this may be just an image or an empty spot. Whether page comments, older versions and unpublished drafts are included depends on the export route chosen; because the actual decision is sometimes in the comments, we agree on this together beforehand.