Note
Links to additional Frequently Asked Questions (FAQs) can be found at the end of this guide.
This article answers common questions about how Teams migrations handle Teams Channel Selection. It also helps you troubleshoot common issues, so you can find out why a channel did not migrate as expected and how to fix it.
Teams Channel Selection FAQs
This section answers common questions about how to choose which channels are included in a Teams migration.
Does anything change for Teams I do not filter?
No. Without a saved filter a Team migrates exactly as before.
Can I choose posts separately from channels?
No. Posts follow their channel.
Are shared channels migrated?
No. They are listed in the filter but cannot be selected.
If I untick a channel, are its files skipped too?
Yes. Its posts and its folder in the default library are skipped when the folder has the channel name. For a private channel its library is skipped too.
Can I skip the Shared Documents library?
No. The default library is always migrated.
How do I migrate a Team's extra document libraries?
Add them to the TeamsDocumentLibraryMapping advanced option. The filter screen does not list libraries.
How can I tell whether a Team is filtered?
Its row shows a badge such as Filtered - 3 ch after any filter is saved, even if every channel is still ticked. Click the funnel icon to see what is actually ticked.
I added a channel at the source after saving the filter. Will it migrate?
No. Open the filter, tick it and save again.
Where did the project folder filter go for Teams?
It is hidden for Teams projects unless it already has a value. Unticking a standard channel skips its folder.
Did licensing change for Teams?
No. Each Team still uses a Teams license, and the 100 GB license types cover up to 100 GB. A larger Team uses more licenses only if Maximum number of licenses to consume per item: is more than 1.
Teams Channel Selection Troubleshooting
This section describes common issues that can cause a channel to be missing or not selected during Teams migrations. For each issue, it explains the likely cause and the steps to resolve it.
| Symptom | Cause | Resolution |
|---|---|---|
| Picker shows We couldn't load the discovered Teams for this discovery run... | A temporary error, or the run was made before Team selection existed | Choose the run again with View Results, or run autodiscovery again. Contact support if it keeps failing |
| There is no Import Items button on my discovery run | Teams projects import from the picker now | Use Import Items in Discovered Microsoft Teams |
| Some ticked Teams were not imported | A search was active, so only the Teams shown were imported | Clear the search and click Import Items again |
| Import failed. | The run was made before Team selection existed, or a temporary error | Run autodiscovery again |
| Filter screen shows We couldn't load this Team's channels and libraries... | The Team cannot be found at the source, or the project uses an older (non parallel) Teams endpoint | Check the source Team. Close and reopen the filter |
| Select at least one channel. and Save is disabled | No channel is ticked | Tick at least one channel |
| The filter could not be saved. Please try again. | Saving failed | Try again. Contact support if it keeps failing |
| The funnel icon is greyed out | A migration of that item is in progress | Wait for the migration to finish |
| An extra library was not migrated | Extra libraries cannot be picked in the filter | Add the library to the TeamsDocumentLibraryMapping advanced option and run again |
| Site Assets migrated although I did not want it | Site Assets always migrates unless TeamsSkipSiteAssets is set | Set the TeamsSkipSiteAssets advanced option |
| Badge shows Filtered but nothing seems left out | The badge shows after any saved filter, even when every channel is ticked | Open the funnel icon to check what is ticked |
| Posts of a channel are missing | The channel is unticked, or it was created after the filter was saved | Tick it, save, and run again |
| Files of an unticked channel were still migrated | The channel folder name does not match the channel name, or the filter was ignored because it was saved for a different Team | Check the folder name. Contact support with the line item details |
| Some folders are missing | They have the name of a channel the filter leaves out, match the old project or line item folder filter, or match a folder pattern saved before libraries were removed from the filter | Check the ticked channels and the old folder filters. Save the filter again to clear old folder patterns |
| Warning: the channel scope was saved for a different team | The line item Team changed after the filter was saved | Open the filter and save it again |
| Picker counts show 0 | The counts for that Team could not be read | Expected now and then. The Team still imports normally |
| I cannot find the folder filter in Advanced Options | Hidden for Teams projects unless a value is already set | Untick a standard channel to skip its folder |
| Migration stopped once a Team reached 100 GB | The license 100 GB limit was reached and the project allows one license per item | Raise Maximum number of licenses to consume per item: and run again |
Messages You May See
This section lists the messages you may see during migration and explains what each one means and how to respond.
| Message | Meaning and action |
|---|---|
| Shared channels are not supported for migration and cannot be selected | Tooltip on shared channels. They are never migrated |
| Domain validation failure prevented some items from being imported | Some Teams failed domain validation, so they were not imported |
| This folder filter still applies to the whole Team. Clear it and use the per-library folder filters in the Teams scope filter instead | Shown next to an old folder filter that still has a value. The per-library filters it mentions are no longer in the filter screen |
| {library} : The folder filter '{pattern}' took too long to evaluate on some folders, so those folders were skipped. Simplify the filter | Only for filters saved before libraries were removed from the filter screen. Save the filter again to clear the pattern |
| {library} : The folder filter '{pattern}' is not a valid regular expression, so no folders of this document library are migrated. Correct the filter and run the migration again | Same as above |
Still need help?
Contact support and include:
- the project name and the line item that shows the problem.
- the exact message you see, copied as written.
- the date and time of the run or pass.
- a screenshot of the line item or screen.
Related Topics
- Flex Collaboration License Frequently Asked Questions and Troubleshooting
- Version History Frequently Asked Questions and Troubleshooting
- Permission Fidelity and Re-sync Frequently Asked Questions and Troubleshooting
- Metadata Migration Frequently Asked Questions and Troubleshooting
- SharePoint Sites Site Level Content Frequently Asked Questions and Troubleshooting
- SharePoint Sites Sensitivity Labels and Encryption Frequently Asked Questions and Troubleshooting
- SharePoint Sites Migrations Frequently Asked Questions and Troubleshooting