Quickly compare source and destination content in order to see what needs to be incrementally migrated and to prove to customers that every item from the source made it to destination.
To be compared:
-lists and libraries239 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.
For example, if a file has been deleted in the source after it had gotten copied over to SharePoint, can it be deleted in SharePoint?
The goal is to re-sync only the updates, additions and deletions without the need to copy the whole thing again. It allows to keep on using the source environment while keeping the destination one sync until we're ready to go live with the new site.
-documents (move them to a different location if the user has moved it since the last update)
As much as we hear your need, this is not currently on our road map. We will revisit it eventually.
[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.
Having to remember to keep the selection, verify the copy & then delete stuff when you're moving thousands of files around is really hard & painful when you make a mistake. It would be great if you guys had a move option that took care of all of that123 votesThinking About it · AdminJean-Philippe Beaulieu (Voice of the User / User researcher, ShareGate) responded
I am glad to say that we are currently exploring the possibility to add an option to automatically make Read-only and/or Delete the source of migration if it goes errorless.
We’ll keep you updated with any news on this.
The idea is to use the migration report to start a new migration of the files that error out only, instead of running a full incremental migration.118 votes
As much as we really like this idea, it doesn’t fit in the current narrative of ShareGate Desktop.
We will for sure reevaluate this one in a near future.
Preserve List Items ID's64 votesNot For Now · AdminJean-Philippe Beaulieu (Voice of the User / User researcher, ShareGate) responded
Lately we decided to shift most of our energy towards migrating, managing and adopting Office 365. When we create new features, we make sure they also work with SharePoint on-premise (if possible), but we are not planning on developing more options of features specifically for on-premise at the moment.
I’ll keep the suggestion open and our ears are still open to new comments.
During a migration, have the ability to convert Site Pages and their classic Web Parts to their Modern version (when it exists).
61 votesNot For Now · AdminJean-Philippe Beaulieu (Voice of the User / User researcher, ShareGate) responded
- If a Classic Web Part does not exist as Modern, it should not be converted.
- Custom Web Parts should be ignored.
After a review of our roadmap, this suggestion is not a high priority at the moment.
With all the improvements that were done to the SharePoint PnP Modernization framework (https://docs.microsoft.com/en-us/sharepoint/dev/transform/modernize-userinterface-site-pages) over the last year, we feel like this is a solid alternative right now to convert classic pages to modern ones so we decided to put our efforts in adding more migration capabilities (Teams migration coming soon) to our tool instead.
We’ll keep the suggestion open and will monitor the comments and feedback and will review it in the future.
To have the ability to migration video files when Microsoft Stream replaces Office 365 Video Portal60 votes
We understand the need for this and are evaluating the possibility of doing it.
Can we move list with PowerApps Customized form to another site using ShareGate? Currently it is not possible in PowerApps to tag along its customized form once its list is moved.55 votes
Support the migration of Google Team Drives53 votes
Be able to create a Migration Queue where a migration job will start only when the previous one is completed.
Example: SG Job 1 Starts > SG Job 1 Completes > SG Job 2 Starts > SG Job 2 Completes > SG Job 3 Starts > SG Job 3 Completes > and so on.
Can we schedule migrations that start when another finishes (dependent)? Not with PowerShell, but with the current UI.48 votes
User would like to have support to copy Microsoft Planner from one tenant to another.47 votesBuilding it · AdminJean-Philippe Beaulieu (Voice of the User / User researcher, ShareGate) responded
You’ll be please to hear that we started working on adding the ability to copy Planner. In the first iteration, whenever you copy a Team the connected Planner will also be copied which means we won’t be able to copy Planners by themselves.
We are currently aiming at releasing this somewhere in June.
Have a nice day!
Users wish to lock their sites during the migration to avoid having to deal with any user changes, during, or post migration.
Having a feature that would extract all the source site permissions (I'm thinking PMR), strip it and leave it read-only for everyone, and then allow to use the extracted permissions to re-apply them at the destination (or source if they wish to), could be very useful for a good number of users.40 votes
Create a PowerShell Sharegate command to create Site Collections at destination from source.40 votes
Ability to create a standard document library or folder through PowerShell36 votes
Ability to configure migrations options and mappings that can be persisted and applied to multiple migrations (or as default values)
- Copy options for all migrations (ex: not preserve permissions, silent mode, merge)
- Templates30 votes
- Ability to import a list of source-destination pairs (ex: CSV file)
- Ability to set up a batch of multiple migrations from the UI
- Connect multiple sources to a single destination (or vice-versa)
Without going to PowerShell30 votes
Some users would need to be able to generate the Excel Spreadsheet for their metadata using PowerShell. When automating a complex migration, having an export for all the lists with a foreach loop would be a powerful way to take full control of the data during the migration project.29 votes
allow migration of external users and preserve the external sharing invites29 votesLP Lavoie responded
We collected information and are evaluating this further
Migrate Flow integrations attached to lists and libraries
See if we could potentially convert old email enabled lists to the equivalent Flow integration26 votes
- Don't see your idea?