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.
We are planning to migrate our users homedrive (personal network share) to OneDrive. Some users have created folders/files wich we want to exclude from the migration. We have 10.000+ homedrives. It would be great if we could use a rule or filter for this.
Matthias Habegger commented
"Import-Document - Exclude Subfolders" is really a required feature.
Let's say we have an network drive G:\ where our departments have their files
- Department A
- - Team A1
- - Team A2
- - Lots of other department A stuff
- Department B
- - Team B1
- - Team B2
- - Lots of other department B stuff
Now we want to move that content to MS Teams but have the following Teams
- Department A
- Team A1
- Team A2
- Department B
- Team B1
- Team B2
How should we be able to migrate all that content over night without the possibibility of exclude folders?
Kevit Patel commented
Hello is there a way to add a feature to exclude content types and term store groups, sets and terms during site migrations? We are migrating content from SharePoint On-Premise to SharePoint Online and ShareGate is migrating unwanted content types and term store data to our new SharePoint Online environment.
Giacomo Pozzoni commented
It would be nice if powershell command Import-Document supported excluding folders with wildcards, it feels like just 1 parameter to add and some regex checks in the path.
You really need to give the ability to exclude folders from source for fileserver migrations, via powershell or the GUI. This is especially important when doing a fileserver migration containing redirected user profiles to onedrive. There could be 1000s of profiles, and each one will have a series of folders that you may decide you dont want to migrate e.g. a downloads folder. However the ShareGate tool cannot exclude this. For fileserver ->OneDrive migrations this should be a basic feature.
I need an urgent help. I am trying to do some delta migration via script. I want to migrate any files modified after a certain date.
In my script the date filter is not working correctly and is migrating some extra files and folders too.
I think the string to date conversion is not correct.(Edited by admin)
at least we should able to apply date range for data to be migrated with copy structure & contents as well, that will give more control to ingore data to be migrated which does not needed to retain while migrating to new sites.
We would like file and folder filter options. Essentially ROBOCOPY /XF /XD options. If we can't exclude - then we really have to fall back to other options (robocopy, copy, powershell), which moots the value of the migration utility.
Acep Karmana commented
Copy Structure with Filtered Contents will be a huge improvement. Am I miss it, is there already workaround for this? powershell script fine too.
Murali Rama Krishnan commented
Is it possible to update the content editor webpart's content during migration. user's seems hardcoded styles to disable the SharePoint default header, side navigation, and footor contnent lots of pages.
When we migrate the content remains same, but the user expected behaviour is lost as the new version does not hold the same css class names for header, side navigation, and footer.
Any suggestions or recommended approch for this kind migration.
Appreciate your advice on this.
It's nice that you feel like your migration experience is quite good right now, but many people have asked for this feature. I understand it's a big change to add it to the UI, so how about adding it to PowerShell? I've tried migrating a specified set of lists as a substitute for excluding lists, but we have a lot of lookup columns, and this rapidly becomes too complex to be workable.
My client is migrating everyone's homedrive from the SAN to OneDrive. Of course each person's homedrive is different, but there are some common top level folders that were created for users that the client does not want copied to OneDrive. Such as WINDOWS or DESKTOP. What we would like to be able to do is feed in a list of foldernames to be excluded from being copied. Similar to the existing functionality to feed a list of file extensions to be excluded.
File Size should be able to be limited when copying content.
We want to do all sites/subsites migrated without one library in each site. And I don’t find any option for migration excluding a library/list. Can such migration through Sharegate tool is possible?
Douglas Punchak commented
I'd also like to add further filtering options. I have a requirement now to not upload any file > 1 GB.
Asif Khawaja commented
This is extremely required. Especially the ability to filter libraries or lists that are empty.
Dany Lavertu commented
Add the time range and extension filter to structure migrations as well (only available for content migrations for now)
When running a Copy Site Structure task, please stop trying to migrate the MicroFeed. It is know that it cannot be migrated, so, simply skip it.
Feedback sent from the Migration Report view.
For customers running a ShareGate job on a regular, scheduled basis, the time range filter is a nuisance. You need to keep changing the time range for every job. It would be a big improvement if we could filter by "present date minus 3 years or more" to migrate documents that are 3 years old or older, for example. That way, we could continually send old documents to an archive location, without admin interaction.
It would be good to have an -exclude option for Copy-Content.
With SharePoint migrations, in some instances the target environment has some pages already created, and should not be overwritten from the source environment (they are pre-configured).
In the above example, you could have a page library (20 items), but you only ever want to migrate 19 of them.