Add Custom Rules and Filters During Migration or Import
[Admin note: Merged all suggestion related to more complex filtering during Migration or Import]
- Filter on full file names instead of just exensions.
- Filter with wildcards
- Include / Exclude folder by name using the custom templates
- Exclude specific (sub) folders based on names
- Timestamp/range filters - last modified date and created date
- List or site template filters
- Filter by property (name, type, etc.)
- Filter by size
- Filter empty objects (sites, libraries, folders, ...)
- Exclude specific type of objects (Microfeed...)

We feel like our migration experience is quite good right now and we don’t plan on doing custom rules and filters for now.
Some of those can already be done using PowerShell, SharePoint views and other means.
We will eventually reevaluate this once we advance further in our roadmap.
-
Anonymous commented
Agreed I would love to be able to excluded certain files for a File Share to OneDrive migration. For instance "Desktop" because this is be handled via folder redirection.
-
Anonymous commented
I'd like to be able to apply multiple filters. This would super handy for cleaning up content as it comes across from a file share.
For example, I want to exclude the any files matching the following exact filenames:
Thumbs.db
.DS_Store...as well as any temporary files that match the following wildcards (where the asterisk "*" is the wildcard):
~$*.*
*.tmpBeing able to apply all of these filename filters would be amazing. Thanks! :)
-
Hello Martjin,
When copying content though a Powershell script, the time range filter is available by creating a property template. You can find more info on the subject here: https://support.share-gate.com/hc/en-us/articles/115000598707-New-Property-Template
-
Martijn de Bont commented
Timerange is available from the UI (thanks!)
But I am wondering how to set this up for powershell, or when this feature is coming? -
Michael Williams commented
Hi just wondering if this feature exists or has been considered, however quite often during migrations we end up migrating empty folders. For example, due to certain rules we set (e.g. restrict file types or disable migrating files older than a set date) it's quite often when migrating a folder moves, however the contents are empty as the files don't meet the criteria we want to migrate. Would it be possible to have an optoin "Not to migrate empty folders"
Kind Rgds,
Mike -
Anonymous commented
Please add the ability to skip the migration of a specific site object when using the Copy Structure migration tool. It would be great if I could skip this really big list that is slowing down my migration, without disturbing the rest of the migration. This could be an option in the migration's task view if I right click on a site object that is in the "Started" status.
-
Naval Verma commented
filter at List / library level
filter at item level -
Jeroen Schoenmakers commented
Straight from the logging interface ->exclude this item (or wildcard) in next migration which then writes to the exclude xml you can reference to in the PowerShell commands..
-
Ed Williams commented
It would be great if we could deselect certain libraries/lists and Pages from the migration like is done with most Backup software. Right now I have about 300 errors I have to fix to migrate over, it would be easier to deselect many of them and recreate the ones with the errors on my own.
-
Victor commented
When importing from a FileShare, the "Filter by time range" feature will use the latest date between created and modified values. This can pose a problem since moving a file within a FileShare will update the created, but the modified remains the same. This causes some users to experience unexpected results with the filter and an option to decide to absolutely use last modified would be very useful to avert these problems
-
Victor commented
During the migration, some users would like more flexibility on managing the content types that gets copied.
It would be great to have an option to exclude or even map content types for full site copy.
-
Victor commented
For import jobs, since that value exists in a File Share, some users would like to import only more recently used files by using the Last Accessed date for their migration
-
Jimmy (Sharegate) commented
It would be a great way to avoid bringing over unnecessary structure to the destination environment and have to clean it up afterwards.
-
Can ShareGate Migration skip over certain source files based on file name, like “has product in title – skip”.
-
Anonymous commented
Ive been working with the teampltes in Sharegate, and was hoping that Id be able to exclude files that have no size, but unfortunately filesize doesn't appear to be one of the filters that can be applied.
It would be very useful to have the ability to limit by filesize in the same way date is used, with an optional upper and lower limit. This way you could easily and flexibly limit files of certain sizes from a migration.
Just an idea :)
-
Stephanie Pelland commented
Prevent Sharegate from import too large files in SharePOint when importing from File Shares
-
Anonymous commented
I'd like to be able to apply multiple filters. This would super handy for cleaning up content as it comes across from a file share.
For example, I want to exclude the any files matching the following exact filenames:
Thumbs.db
.DS_Store...as well as any temporary files that match the following wildcards (where the asterisk "*" is the wildcard):
~$*.*
*.tmpBeing able to apply all of these filename filters would be amazing. Thanks! :)
-
Victor commented
Add more filtering options in Sharegate to get specific Content Types or custom values to the "Export Selection to Excel" option.
-
Caroline Vongkoth commented
Exclude folder by name using the custom template in Copy SharePoint Content
-
mats.warnolf commented
I would like Last Write Time to be included in the inventory. It is a good indicator of stale data. Also if there was a way to filter data when using the powershell cmdlet Import-document. an Exclusion Settings object perhaps where you could specify not to import certain extensions, stale data, etc