Feedback by UserVoice

I suggest you ...

Support SharePoint Online to SharePoint Online Migrations in the SharePoint Migration Tool

A very useful addition to the SharePoint Migration Tool from Microsoft would be support for SharePoint Online to SharePoint Online migrations. There are many scenarios where this is commonly needed for some customers who must restructure or realign and be able to migrate from one area of SharePoint Online to another. Just in general as well this would be a handy option to have.

Could this please be considered as a future improvement to the SharePoint Migration Tool including support with bulk migrations for SharePoint Online as a source. Thanks.

148 votes
Sign in
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

Cian Allner shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
SharePoint Hybrid and Migration Team responded  · 

Thank you for bringing this suggestion to our attention. While the SharePoint migration investments have been focused on helping the on-prem customer transition to OneDrive and SharePoint in Office 365 using the SharePoint migration tool, we acknowledge that there are additional scenarios like the ones explained in this suggestion that are not covered yet. We are currently considering various options to solve those scenarios, but we cannot commit to anything at this point. Please continue bringing great suggestions to our attention like this one.


Sign in
Password icon
Signed in as (Sign out)
  • Beth Hall commented  ·   ·  Flag as inappropriate

    As a general practice, IT pros have spent years and much sweat and heartache controlling change within our production environments. We often have strict change management practices and security to ensure nothing negative happens to our important business systems during the work-day. We enforce maintenance windows with our staff and our organizations. This is a core requirement for all systems that the business relies on. And it was not an easy road for us to get here.

    SharePoint has become one of our most important business tools. YES, it needs to be flexible, and we must be able to fluidly add new sites, libraries, etc. on the fly, but we also need some constraints to reduce the risk to our data.

    What we can't do is Test, Validate and Iterate new approaches and features in our Production Tenants. So we create Lab/Dev tenants to do that in. And we put up with having to manage the administration of 2 ecosystems, because we know the value is high. Having a place to try stuff, and import data, and mess with list columns and figure it all out using SharePoint emerging features makes it worth it.

    It is clear that MS is working in a very agile approach to deliver features to SharePoint. You're obtaining customer input from us, and then iterating the product to general release and beyond. This is great. The evolution of the product is awesome, and now that we have insight into what is coming--well that part seems to be working well.

    Unfortunately, without some sort of tool to help us move config and data around from tenant-to-tenant in the SharePoint cloud, your customers aren't able to work in an Agile way ourselves. Even when we have defined a solution in our Lab--to make it happen in Production, we often have no choice but to dive elbows deep into live data lists and libraries and make the changes manually--and hope we didn't overlook something or mess-up the data. This is just not good.

    I'm sure this is not an easy problem to solve, but it is a critical one that inhibits those of us that are pushing for new features to be adopted, and for the tech to solve more of our business problems. There is just so much hand-work involved--too much! In these days of AI and automation and all that, we’re living in the stone age without this ability.

    Frankly, It is difficult to understand why we don't have a truly basic need like this fulfilled when there has clearly been years of development time spent on features like Spaces. I'm sure these things aren't correlate-able within the way that MS makes decisions and prioritizes future-looking functionality vs. administrative tools. but from the outside it stinks that there hasn't been move progress with this while less practical things move forward.

    Rather than diving into a full move tool, how about we start small and step into it. Give us some way to produce a packaging report on an Item (list/library/calendar) that shows its columns and their configuration. We could all benefit so much from just this! This would be a great step in the right direction towards the ability to packaging an item with or without its data and import it somewhere else. Seriously, the ability to pull a report on an item’s configuration would be HUGE!

    I propose that this is not a Migration issue, but rather a general administration issue. Where the Item is coming from or going to should be irrelevant. The ability to identify an item, package it, and import it wherever we want is what is critical. Whether that is within the same site, another site in the tenant, or another tenant.

    Starting with an Item rather than a Site would have more immediate application in our day-to-day world.

    Today it is so difficult to share solutions in the community because we have to manually write out all configuration option settings—it can take hours to do a decent job. Imagine a world where we (citizen developers) can create a solution that we know others could benefit from, and so we package it up and post it on the Tech Community to help other folks with the same issue. Talk about a powerful community!

    Maybe I’m preaching to the choir and you guys already know all this—but it is such a huge issue that I had to get my soap-box out and vent a little.

    I hope my perspective helps.

  • SDADM commented  ·   ·  Flag as inappropriate

    Even within the same tenant would be helpful. We had several units set up as their own site collections. If we could mode these to subsites under other site collections, to get to a flat architecture without having to recreate everything, that would be amazing.

  • UX Consultant commented  ·   ·  Flag as inappropriate

    So Microsoft...

    How would YOU move from one tenant to another... or from dev/test/UAT to Production? Come on guys, waky waky time.

    This is very important and pedestrian at best that we cannot perform these migrations without VERY expensive tools...

    Time to get it done :)

  • Maruxa Cabezudo commented  ·   ·  Flag as inappropriate

    There is no tool that we can use for SPO to SPO migrations, this feature will help us a lot in our Migrations. Please consider it!!

  • Raymundo Fugoso commented  ·   ·  Flag as inappropriate

    Yes, we really need the support of SharePoint Online to SharePoint Online migrations. We are doing the SharePoint Online product and we are selling to Customers. It's really a great help if we just migrate the SharePoint Online product to the new SharePoint Online that the Customer purchase/subscribe

  • Anonymous commented  ·   ·  Flag as inappropriate

    ??? So, the MIGRATION tool works FROM onPrem to O365. WHAT ABOUT FROM O365, to another O365? Why does the tool not let you PULL O365

  • Nikhil Sinha commented  ·   ·  Flag as inappropriate

    I like the sharepoint tool for migration but it supports only on premise to online could you include Online to Online Migration..

  • Thad Brown commented  ·   ·  Flag as inappropriate

    This would be great or adding a page/site collection move inside of SPO with powershell or a gui.

  • Lea Brooks commented  ·   ·  Flag as inappropriate

    Agree with the suggestions to support file metadata. Also would like to be able to migrate to specific folders within the library.

  • Adam Pope commented  ·   ·  Flag as inappropriate

    The inability to rename a site in Sharepoint Online has forced us to have a date-based naming convention. On the one hand it resolves the issue of not having to migrate sites when their names inevitably change; on the other it makes finding a site to save a file to an impossible task. The ability to easily migrate SPO -> SPO would resolve this issue and allow us to give our sites human-readable names.

← Previous 1

Feedback and Knowledge Base