Douglas Punchak
My feedback
-
36 votesDouglas Punchak
supported this idea
·
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment Douglas Punchak
commented
Clients always want to archive old content. As part of those migrations, they want to "...migrate all content (sites, lists, libraries, etc. in their current form), older than 1/1/XXXX to a separate archive site collection.
Then migrate current content (1/1/XXXX) and newer to their active collection(s). With large migrations, this is a horribly tedious effort to use PowerShell to do List\Library level migrations.
It would be great if we could use the "Copy Structure" and use a date filter that would use a "Copy Content Newer Than" and "Copy Content Older Than" filter. It would then only migrate all list items, libraries, etc. that meet this criteria
Douglas Punchak
supported this idea
·
-
228 votes
This is not currently in our plan to allow our users to compare two environments.
We might do it in the future, possibly starting with permission as it seems like it would be the most useful part on security level.
An error occurred while saving the comment Douglas Punchak
commented
For me personally, security would be the least helpful. I'd be more interested in comparing content. Then it would be good to run an incremental on those results because you already know what the differences are.
An error occurred while saving the comment Douglas Punchak
commented
I personally think comparing content would be the most useful. Then being able to run a delta migration job against the result since you already have the differences.
Douglas Punchak
supported this idea
·
An error occurred while saving the comment Douglas Punchak
commented
The ability to do a delta migration is a must have for our clients 90% of the time. We've had to overlook ShareGate on a few occasions and go with another product because of this. Our clients want us to migrate everything first, they want to review it and test it out, then just prior to their go-live date, they want a delta migration.
-
133 votes
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.
Douglas Punchak
supported this idea
·
An error occurred while saving the comment Douglas Punchak
commented
I'd also like to add further filtering options. I have a requirement now to not upload any file > 1 GB.
1. If PowerShell had a switch\property for "-CreateDestinationFolder" when doing a "Copy-To" migration, to create the destination folder path if it doesn't exist would be fantastic. I find myself having to create the folders manually first then using the PowerShell commands.
2. Alternately, if there was a "Create-Folder" command-let within ShareGate instead of needing to incorporate the SharePoint Online Management Shell that would be good too.