← Al Davies, 250 High Street

How to move a file in SharePoint with Power Automate

Use the SharePoint action "Move file". Pick the file, type the destination site address, choose the destination folder, and set what to do if the name is taken. The original file leaves its old place.

What does the Move file action do?

Microsoft describes it this way: "Moves a file. Works in a similar way to the 'Move to' command in SharePoint libraries." The action also returns details about the file in its new place.

So the flow does what a person does when they pick a file and choose Move to. Here, the flow makes that move for you each time the trigger fires.

Which fields does the action have?

The connector page lists five fields, and all five are required.

  1. Current Site Address: the site that holds the file today.
  2. File to Move: the file itself, chosen by its identifier.
  3. Destination Site Address: the site that will receive the file.
  4. Destination Folder: the target folder on that site.
  5. If another file is already there: your choice when the new location has a file with the same name.

How do you set it up step by step?

  1. Open make.powerautomate.com and create a flow.
  2. Add a trigger, such as "When a file is created (properties only)" on the library that receives new files.
  3. Add the SharePoint action "Move file".
  4. In Current Site Address, pick the site from the list.
  5. In File to Move, select the Identifier dynamic content from the trigger.
  6. In Destination Site Address, pick the target site. Use the same site to move inside it.
  7. In Destination Folder, pick the folder.
  8. In If another file is already there, pick one option. Test with one file.

What should you pick for "If another file is already there"?

The field is a pick list. Common tutorials describe options to fail the action, replace the file, or move it under a new name. Open the list on your screen to see the exact words in your tenant.

If you cannot lose either file, pick the option that renames. Replace deletes the old file in the destination. Our advice, not a Microsoft rule: test with a dummy file first.

When should you copy instead of move?

Use Copy file when the original must stay in place. Use Move file when the file should live in one place only.

To move a whole folder, the connector has a separate "Move folder" action with the same five fields. Tutorials report that Move file works on one file at a time, so use Get files, then Apply to each, for many files.

Why does the flow fail or get stuck?

A common cause is a file that someone has open. See file is locked for shared use for the fix.

Another cause is that the flow's connection has no permission to add files in the destination folder. Test the folder by hand with the same account.

If your flow watches a library for new files, a move inside that same library may not count as a new file. Test it with one file. If the flow does not run, start it from a different trigger.

Can you create the destination folder first?

Yes. Add a Create new folder action before Move file. To build one folder per list item, see create a folder for each list item.

Want help with a flow that moves files?

I am Al Davies at 250 High Street LLC. I build SharePoint and Power Automate trackers remotely for small teams. The first call is free. You can see past work in the portfolio.

FAQ

Does Move file keep the file's version history?

Microsoft says the action works like the Move to command in libraries. Check one test file in your own library to see what history is kept.

Can I move a file to another SharePoint site?

Yes. Type the other site's address in Destination Site Address.

Is Move file different from Copy file plus Delete file?

Yes. Move file is one action and keeps one file. Copy file plus Delete file takes two actions and a failed delete can leave two files.

Sources