SharePoint
Feedback by UserVoice

SharePoint Hybrid And Migration

Welcome! This is your place to suggest ideas or vote for ideas for improving the SharePoint Hybrid or Migration experiences.

How to submit a new idea

  1. Check if it's already been suggested. If it has, vote for it.
  2. If it's new, submit it in 50 words or less.
  3. Gather support!
  4. If your idea receives over 100 votes in 90 days, we will respond.
    If not, we will close it.

Want to engage further? Please visit the SharePoint Community

Note: we have partnered with UserVoice, a third-party service and your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Migrate Workflow Definitions

    The SharePoint Migration tool should being over Workflow Definitions from SP2010 and SP2013 workflows. While we understand inflight workflows can not be migrated customer with workflows should see the definitions migrated to SharePoint Online.

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Please make the output of Start-SPMTMigration an object

    The output of Start-SPMTMigration is in sentence form, and while you can capture it, you still have to parse it, which is exactly what you're NOT supposed to have to do in PowerShell.

    Instead the Output of Start-SPMTMigration should be something like this
    GUID Status Reason


    c3cc7804-7164-4a2b-8996-7e51f319dea9 Passed
    efd127ce-68f4-4d85-960d-5384ba561bef Failed The Target Site <URL> does not exist

    I mean, you still have to parse the Reason, if you want, but at least you have fewer hoops to jump through just to remove tasks that are destined to fail from your migration.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Include timebased information like CreationDate,ModifiedDate and LastAccessedDate in the scan reports

    Include timebased information like CreationDate,ModifiedDate and LastAccessedDate in the scan reports to gain insights on data in fileshares or SharePoint that might require archiving or disposition opposed to migration. By including this in the reports, these can be used for further processing.

    11 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow migration of Library structure but not take content. Popular request from customers

    Third party tools such as ShareGate and Metalogix allows the customer to migrate libraries with an option (setting) to leave behind the content. This is very common request from our customers needing to cleanup sites/content before migration but allows the migration of site structure. I have been asked if this is possible many time and I can only recomment using a 3rd party tool. This would be a great addition to our migration tool.

    24 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  5. When doing an Incremental Migration do not overwrite list/library settings

    I noticed that when doing an incremental migration with the SPMT tool that the tool will bring over the setting from the source and overwrite the Destination. Example after migration I enable versioning in SPO but versioning if off in SP2013. When I do a incremental migration versioning will be disabled on the SPO library. It might be useful for people to pick if they want to migrate all setting or leave the destination setting like versioning.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Regarding file migration from on-premise file server to SharePoint Online

    *English follows Japanese

    ■Title(件名):
    オンプレミスのファイルサーバーから、SharePoint Online へ移行について
    Regarding file migration from on-premise file server to SharePoint Online


    ■Description(内容):
    オンプレミスのファイルサーバーから、SharePoint Online へ ファイルをドラッグ アンド ドロップ、もしくは、サイト上のアップロードボタンで移行した際に、ファイルに破損などなく移行できたか確認できる機能の追加を希望します。
    When I migrate files by uploading or drag and drop from on-premise file server onto SharePoint Online, I want to check if the file has been moved successfully without any damages, so please implement such a feature.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Limit scope of what the tool does when only migrating lists

    Currently the SPMT tool does a lot more than it should when migrating only lists or libraries. For example - it changes the site title, activates features (web & site scoped) that are completely unrelated to list data that's being migrated.

    It's rather frustrating when having spent considerable time setting up a site where features need to be deactivated and other settings reverted. The incremental process does the same too. The tool also resets and removes views, as well as surprisingly deletion of indexes that were put in place to assist with filtering in views.

    Thanks,

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  8. SharePoint Migration Tool should support migrating to O365 Team Sites

    Currently it gives an "Access denied" error, but it doesn't really make any sense why O365 Team Sites would not be supported as a destination. There are many scenarios where this is commonly needed for some customers who have Sharepoint sites setup as O365 Team Sites and not as an SPO Site Collection. Just in general as well this would be a handy option to have.

    Please consider this as a future improvement to the SPMT. Thanks

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  9. SPMT should have a silent, scriptable installation process

    The SharePoint Migration Tool should have a well documented, silent and scriptable installation process. The GUI portions of this product have interest to me, and yet, I'm stuck with 3 or four clicks to get it installed just so I can automate data migrations.

    Maybe a Nuget Package? Chocolatey?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow a user using the SPMT tool to select what site template to use when creating a new site.

    Currently when SPMT creates a new site it only does a Modern site no groups. It would be beneficial to have the tool give an option of what site you would like to create. Example sometimes I might want a communication site. In order to do this today I have to first create the site in SPO then use the SPMT tool to set that as my destination. It might be good to have a few choices to pick from or let the user build a site template mapping file.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  11. list data

    SharePoint Migration Tool Migration Support for Lists Import from CSV or Excel

    It would be great to have support for loading list data from files - especially large lists!

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Increase the file upload limit

    Currently uploading files to onedrive is limited to 15GB.
    With an increasing file size, especially with 4k content, the 15GB limit causes some inconveniences
    Please
    Increase limit of the uploaded file to 50GB or the highest possible level

    3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  13. Convert folders to metadata of file while migrating to SharePoint

    Provide the ability to analyse folders and sub folders around files and give the feature to convert that information to file metadata before completing the migration. Ultimately removing folders from showing in the SharePoint Library.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add the ability to schedule a migration to the SharePoint Migration Tool

    Pretty much as per the title - add the functionality to create a migration job, and have it start at a particular time of day, pause when required, and then continue. The SPMT can use a lot of resource on the device it's installed on, and consumes bandwidth, so have it start after working hours, pause for the next day, and then continue, all automatically, would be very useful.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support including Chrome Type in web parts migration in pages.

    Migrated Web parts from SP13 to SPOnline don't include the chrome type attribute as it is and set to "Default".
    So, if I have a web part that its Chrome type is set to "None", it's set online as "Default" instead.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  16. Share point subfolder migration

    Hello i talk about one month with the premier support share point about an issue with migration tool in share point online , when you begin a new job and give the url subsite have only the first folder (and this after the update of migration tool )this, befor cannot do that. MEans that when you have big files under 50GB cannot split the big files to the smaller job . Need to do manually in other folder inside the site and move to the destination.Loose to many hours to migrate the files , and if you have incremental jobs…

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support in SPMT SP 2019 <=> SPO migrations

    Would be nice to have the ability to move sites and content between SharePoint 2019 and SharePoint online with SPMT tool in both directions

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  18. SharePoint Migration Tool: Excluding paths

    A useful addition to the SharePoint Migration Tool would be to support the option for excluding paths in a file share to SharePoint migration scenario. It would be very useful to put an exclude symbol "-" in front of a mapping while building the .csv. In this way you are able to migrate the only what you really need. Example: a library with 50 folders and you need 48 of them. In the current version you migratie everything and in a post migration step you need to manually find and delete these 2 folders. Or I need to add 48…

    9 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  19. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →
  20. migrate SharePoint 2016 to O365

    We have a few SharePoint 2016 sites that we would like to have migrated to Office365 but I'm not able to find an easy way to do this. I tried to save list as template to get some of the content there but the data didn't import correctly. There needs to be a way to migrate SharePoint 2016 to O365 fully.

    43 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Migration  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for providing feedback. We do have in the plans to bring support for SharePoint 2016 as a source in the SharePoint Migration tool. While we can’t commit to a timeline right now we are working on enabling the SharePoint 2010 first then move on to 2016 based on current feedback.

← Previous 1 3
  • Don't see your idea?

SharePoint Hybrid And Migration

Categories

Feedback and Knowledge Base