Migrating Page Author and Editor from Confluence to SharePoint (Video)
WikiTraccs can migrate the creator and editor of Confluence pages to SharePoint, so the migrated SharePoint pages carry the same author and editor information.
This video shows the whole flow end to end: migrating a small space, how WikiTraccs discovers users and automaps them to Entra ID, why some users map and some do not, and how to fix the rest with an update run and bulk pre-filling.
Prefer to read, or want to jump to a specific part? Each section below links to the matching moment in the video.
Written, step-by-step versions
This post follows the video. For the detailed write-ups, see Mapping user accounts from Confluence to SharePoint and Syncing and updating the user mapping list.AI Note
The step-by-step instructions were automatically generated from the video transcript.What this walkthrough covers
The plan: migrate a few pages, look at the result, see what gets automapped and what does not, find out which pages are done and which are not, adjust the user mapping, run an update run that updates the creator and editor on SharePoint, and finally look at bulk options for users and groups.
▶️ Watch from the start · start 0:00 · duration 0:56
The Confluence space and its three pages
The source is an old local Confluence Server with a space that has three pages: a home page, a “Collab Page Adele”, and a “Collab Page Megan”. The Adele page was created by Adele (who has an email address) and last edited by an automation system user that has no email set. The Megan page was created by Megan (who has a Gmail address) and edited by Adele. The missing email and the Gmail address both matter later.
▶️ Watch this part · start 0:56 · duration 1:06
Running the migration in WikiTraccs
WikiTraccs is already configured for this Confluence and SharePoint. The demo uses certificate authentication, so there is no interactive login. Two SharePoint sites are involved: the WikiTraccs site that the tool manages, and one target site where the pages are created. Hitting start kicks off the migration.
▶️ Watch this part · start 2:02 · duration 1:19
How users land in the mapping list
The WikiTraccs site holds one list of interest: Confluence User and Group Mapping (WikiTraccs). It starts empty. While migrating, WikiTraccs reads metadata about each page (who created it, who edited it, plus any @mentions) and adds every new user account it finds to the list. In this run that is three accounts: Adele, Megan, and the system user. The email address, key, internal name, and display name all come from Confluence.
▶️ Watch this part · start 3:21 · duration 1:42
Automapping to Entra ID: who maps and who does not
To set the author and editor on SharePoint, WikiTraccs needs an Entra ID account for each user. That target account goes in the Map for data and mentions column. WikiTraccs automaps by taking the Confluence email address and looking for an Entra ID user with the same email. For Adele this succeeds. For Megan it fails, because her Gmail address has no matching Entra ID account. For the system user there is nothing to look up, because it has no email.
▶️ Watch this part · start 5:03 · duration 1:03
Created by and Modified by on the migrated pages
Created by and Modified by are standard SharePoint page columns. On the Adele page, WikiTraccs correctly set Adele as creator, but Modified by shows SharePoint app. Two things combine here: when no mapping is available, WikiTraccs falls back to the migration account that logs in to SharePoint, and under certificate authentication that account is shown as SharePoint app. The system user has no email to look up, so it is not mapped, which is why it ends up as SharePoint app. The Megan page shows SharePoint app as creator too, because Megan is not yet mapped. Its Modified by is correctly set to Adele, who is mapped.
▶️ Watch this part · start 6:06 · duration 3:31
The Check Principal Mapping done indicator
WikiTraccs marks pages that still need work with the Check Principal Mapping column in the Site Pages library. You may have to add the column via Add column, then Show or hide columns. A tick means a mapping was missing. The space home page, created and edited only by Adele, was fully mapped during migration, so it has no tick. The update run only touches pages that have a tick. You can set a tick by hand to force an update, and WikiTraccs clears it once both creator and editor are set. This makes the process iterative: add mappings, run an update, repeat, and the ticks disappear over time.
▶️ Watch this part · start 9:37 · duration 1:50
Adjusting a mapping and running the update run
In the mapping list, Megan is mapped to a system account by hand (using the grid view). Then, back in WikiTraccs, the update run is configured under Settings, Configure transformation, by choosing Update ‘Created by’ & ‘Modified by’ of already migrated content. Everything else stays the same, and the transformation is started again. WikiTraccs now looks only at migrated pages that have the Check Principal Mapping tick and updates their author and editor from the mapping list.
▶️ Watch this part · start 11:27 · duration 2:28
Checking the corrected author and editor
After the update run handles the two flagged pages, the SharePoint pages reflect the mapping. The Megan page now shows Megan as creator and Adele as editor. The Adele page shows Adele as creator and the mapped system account as editor. The Check Principal Mapping ticks are gone. This is the happy path; some things can go wrong, but those are out of scope for this video.
▶️ Watch this part · start 13:55 · duration 1:06
Pre-filling the list with Sync and Update User List
The mapping list normally grows while migrating, but you can also pre-fill it beforehand. Under Tools, Sync & Update User List (with content migration mode switched on), WikiTraccs first syncs the SharePoint list with its local cache. You then name one or more Confluence groups to pull members from. In the demo, a “space migration users” group with three members (Adele, Megan, the system account) is used.
Confluence Cloud
As of WikiTraccs v1.34.50, the Sync & Update User List tool also works with Confluence Cloud: it can discover groups and their members (by group name, or across all groups) and write them into the mapping list. Confluence Cloud’s group APIs do not return email addresses, though, so the email column stays empty on this path; you can add the emails via CSV import. On Confluence Data Center and Server, like in the video, emails are fetched directly (when email visibility is enabled in the Confluence administration).▶️ Watch this part · start 15:01 · duration 1:15
Fallback account and what stays manual
A fallback account can be set for users without a Confluence email, which is handy when you have many email-less system accounts that should all map to the same Entra ID account. After the run, Adele is automapped by email, the system account (no email) gets the fallback, but Megan stays empty. Her Gmail address is present, so the fallback (which only applies to empty emails) does not touch her, and there is no matching Entra ID account to automap to. Accounts like Megan are manual work: leave them unmapped (their pages get the migration account as author), or map them by hand or with a script such as PnP PowerShell.
▶️ Watch this part · start 16:16 · duration 3:51