*English follows Japanese

■Title(件名)：
SharePoint ワークフローを Power Automate に移行する機能の追加希望
Add a function to migrate SharePoint workflows to Power Automate

■Description(内容):
SharePoint 2010 および SharePoint 2013 ベースのワークフローを、そのまま簡単に Power Automate に移行する機能を追加してほしい

Please add a way to easily migrate workflows based in SharePoint 2010 or SharePoint 2013 into Power Automate.

Currently, there is no option to programmatically control migrations with the Migration Manager.

For large file share migrations we would like to implement a user interface that allows some controls by the end user.

An API or some sort of scripting possibilites would be great.

Actually the API is already there _api/MigrationCenterServices

Please make this endpoint publicly available.

Hello team,

is there any feature planned for setting maximum single file upload limit for migration to OneDrive or SharePoint.

With current update from OneDrive, it now allows 100GB of file upload, while our requirement is to not migrate files greater than 15GB.

Thanks and regards,
Rupali Kothawade

Locked or secured API for data encryption

I have been migrating a few 10's of Gbytes from on-premise file shares to cloud and find that the migration is so efficient, it saturates my network connection, causing problems for my users.

When I paused the task after 60 minutes to allow users to do their work, although the file system scanner paused, the package upload didn't, so the tool continued saturating my bandwidth for an additional 75 minutes.

It would be helpful if the migration tool had some throttling settings to avoid this situation, and if the pause could also affect the package uploader.

Are you looking for the best software that can fix all the errors related to the EDB file quickly so SysInspire EDB to PST Converter is the best solution? This software simply repairs the corrupt EDB file by scanning and removes all their errors immediately to make it usable for the user. It export Exchange database to PST and many other multiple formats like EMLX, MSG, EML, and HTML.

For More Info:- https://www.sysinspire.com/edb-to-pst-converter/

The SummaryReport CSV generated from a PowerShell SharePoint Migration Tool (SPMT, SPMTMigration), is not showing accurate information for one of the tasks at the end of a multi-task migration run; the task shows that it is still in progress, but the migration finished successfully.

Checking the task reports in the folder, everything is in order; the migration completed successfully; all files/folders have migrated to SharePoint online, and there are no issues, as well as no FailureReports in any of the report folders.

For more details, see my post on Q&A here: https://docs.microsoft.com/en-us/answers/questions/172930/inaccuracies-in-summaryreport-generated-from-spmtm.html

Thanks!

Would like to request to choose which files/folders/subsites to migrate over to prevent possible issues with 3rd party applications.

I am using SPMT ver 3.4.119.7. I receive the error code above with the message "Scan File Failure:The item's content type was not found in the initial scan" in the Failure summary report. I am copying a list with the single content type "Item". In the past, I have been able to copy items from the list using ShareGate.

Support for Sharepoint 2019 on premise would be nice.

We are migrating the files form local machine to sharepoint site using sharepoint migration tool and running the incremental migrations after completing the migration. Now we want our local machine and sharepoint site are in sync and if i delete/move file on my local machine same should be reflected in sharepoint site after running the incremental migration. Currently its not possible. is there anyway to fix it?

SPMT has been extend to SharePoint 2016, it will be be nice to also extend to SharePoint 2019.
I have already vote for the both direction idea, but the on premise to cloud direction should be easier implement.

The migration settings of SPMT must have an option to filter out files and folders having specific name or starting with certain string.

For example -

1. We want to filter out "$RECYCLE.BIN" folder while migrating home drives to OneDrive for Business.




2. Sometimes, the Office applications, such as Word, Excel etc, create temporary hidden files which start with the characters "~$", which we want to filter out in the SPMT migration settings.

Change the amount of simultaneous migrations currently this is set to 5 but it would be nice if we can set this our self. this doesn't have to be an infinite number but for example 1-20 so that if we got fast hardware/bandwidth we can migrate more and for slower older stuff lower it.

Ability to remove access to the old location or run custom scripts after each migration job. We currently have an issue where we migrate a user to OneDrive but the Recent Links still point to the old file path.

It would be great if we could have something that either blocks access to the user once the migration is done or the ability to run a script so we can automate process after a migration.

SPMT agents, specifically for local fileshare to OneDrive, is limited in that you define X agents, they are selected automatically. Adding a feature to either specify the agent pool to use, or limit it by domain. Use case: Multinational company doing migrations both in EMEA and Americas end up with agents in EMEA migrating AM users, which is essentially two ocean hops for the data.

we need a way to change the TMP stoag locetion from C to other

*English follows Japanese

■Title(件名)：
SharePoint 移行ツールについて
About the transfer speed of objects/list items in the SharePoint migration tool

■Description(内容):
SharePoint 移行ツールで移行する際に、オブジェクトとリストアイテムは、ファイルより移行速度が低くなります。
オブジェクトとリストアイテムも移行速度が速くなるように改善を希望します。

If carrying out a migration via the SharePoint migration tool, objects and list items are moved more slowly than files.
Please improve the speed at which objects and list items can be migrated.