Include/Exclude Filters
This article explains how ad-hoc include/exclude filters work and how to combine them with waves.
You can assign waves to your content selectors in the Space Inventory.
When starting a migration, you can optionally specify the waves to migrate.
In the context of WikiTraccs, waves are labels that you assign to selectors in the Space Inventory.
Those labels can be:
1, 2, or 100pilot, review, or archiveWhen starting a migration you can tell WikiTraccs which of those waves it should migrate.
Using waves you can prepare a multi-wave migration where each wave is assigned the same label.
Let’s look at an example:
Wave 1: Project Teams and Miscellaneous
Wave 2: Client-Facing and Support Departments
Wave 3: Core Operational Departments
When configuring what to migrate in the Space Inventory, you use the WT_Setting_Waves column to assign a wave it belongs to.
Here’s what the Space Inventory list might look like:
| WT_In_CfSpaceName | WT_In_CfSpaceKey | Wt_Setting_RequestTransformation | WT_Setting_Waves | WT_Setting_TargetSiteRootUrl |
|---|---|---|---|---|
| Project Alpha | PALPHA | x | 1 | https://contoso.sharepoint.com/sites/ProjectAlpha |
| Project Beta | PBETA | x | 1 | https://contoso.sharepoint.com/sites/ProjectBeta |
| Miscellaneous | MISC | x | 1 | https://contoso.sharepoint.com/sites/Miscellaneous |
| Marketing | MRKT | x | 2 | https://contoso.sharepoint.com/sites/Marketing |
| Sales | SALES | x | 2 | https://contoso.sharepoint.com/sites/Sales |
| Customer Service | SERVICE | x | 2 | https://contoso.sharepoint.com/sites/CustomerService |
| HR | HR | x | 3 | https://contoso.sharepoint.com/sites/HR |
| Finance | FIN | x | 3 | https://contoso.sharepoint.com/sites/Finance |
| IT | IT | x | 3 | https://contoso.sharepoint.com/sites/IT |
Note: Other columns have been omitted for brevity.
With this configuration everything is prepared for a 3-wave migration.
Wave numbers are supposed to be:
Wave numbers don’t have to be consecutive. For example using 100, 200, and 300 (instead of 1, 2, and 3) is fine.
Wave names are also supported (note: starting with WikiTraccs v1.33.0).
Wave names are not case-sensitive. For example, pilot, Pilot, and PILOT all refer to the same wave.
Wave names:
*:;#+Examples: pilot, review, archive2026
In WikiTraccs.GUI you can enter wave clauses into the Waves & filters text box right above the Start transformation button:

You can choose multiple waves to migrate.
Use commas, spaces, or a mix of both to separate wave clauses (note: only commas are supported prior to WikiTraccs v1.33.0).
Here are supported ways of selecting waves:
| Wave selection example | Description |
|---|---|
| 1 | Migrate wave 1 |
| 1 2 3 | Migrate waves 1, 2, and 3 |
| 1,2,3 | Migrate waves 1, 2, and 3 |
| 1-3 | Migrate waves 1, 2, and 3 |
| 1,4-6,8 | Migrate waves 1, 4, 5, 6, and 8 |
| pilot | Migrate the named wave pilot |
| pilot review | Migrate the named waves pilot and review |
| pilot, 2, review | Migrate the named waves pilot and review and wave 2 |
| -4 | Migrate all waves up to and including 4 |
| 4- | Migrate all waves equal to or greater than 4 |
| 1,4- | Migrate wave 1 and all waves equal to or greater than 4 |
| * | Migrate all selectors with wave configuration, but skip selectors with empty WT_Setting_Waves column |
| Migrate all selectors with checked Wt_Setting_RequestTransformation column |
Waves are used to partition the migration into different chunks.
Those chunks can then be
Have a look at the How to run parallel WikiTraccs migrations blog post about the latter use case.
This article explains how ad-hoc include/exclude filters work and how to combine them with waves.