Following on the announcements we made at our May 4th Future of SharePoint event, we’re happy to announce that we’ve begun the first phase of our rollout for copying and moving files between SharePoint and OneDrive.
Modern file management is built on top of modern document libraries, now fully rolled out to production. We know that many modern information workers begin content creation inside One Drive for Business, and then need to publish more finished content to a wider audience on a SharePoint team site.
Initially, you’ll be able to copy files from OneDrive for Business to destinations in SharePoint or OneDrive. Once you select a file inside OneDrive, you’ll see the Copy to option appear on the command bar. Copy to uses intelligence from the Microsoft Graph to display about your most frequently used sites, along with the option to browse to sites you’re following, as well as other locations within OneDrive.
File Copy destination panel
Modern Copy/Move works for both modern and classic experiences on target team site document libraries. You can copy single files, multiple files, or whole folders, preserving metadata.
Today, there are two notable restrictions. At this point, each copy operation between OneDrive and SharePoint is limited to a maximum size of 50MB. If a user tries to copy a larger amount of data to SharePoint, they will be reminded that large file copies can only use the current OneDrive as a target. Also, files can be copied from OneDrive to SharePoint, but not yet from team site to team site.
We have more plans to enhance the Copy/Move functions in the coming months:
Adding support for all file sizes, beyond today’s 50MB limit. (We know the vast majority of files in OneDrive are below this limit today.)
Copy files among SharePoint team sites.
Finally, we will also add the ability to move files, as well as copy files, among SharePoint Team sites as well as OneDrive sources.
Although this is an early version of these personal content management enhancements, we’re happy to start extending these capabilities to all information workers. Our rollout will start in August for First Release tenants, and will then proceed to full production over the coming weeks. Once this goes live, users will see “balloon help” inside OneDrive to alert them to the new capability.
Thanks, Chris McNulty. I have set individual libraries to get the MODERN document view. That is good. In this case, I'm trying to figure out why my tenant is getting reverted to the classic view. I'm a WHY kind of person. Unlike my users who don't care about the why, and just want it to work. I'll keep me ears and eyes open and wait for my tenant to get the MODERN view.
PBeiler1 can you try setting a single library to modern? How about the tenant level setting? Its already rolled out - so you likely have a setting somewhere that's reverting to classic.
Knut Relbe-Moe Currently the feature only works from OneDrive for Business to SharePoint but its definitely in the roadmap to enable SharePoint to OneDrive for Business and across SharePoint sites.
There is no connection between the copy and its parent/master file at this time but has come up before so it’s something I’m considering as a future improvement.
I still don't see the "Copy to.. Sharepoint" as an option. Is this feature rolled out as yet? I'm already in the fast track group (or whatever it is called)
Would it also be possible to copy files from SharePoint to OneDrive for business, or does this only work from OneDrive for business to SharePoint, also will it be stored in the metadeta, or would it be some trace of the fact that I copied the file from OneDrive to SharePoint?
Or can I use this to copy from one SharePoint Library to another SharePoint Library, that function is also really in demand.
Because what if someone updates the file in Onedrive for business, or in a "master-SharePoint-library" it would be great if that would be the "master-file" and i could just push out changes to all the places where this file have been copied to, like I could do with Content Types for instance.
Following on the announcements we made at our May 4th https://blogs.office.com/2016/05/04/the-future-of-sharepoint/ event, we’re happy to announce that we’ve begun the first phase of our rollout for copying and moving files between SharePoint and OneDrive.
Modern file management is built on top of https://blogs.office.com/2016/06/07/modern-document-libraries-in-sharepoint/, now fully rolled out to production. We know that many modern information workers begin content creation inside One Drive for Business, and then need to publish more finished content to a wider audience on a SharePoint team site.
Initially, you’ll be able to copy files from OneDrive for Business to destinations in SharePoint or OneDrive. Once you select a file inside OneDrive, you’ll see the Copy to option appear on the command bar. Copy to uses intelligence from the Microsoft Graph to display about your most frequently used sites, along with the option to browse to sites you’re following, as well as other locations within OneDrive.
File Copy destination panel
Modern Copy/Move works for both modern and classic experiences on target team site document libraries. You can copy single files, multiple files, or whole folders, preserving metadata.
Today, there are two notable restrictions. At this point, each copy operation between OneDrive and SharePoint is limited to a maximum size of 50MB. If a user tries to copy a larger amount of data to SharePoint, they will be reminded that large file copies can only use the current OneDrive as a target. Also, files can be copied from OneDrive to SharePoint, but not yet from team site to team site.
We have more plans to enhance the Copy/Move functions in the coming months:
Adding support for all file sizes, beyond today’s 50MB limit. (We know the vast majority of files in OneDrive are below this limit today.)
Copy files among SharePoint team sites.
Finally, we will also add the ability to move files, as well as copy files, among SharePoint Team sites as well as OneDrive sources.
Although this is an early version of these personal content management enhancements, we’re happy to start extending these capabilities to all information workers. Our rollout will start in August for First Release tenants, and will then proceed to full production over the coming weeks. Once this goes live, users will see “balloon help” inside OneDrive to alert them to the new capability.
More information
Please visit our support article “https://support.office.com/en-us/article/Copy-files-and-folders-from-OneDrive-for-Business-to-a-SharePoint-site-67a6323e-7fd4-4254-99a8-35613492a82f?ui=en-US&rs=en-US&ad=US” for more detailed technical information. And please share your feedback here on the Office 365 Network or on http://sharepoint.uservoice.com/. Thank you.
Following on the announcements we made at our May 4th https://blogs.office.com/2016/05/04/the-future-of-sharepoint/ event, we’re happy to announce that we’ve begun the first phase of our rollout for copying and moving files between SharePoint and OneDrive.
Modern file management is built on top of https://blogs.office.com/2016/06/07/modern-document-libraries-in-sharepoint/, now fully rolled out to production. We know that many modern information workers begin content creation inside One Drive for Business, and then need to publish more finished content to a wider audience on a SharePoint team site.
Initially, you’ll be able to copy files from OneDrive for Business to destinations in SharePoint or OneDrive. Once you select a file inside OneDrive, you’ll see the Copy to option appear on the command bar. Copy to uses intelligence from the Microsoft Graph to display about your most frequently used sites, along with the option to browse to sites you’re following, as well as other locations within OneDrive.
File Copy destination panel
Modern Copy/Move works for both modern and classic experiences on target team site document libraries. You can copy single files, multiple files, or whole folders, preserving metadata.
Today, there are two notable restrictions. At this point, each copy operation between OneDrive and SharePoint is limited to a maximum size of 50MB. If a user tries to copy a larger amount of data to SharePoint, they will be reminded that large file copies can only use the current OneDrive as a target. Also, files can be copied from OneDrive to SharePoint, but not yet from team site to team site.
We have more plans to enhance the Copy/Move functions in the coming months:
Adding support for all file sizes, beyond today’s 50MB limit. (We know the vast majority of files in OneDrive are below this limit today.)
Copy files among SharePoint team sites.
Finally, we will also add the ability to move files, as well as copy files, among SharePoint Team sites as well as OneDrive sources.
Although this is an early version of these personal content management enhancements, we’re happy to start extending these capabilities to all information workers. Our rollout will start in August for First Release tenants, and will then proceed to full production over the coming weeks. Once this goes live, users will see “balloon help” inside OneDrive to alert them to the new capability.
More information
Please visit our support article “https://support.office.com/en-us/article/Copy-files-and-folders-from-OneDrive-for-Business-to-a-SharePoint-site-67a6323e-7fd4-4254-99a8-35613492a82f?ui=en-US&rs=en-US&ad=US” for more detailed technical information. And please share your feedback here on the Office 365 Network or on http://sharepoint.uservoice.com/. Thank you.
Following your suggestion ... I created a new site, (not sub site), using the Enterprise\Document-Center template. I uploaded two files for an added visual of which view (classic/modern) I was in. The new site is in the CLASSIC view.
Let me clarify what we are talking about.
This is NOT what I'm referring to ... The SITES page on the waffle menu, got changed and renamed to SHAREPOINT. I'm good here.
This is NOT what I'm referring to ... The SITES CONTENTS view changed. I'm good here.
This IS what I'm referring to ... There is the MODERN document library that has the command bar instead of the ribbon. I do NOT have this. While I could go into each library and change the view for that library only, that is not practical.
I do understand updates are constantly occurring. My concern is that one day everyone in my tenant will see the MODERN document view and I will have had no notice it was coming, and because I don't see it now, I cannot prepare for this change. I have three of us in the tenant setup as FIRST RELEASE. None of us have the MODERN document view.
PBeiler1 it depends on how you customized the banner page, and if it involved jQuery or master poage changes that can trigger autofallback to classic mode for libraries. Id suggest creationg an unbranded site and see if we can trigger modern there. cc LincolnDeMaris
Brent Ellis right now the copying is within the scope of a single tenant, not cross tenant and not OneDrive (Consumer). Reece Gallagher Offioce 365 Groups are really Team SItes under the hood, and we've committed to turning all Groups into full Team Sites soon.