SharePoint Rules: Move files when metadata changes

Key insights

• Create the rule in a document library and choose the file-or-metadata-modified scenario.
• Set a condition such as Status changing to Archived, then choose Move file to or Copy file to.
• The rule can send a file to a destination library on another site.
• A move can retain metadata when the destination has matching columns; a copy does not carry metadata.
• Rules apply to files in document libraries, not folders or lists, and may take a short time to run.

SharePoint Rules can move or copy a file when its metadata changes, such as when someone changes a Status value to Archived, without requiring a Power Automate flow. This is useful for people who manage documents in a SharePoint library and need a simple, event-based way to route files. SharePoint Maven Inc demonstrates a rule that moves an archived policy into another library.

What it does

A SharePoint Rule can respond to a file or metadata change and perform an action, including moving or copying the file to a selected site and library. For example, a policy library can use a Status column: when a policy’s status changes to Archived, the rule moves it into a Policy Archive library. The user who changes the status does not need edit rights to the destination library, according to the demonstration’s description.

This is different from selecting Move to or Copy to for a manual file operation. The rule is configured in advance, so the user changes the metadata and SharePoint performs the configured action after a delay. The demonstration presents this as an alternative to creating a Power Automate flow for this particular scenario, not as a replacement for every kind of workflow.

Who it is for and what you need

The feature is relevant to library users who manage documents using metadata and want a file routed when a field changes. It may also help SharePoint owners who want a basic document process that users can configure without building a flow. The example uses a Status column with an Archived value and a separate destination library.

The supplied material does not specify a license, tenant requirement, rollout stage, preview status, or regional availability. It also does not provide a full permission matrix. The description says the person changing the metadata does not need edit rights to the destination library, but does not explain what permissions are otherwise required to create a rule or access the source library.

How it works

In the demonstration, the rule is created from the source document library. The transcript gives the menu path as Integrate > Rules; the published description names Automate > Rules. The material does not explain why these labels differ, so check the available Rules entry in your library.

1. Open the source document library and choose its Rules option, then select the command to create a new rule.
2. Choose the scenario for when a file or its metadata is modified.
3. Set a condition, such as Status changing to the exact value Archived.
4. Choose Move file to or Copy file to, then select the destination site and library.
5. Create the rule. Afterward, changing a file’s status to Archived triggers the configured action.

In the example, the rule sends a policy from the main library to Policy Archive on the same site. The description says a destination can be a different site as well. When the metadata was changed, the file did not move immediately; the demonstration reports a delay of roughly 30 to 40 seconds before checking the destination.

Plan the destination’s columns before relying on metadata after a move. The description says a move keeps metadata when the source and destination columns match, while a copy does not carry metadata. In the example, the destination lacked the same metadata fields, so the moved document arrived without those values.

Limitations and open questions

The described Rules action is for files in document libraries; it does not apply to lists or folders. It can take a short time to run, so users should not expect the file to relocate at the exact moment they change its metadata. The source material does not give a guaranteed processing time or explain how the rule behaves if the destination is unavailable.

The demonstration also says there is no workflow history to trace. That matters for support: the material does not describe a run log or a detailed way to investigate a missed or delayed move. If you need that kind of visibility, or more complex sequential logic, the source does not establish that Rules will meet the requirement; it only demonstrates the basic metadata-triggered move.

There is no comparison of all Rule actions, no guidance on limits such as how many rules a library can have, and no official Microsoft documentation among the supplied sources. Confirm the rule’s behavior with a test file and check the destination’s columns before applying it to important documents.

Sources

• SharePoint Maven Inc demonstration of metadata-based file Rules
• SharePoint Maven Inc website

Frequently asked questions

Can SharePoint Rules move a file when a metadata value changes?

Yes. The demonstrated rule triggers when a file or its metadata is modified and can move or copy it based on a condition such as Status changing to Archived.

Do SharePoint Rules work with folders or lists?

The supplied description says this action is for files in document libraries, not folders or lists.

Does a SharePoint Rule preserve metadata when it moves a file?

The description says a move retains metadata when the destination has matching columns. It says a copy does not carry metadata.

How long does a SharePoint metadata Rule take to move a file?

The demonstration reports that the move was not immediate and took roughly 30 to 40 seconds in its test. It does not provide a guaranteed processing time.