So what do we do? Well… We have a property called FileSystemObjectType that can be either File or Folder. Folders are also in scope if we don’t do something! Because we’ll use the Get-PnPListItem cmdlet to grab all the items, it’ll also grab the folders. If you have PowerShell v3 installed on the remote machine, configuring it for PowerShell Remoting is easy. Configure Remote machine for PowerShell Remoting. In this blog post, we are going to discuss the steps to do the same. If we look at the description of the Copy-PnPFile cmdlet ( or the Move-PnPFile for that matter), we can read: “ Copies a file or folder to a different location“. In such a case, you can also copy files from your local machine to remote machine or vice versa using PowerShell remoting. 👉🏻 For this example, we’ll copy them into a different site (SitePnP2), therefore a different library! We do not want to have a folder structure, so we’ll leave the folder(s) “behind”. So the goal here would be to copy or move those files into a new location. And we also have a files on its own (SPO Roadmap.pptx) at the same level as the Folder1. Inside this library, we have a folder called Folder1with files inside (nested files). We have SitePnP1 where we’ll use the default Documents library.

Let’s have a look first at our current (dummy) structure.

We’ll see how to copy or move files to another location, either on the same site but different library, or a completely different site 🙂 In today’s post, we’ll have a look at something that could potentially be your mini “re-organisation / migration” project.

Move file in powershell