Note
Content Decision Lists are new in WikiTraccs 2, starting with release 2.0.12. More documentation will follow; this video is the first walkthrough.A Content Decision List (CDL) lets you decide for each page whether WikiTraccs migrates it, and to which SharePoint site. Each row of the list is one Confluence page. You set a Decision (include or exclude), a Target Site, and whether a setting also applies to the child pages below (Apply Below). The space selector in the Space Inventory stays as it is; the Content Decision List refines what that selector covers.
This video shows the whole flow end to end: one Confluence space is migrated to a default target site, while one page subtree (IT Security) goes to a separate site collection and an archive stays behind. On the way you see the Space Inventory of WikiTraccs 2, the new Sync CDL button, the full sync and the refresh of effective values, automatic target site creation, and the WikiPakk page tree on both target sites.
Prefer to read, or want to jump to a specific part? Each section below links to the matching moment in the video.
Related articles
A Content Decision List builds on the Space Inventory and on the source-to-target mapping. Waves are covered in Migration Waves.AI Note
The step-by-step instructions were automatically generated from the video transcript.What this walkthrough covers
Splitting one Confluence space across several SharePoint sites is a common requirement in migration projects. WikiTraccs could do it before, but the configuration was cumbersome. With Content Decision Lists you select single pages and subtrees and send them to different target sites. The video shows how.
▶️ Watch from the start · start 0:00 · duration 0:49
The demo space and the goal
The example space is IT Services of the demo company Wrenfield. The IT Security page and its whole subtree must land in a separate site collection, so the space needs two targets: one site for IT Services, another for the IT Security branch.
▶️ Watch this part · start 0:49 · duration 0:32
Connecting WikiTraccs to Confluence and SharePoint
WikiTraccs.GUI is already set up with the Confluence base address, the WikiTraccs site (here Wrenfield Migration Center), the tenant ID, an Entra ID application, and the Default target site (here Wrenfield IT Knowledge). The two connection tests confirm that WikiTraccs reaches Confluence and SharePoint; the SharePoint test also checks the default target site. The Getting Started guide covers this setup in detail.
▶️ Watch this part · start 1:21 · duration 2:02
Updating the Space Inventory and preparing the WikiTraccs site
With Update Space Inventory in WikiTraccs site, WikiTraccs first checks whether the WikiTraccs site has all lists, fields, and content types, and offers to create what is missing. This one-time preparation takes a minute or two per list, and a new status picture shows the site being put together. Then WikiTraccs reads all spaces from Confluence (43 in the demo) and stores their basic data in the Space Inventory list.
▶️ Watch this part · start 3:23 · duration 1:52
Choosing the space in the Space Inventory list
The Confluence Space Inventory (WikiTraccs) list has one row per Confluence space, with formatting, colors, and a bit of logic. Request Transformation marks a space for migration, and a filter on the new Space Labels column narrows the list to the Wrenfield spaces. We select IT Services for migration. This is a plain space selector, so starting the migration now would migrate the whole space.
▶️ Watch this part · start 5:15 · duration 2:22
Requesting a Content Decision List
To migrate only part of the space, the IT Services row also gets Request CDL in the CDL Enabled column, which asks WikiTraccs to create a Content Decision List for this selector. WikiTraccs.GUI then shows a new Sync CDL button next to Start transformation. The button appears the first time a selector uses a Content Decision List and then stays; without Content Decision Lists, this part of the user interface stays hidden.
▶️ Watch this part · start 7:37 · duration 1:22
Running the first full sync
Sync CDL offers two operations, Full sync and Refresh effective values. The first full sync opens the black console window like a migration, but it only does the first part of a migration: WikiTraccs reads all pages of the space from Confluence and writes one row per page into a new Content Decision List in the WikiTraccs site, about 340 rows here. The demo is quick because an earlier sync had cached the page data in the local database; the first sync of a space takes longer.
▶️ Watch this part · start 8:59 · duration 3:04
A first look at the Content Decision List
The Content Decision List mirrors the page tree of the space, starting with IT Services Home and its children. The yellow columns are the inputs you set. The grey columns are outputs that WikiTraccs calculates from them, above all Ready, which tells the migration whether a page may go. An Exclude decision, for example, turns Ready to No after the next refresh. The list also holds a review gate and page metadata.
▶️ Watch this part · start 12:03 · duration 2:25
Finding the subtree with the Level columns
Instead of scrolling, the video adds one of the hidden Level columns. Each Level column names the ancestor of a page at that level of the hierarchy, so a filter on Level 02 = IT Security shows exactly the pages of the subtree.
▶️ Watch this part · start 14:28 · duration 1:07
Routing the subtree to another site, and excluding the archive
On the IT Security row, Decision becomes Include, Target Site gets the URL of the Wrenfield IT Security site, and Apply Below becomes All. With All, every page below inherits the decision, the target site, and also the update mode and the wave. Child rows show Automatic, which means they inherit from above. The _Archive row gets Exclude with Apply Below All, so the whole archive stays behind.
▶️ Watch this part · start 15:35 · duration 2:13
Refreshing the effective values
The inputs take effect only after WikiTraccs calculates the outputs, which Sync CDL with Refresh effective values does. In the demo it checks 341 rows and updates 57. The archive pages now show Ready = No with the reason, an exclude decision inherited from the parent. The IT Security pages stay ready and show the IT Security site as Eff. Target Site; all other pages show the IT Knowledge site, the default.
▶️ Watch this part · start 17:48 · duration 2:18
Where the default target site comes from
The target site of a row comes from a cascade. The row uses its own or inherited Target Site, otherwise the Target Site URL of the selector in the Space Inventory, and otherwise the Default target site from WikiTraccs.GUI. In the demo the selector URL is empty, so the default applies. The Space Inventory row now also shows the CDL status, the page count, the lower Ready Page Count, zero transformed pages, and a link to the Content Decision List.
▶️ Watch this part · start 20:06 · duration 1:52
Starting the migration
With Start transformation, WikiTraccs reads the Space Inventory, finds the Content Decision List behind the selector, and takes the ready pages with their target sites from it. Because this is the first run against new sites, WikiTraccs also creates the Confluence User and Group Mapping (WikiTraccs) list, writes the 216 users it already knows from its local database, and prepares the Site Pages library of the default target site with a content type and fields for the migrated metadata. The status picture shows each site being built like a rack in a data center.
▶️ Watch this part · start 21:58 · duration 2:42
Automatic site creation and the page flow
The IT Security site does not exist yet. With the setting CustomSettings:SiteCreation:Enabled switched on, WikiTraccs creates missing target sites itself, which takes one to three minutes per site. Meanwhile 284 scheduled pages start flowing into the IT Knowledge site, and once the new site is ready, the IT Security pages go there. Later runs skip all this preparation. In the end, WikiTraccs has migrated more than 300 pages.
▶️ Watch this part · start 24:40 · duration 2:59
Checking the result in the Space Inventory and the Content Decision List
The Space Inventory now shows 335 transformed pages: every ready page went over and the excluded ones did not. The views of the Content Decision List show the migration state of each page next to its metadata and anomalies.
▶️ Watch this part · start 27:39 · duration 1:00
The target sites and the WikiPakk page tree
On the IT Knowledge site the pages sit in the Site Pages library, where a WikiTraccs view adds quality metrics per page. To see the hierarchy, the video adds WikiPakk, an optional SharePoint Framework app from Microsoft AppSource that understands the migrated metadata. Its page tree shows IT Services Home with its children, without the IT Security branch.
▶️ Watch this part · start 28:39 · duration 2:13
Fixing the parent of the migrated subtree
On the IT Security site, the subtree has lost its parent. In Confluence its parent is IT Services Home, which now lives in the other site, so the page tree shows nothing at first. The fix takes two actions: Move to tree root on the IT Security page makes it a root page in the WikiPakk tree, and Make homepage in the Site Pages library makes it the start page of the site. The tree then shows the whole subtree. Many more things are possible with Content Decision Lists; those are for another video.
▶️ Watch this part · start 30:52 · duration 3:15