The last response to this from ShareGate was in 2019. Is this now being considered in a future update?

When doing a file share migration, or any migration for that matter, it would be good to just retry the items that errored out.
For example, I did a move of hundreds of thousands of files and had ~250 errors. The errors were simply because of an upload issue on the Microsoft side. Instead of doing a full incremental of ALL files again, it would be good to be able to just isolate and retry the files that errored out.

+ would be nice to have this also for "download content" feature

Would LOVE for this to be a feature - I am wanting to re-migrate about 1000 failed versions, and without an option like this i have to the whole migration of 6000 items (including versions) again - preferably waiting for After Hours, but if it was just remigrating the failed versions, i could just run the failed 1000 now with less load / throttling / impacts etc etc.

During a migration happens that some items can not be copied completely bacause of e.g. wrong mapping, missing values etc. Often the error occurs on older item versions. In the protocoll we can filter on those errors.
After fixing the problem we want to try to copy the items with an error again. Not within thausend of files and folders, it is a challenging job collect get all that stuff. Once found the item, we must copy them one by one because they are stored in different folders.

It would be realy helpful if we could restart the copy just for the error items from the protocol list directly. Maybe with the same screen as for Import and copy dialog where we can change also the mapping.

Feedback sent from the Migration report view.

Having to rerun an entire migration job for a few failed files, lists, etc seems to be a huge waste of time and resources. I don't understand how this "doesn't fit in the current narrative". The whole purpose of the software is to making migration easier. Not having this feature, and requiring users to re-run the whole job for a few files and therefore tying up the software (because running current jobs can result in throttling) seems counter-productive.

How is it possible that after 5 years (!!), there is still no solution to this problem?!

"doesn't fit in the current narrative of ShareGate Desktop"...how is this possible? is the narrative supposed to be that there are never errors, and if so, we ignore them? Adding a button for "Retry errors" would be a huge feature add, vs having to run the entire migration again, wasting a ton of time.

Hi,
if I migrate complete sites to another site then I mostly have some lists which could not be migrated on the first run. If I start the migration again then migration is successfull.
My problem is that I always have to copy the complete site again with copy and replace and that tooks time.
It would be better if I would be able to select automatically the unsuccessfull lists and then try only to copy the lists that throws an error on first run.
Is there an option that Sharegate automatically choose the unsucessfull lists (error) from the migration report and only start a new try for that lists and not for the whole site?
Kind regards

Martin
Feedback sent from the Migration report view.

As someone new to ShareGate migration, this feature would certainly make my job easier.

If you see the error log and files that error out are from selected folders.

As a workaround you can run incremental migration for only these folders, Better than running full migration

Boooo - c'mon 'Toine this would be LEGENDARY.

How can this not be a priority feature...?

1 Please make logs searchable like if I type Steve_Davis I would be able to see the log for Steve_Davis.

Pleae give a cmdlet or a button to retry errors. It is great that you can narrow down a failed attempt, maybe it was a network blip or something that would be corrected if that file was auto retried at the end of the run or a remediation run is auto-kicked off. It would be hugely helpful.
Feedback sent from the Tasks view.

The ability to migrate content base on previous migration log. For example migrate only the items with an error message.

When I am doing a migration, it would be nice to click on the "failed" and have them "tried again" as I have versions major and minor and didn't have MINOR turned on. I just turned it on and I would like to try it again if the system could keep track of what "failed" and allow me to try again.

Really need this to reduce the administration on migration!

The failed items only need to be copied. E. G my list has not copied look up columns, then only copying data in lookup columns need to be allowed

....waiting now about 4 yrs on this... c'mon Sharegate..... I believe in you

It is frustrating to have to go back a screen or two to retry a move when there are only a few "warning" or "errors" that resulted from the move. It would be great if from the results screen , if there was a option to right click a line item that had an issue and click retry.
You would do this after making the appropriate changes to correct the issue of course. But having to go back and trendge through processing all of the other items (even though you click incremental). It still takes time to compare the last changed dates, which means more time waiting.
Where as if you could just kick it off right from the result page, it would make things a lot faster.
Feedback sent from the Migration report view.