RSS

Question Time November 2025

This post covers some of the recent questions around WikiTraccs and WikiPakk

I got the following questions.

  1. How to migrate a page that has been updated in Confluence?
  2. Is there a migration report showing whether a space has been completely migrated to SharePoint?
  3. Is it possible to hide the remains of (defunct in SharePoint) macros on the migrated pages?
  4. How to check how many cross-space links there are in a Confluence space?
  5. We want to keep the links to Confluence in some spaces - is that possible?
  6. We want to rewrite some of the migrated Confluence-links to a new Confluence instance - is that possible?
  7. Should the migration run as system user or personal account? Where is the name of this account surfaced in SharePoint?

Let’s dive in.

1. How to migrate a page that has been updated in Confluence?

If - after a migration - users keep working on pages in Confluence, you might end up with already migrated pages that were updated in Confluence since the migration.

WikiTraccs can detect those pages and can overwrite the already migrated pages in SharePoint Online.

Have a look at Updating Previously Migrated Pages to learn how to do that and some constraints that apply.

2. Is there a migration report showing whether a space has been completely migrated to SharePoint?

Yes.

First of all, there are two simple number indicators available in the Space Inventory, showing how many pages where found for each source selector and how many have been migrated to SharePoint.

You can gain deeper insights using progress log files. Please refer to the following article for details: Monitoring Confluence to SharePoint Migration Progress - Overview.

3. Is it possible to hide the remains of (defunct in SharePoint) macros on the migrated pages?

Yes, for many macros.

WikiTraccs will add macro placeholders to migrated pages showing that a macro had no representation in SharePoint and that it thus was replaced by a text placeholder. Read more about the general approach here: Macro Placeholders. This page also shows where to find transformation templates that WikiTraccs internally uses.

You can change the placeholder texts for most macros, using Macro Transformation Templates.

4. How to check how many cross-space links there are in a Confluence space?

WikiTraccs automatically transforms all Confluence-internal links to proper SharePoint links. This covers cross-space links.

As of now, there is no output of links that would be accessible for you.

5. We want to keep the links to Confluence in some spaces - is that possible?

There is an appsetting.json-based setting that can be used to keep the Confluence links if a target site cannot be resolved.

{
  "CustomSettings": {
    "Features": {
      "LinkTransformationMode": "needexplicittargetsite"
    }
  }
}

If a target site cannot be determined based on a space inventory mapping, the original Confluence link will be kept.

This might help, although this is a rarely used feature.

6. We want to rewrite some of the migrated Confluence-links to a new Confluence instance - is that possible?

As of now, there is no way to configure the link transformation such that you could rewrite Confluence-internal links.

7. Should the migration run as system user or personal account? Where is the name of this account surfaced in SharePoint?

For Confluence, use a migration account that is space owner in all to-be-migrated spaces. But better, us a Confluence admin. Administrative access allows retrieving metadata related to user account, page restrictions, and restricted page contents.

For SharePoint Online no system admin permissions of any sorts (SharePoint admin, tenant admin, …) are required. Use a user account that is site owner in all target sites for the migration. This level of access allows setting the creation and modification dates of pages, as well as author and editor.

The M365 migration account is used to create SharePoint pages and might be shown as author and editor of pages and files. You can configure a user mapping to show the original Confluence users instead. Read more about that here: Mapping user accounts from Confluence to SharePoint.

Consider using accounts that don’t have a forced reauthentication configured as this might temporarily interrupt the migration until you reauthenticate.