Do you have any update on this feature?

On march 2021 I've contacted the sharegate support for deleting files after successful copying (from fileshare to SharePoint Online):

"We have not implemented any CMDlet for the PowerShell ShareGate Desktop module that would allow for deletion of content at the source. This is not a functionality that we wish to have within our purview as there are cases where this could negatively affect users.
"

This feature is solely needed. I need to Move items so that users don't keep accessing older copies by mistake.

Need the ability to archive -- MOVE -- old folders/files from one library to a non-sync library within the same site collection. Don't want to create duplicates.

With IE going away, we're making heavy use of OneDrive sync, but running into problems with oversized libraries and need to archive old folders/files to a non-sync library. Need ability to move, not copy.

Get all Items form a SharePoint list

I was really under the impression that Sharegate could move documents from one SP library to another. Not copy but move.

I have activated Document ID on all my sites so if I move documents with the ‘move’ function in SharePoint any shared links to a specific document will keep working (and my users often mail each other links to specific documents). I wanted to use Sharegate for bulk migrations and the extra mapping options, but if I can’t actually ‘move’ documents and only ‘copy’…

This extremely reduces the usefulness of Sharegate for me.

Please invest in this feature!

+1. Why no news regarding the "Move" option ? I see a lot of new functionalities regarding Teams migration but nothing about a basic function like a MOVE. Is Sharegate taking into account user voices ?

I'd like to have an option to move files from one folder to another in SharePoint On premises versions in order to migrate later. I did it copy first and delete later but it will be better if it has the option already. I was thinking not always we are migrating stuff but we always are moving around so will be greate if you tool has the option that sharepoint older verions on prem doesn´t.
Feedback sent from the Copy view.

I have to chime in and agree. I know it would be theoretically possible to use the results file following a successful copy and then write a PowerShell script to locate the files on the source site and delete them to tidy up afterwards, but this is still a complication which shouldn't be necessary. (Not to mention that Copy and Delete is not the same function as Move.)

A move option would be very useful.

Any update on this? This would be pretty critical to our deployment.

Is anyone reviewing this request? It's insane that I can't move files with this expensive utility. We need to move a huge amount of files within our SharePoint tenant, and we can't use the built-in SharePoint Move feature due to the sizes involved (even at the individual folder level).

Since ShareGate obviously can't help me without just copying and then deleting huge amounts of data in SharePoint, does anyone else have a solution I should evaluate?

This is very disappointing, ShareGate.

I think it would come in handy to have the ability to either remove a source after copying has completed or at least hide it from browser.
Plus the copying process should set the source item/list/library to read-only temporary to block user from making modification. Some libraries could be large and take time to copy.

Thanks

I am looking for the option to move the data, not copy it.

WHy does sharegate falsely advertise it can move files when it clearly can only copy them.

This would indeed be a very useful feature, especially on bulk- and scheduled tasks.

Adding a move function is very important, as when you copy then delete, the link is broken, however if you move the file the link stays correct

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!!!!