Add a ''Move'' and Delete Option
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 that
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.
Why does Sharegate not have move option
Feedback sent from the Migration report view.
This was requested in 2016 and its still not available in 2020?
Why does this still not exist? It has to be one of the most obvious features to benefit people, and yet we're treating it like it's not solvable. If there is an error on the file level, then don't 'move' the file... very difficult. What if it's in a folder? Work from the inside out. If a child can't be moved, then it's parent folder can't be moved! Brilliant!
Please stop stalling on this feature!!!!
Move and Delete very useful when working inside SP environment, for instance we have O365 retention on over SP sites which prevents me from moving folders with subcontents using SP move function, at this point I'm using SG-Desktop then have to recursive delete the files using PS
This would be extremely useful when doing large migrations from file shares to SharePoint (Online). Alternatively we have duplicate files which is what we want to avoid.
I think a "move" option should be standard functionality. Of course if the copy fails for any reason the source file should not be removed.
As an addition I would like to see:
1. The ability to manipulate source files after they are uploaded - i.e move to a different folder, change security permissions on the folder/files
2. Same as 1 but to change SharePoint permissions on source libraries
3. An easier folder/file mapping process whereby a spreadsheet can be used to map all folders from their source to their destination folders. This is required as with all the migrations I have done so far there is a level of re-organisation by the customers and to streamline this process for both customer and engineer would be ideal.
When migrating files from a fileshare into SharePoint, it would be great if Sharegate had an option to delete the files from the fileshare if they were successfully migrated. Therfore an option to do a "move into sharepoint" rather than the current copy.
Fantastic product otherwise, really like the recent updates
Agreed! Moving files it difficult but insane making when they are thousands to relocate to new folders or doc sets.
Once the files are in the destination library it would be great to be able to move within the library with Sharegate. Copying means taking extra precautions within the library itself as now there are 2 files. Creating a view to help remove the original file location is an option but another step. Moving with a confirmation would be awesome. Would make Sharegate more valuable post migration.
Donal Clissmann commented
Moving files and folders between document libraries is one of the most tedious tasks to perform in the native SharePoint interface. This is one of the most common pain points that our customers raise with us.
ShareGate should capitalise on this and offer this feature which would provide real benefit to our customers and provide another USP for ShareGate.
Be able to move documents between libraries and sites. Instead of just copy them.
Currently a two step process. Bulk copy with Sharegate and then manual deletion in source. So needs a copy a confirmation step and then a deletion.
Some users wish to move files instead of just copying them. So the source would be removed and the file placed in the destination. This would be useful for certain types of archival.
Fred Larssen commented
When running scripts to import documents periodically, it would be useful to have an option to move documents rather than copy them.
This would prevent reprocessing of already imported documents, and allow the use of the Rename action instead of IncrementalUpdate. IncrementalUpdate creates problems if a document added to source folders have the same name as a previously imported document.
If Sharegate is meant to have read access only to file shares, another option would be to include a list of successfully imported files in the Result object, so that they can be deleted by the script.
Right now we have the option to copy files from ShareDrive while importing to SharePoint. We have to create powershell script to delete them from original location. It needs some work as we are importing based on filter (last Modified date).
If there is an option to move the file it would be helpful. Hope to see in future version.
Move option for list and library, so put on new location and remover from old location
I have used SG numerous times with the traditional of copy the content but it leaves the source content still there so I would have to delete it later. Would be nice to have an option to move the content instead of copying it.