Excluding Folders

Exclusions are only available in multi-destination mode. They're the mechanism for saying "don't migrate this folder, but do migrate everything around it."

Why exclude?

Typical reasons:

• Temp/cache folders — ~snapshot, .DS_Store directories, backup artifacts
• Out-of-scope data — personal folders inside a departmental share
• Known bad data — folders with broken file names, corrupted files, or stuff the client confirmed they don't need

Exclusions don't delete anything from the source; they just tell CloudMove not to migrate that content.

Exclude a folder

In the source tree (multi-destination mode), click the folder and choose Exclude from the destination choice modal.

The folder appears in the Excluded tab on the right. Its children inherit the exclusion — nothing inside gets migrated.

Override an exclusion on a child

Excluding a parent and then mapping a specific child to a destination does re-include that child. The most specific mapping wins.

Example:

• \\fileserver\Archive → Excluded
• \\fileserver\Archive\2025 → mapped to SharePoint

Result: only \\fileserver\Archive\2025 migrates. Everything else under Archive is skipped.

Remove an exclusion

In the Excluded tab, click the undo icon on any entry. The folder reverts to unmapped and will inherit its parent's destination again.

Scan vs migration

Scans still analyze excluded folders — you'll see their issues in scan results. But during migration, excluded folders are entirely skipped.

This is intentional: the scan shows you what's in the source, even if you're not migrating it. Helps when you want to double-check before finalizing exclusions.