Data Storage and Transmission
This article is a resource where you can find information about stored data and data transmission.
Security
This section covers security-related topics.
Architectural Overview of WikiTraccs
The following image shows which building blocks are at play when running a WikiTraccs migration. You find details about each building block in the table below the image.
The building block explained:
| Building block | Purpose |
|---|---|
| Client’s computer | A computer running WikiTraccs. Uses Windows as operating system. You control this computer. |
| WikiTraccs console applications (GUI, Console) | WikiTraccs consists of two .NET-based console applications: WikiTraccs.GUI.exe and WikiTraccs.Console.exe. WikiTraccs is portable, no installation is necessary. |
| Confluence | The source Confluence environment that should be migrated to SharePoint. You decide whether this environment is being connected to via HTTP or HTTPS by using the respective URL scheme (http://, https://) in the source address configuration of WikiTraccs. WikiTraccs’ TLS support is determined by the Windows host environment and the Confluence server. Note when enforcing TLS 1.3 with Confluence, you have to use a migration machine with a recent Windows version with proper TLS 1.3 support (Windows 11 or newer, Windows Server 2022 or newer). |
| Confluence migration account | The account used to log in to Confluence. WikiTraccs uses the session of this account and therefor has access to everything this account has access to. |
| SharePoint, MS Graph | The Microsoft 365 target environment that will be migrated to. All connections are HTTPS and TLS-secured. For the state of TLS in Microsoft 365 have a look at Preparing for TLS 1.2 in Office 365 and Office 365 GCC. As Microsoft deprecated connections via TLS lower than 1.2, at minimum TLS 1.2 will be used when connecting to Microsoft 365 services. |
| SharePoint migration account | The account used to log in to SharePoint. The permission that WikiTraccs has is the intersection of this user’s permission and the permissions configured for the Entra ID app registration. |
| Azure AD App Registration for WikiTraccs | Entra ID app registration that allows WikiTraccs to work with Microsoft services on an API level. See Registering WikiTraccs as app in Entra ID for details. |
| Locally stored files | WikiTraccs stores files locally on the system it runs. Those files comprise: attachments downloaded from Confluence, log files, caches, WikiTraccs.GUI configuration, debugging-related files (if certain debug settings are turned on) |
| Client’s migration team | This is your migration team. |
| WikiTraccs support | Support channels, mainly GitHub, email, and Microsoft Teams. Support might ask for log files to diagnose issues. You decide if you want to provide those log files. |
| Other services | See section Other Services below this table. |
Other Services
WikiTraccs has a minimum set of required endpoints that it needs when migrating data from Confluence to SharePoint Online. Those endpoints are documented in the WikiTraccs Endpoint Reference.
WikiTraccs might reach out to other service endpoints to enhance the migration tooling. No migration data is sent to other services except SharePoint Online.
Other service endpoints might be used for
- downloading the Google Chrome WebDriver
- downloading the Draw.io viewer
- checking for new WikiTraccs releases, or
- downloading external images.
Again, no migration data is transmitted to those endpoints.
Please refer to the WikiTraccs Endpoint Reference for a list of recommended and optional endpoints, as well as the article about locked down environments and the consequences of locking down: Locked-down environments.
Further Information
Endpoint Reference
This article is a resource where you can find endpoint information for WikiTraccs.
Running WikiTraccs in Locked-Down Environments
This article is a resource where you can find information about running WikiTraccs in locked-down environments.
Last modified July 22, 2025