How to Bulk-Move Files from SharePoint Subsites to a Central Library
Question details
Consolidate files scattered across various country-specific SharePoint subsites into a single central document library, preserving organization via metadata.

- Product
- SharePoint / Power Automate
- Device & OS
- not provided
- Scenario
- Migrating files from multiple subsites with varying file types and naming conventions into a unified storage location.
- Observed behavior
- Files need to be moved to a centralized location and organized using custom country metadata and filtered views instead of physical folders or separate sites.
Ensure you have Site Owner or Site Admin permissions for both the source subsites and the destination central library, and that you have an active Power Automate license to create the necessary flows.
Use Power Automate to Migrate and Tag Files
Build an automated flow in Power Automate to retrieve files from multiple subsites, copy them to a central library, and apply country-specific metadata.
By utilizing Power Automate, you can dynamically scan through your subsites, extract documents regardless of their naming conventions, and push them into a single centralized repository.
Instead of relying on rigid folder structures, applying custom metadata (like 'Country') during the flow ensures your central library remains searchable and can be easily sorted using SharePoint's filtered views.
Log in to Power Automate, go to 'My flows', and create a new Instant cloud flow or Scheduled cloud flow depending on how you want to trigger the migration.
Add a 'Send an HTTP request to SharePoint' action to dynamically query and retrieve the list of target subsites and their respective document libraries.
Use the 'Get files (properties only)' action within a loop to fetch the list of files and their identifiers from each identified subsite library.
Add the 'Create file' action. Set the destination to your new central library, mapping the original file's name and dynamic file content retrieved from the source.
Add the 'Update file properties' action immediately after creating the file. Select the newly created file's ID and populate the 'Country' column to categorize the document for filtered views.

Looking for a Lightweight Alternative to Microsoft Office?
While SharePoint and Power Automate handle complex administrative migrations, day-to-day document editing shouldn't be a hassle. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office for all your document, spreadsheet, and presentation needs.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install and Launch: Run the installation file. Once completed, launch the application to access Writer, Spreadsheets, and Presentation modules.
- 3. Open Your Documents: Directly open any Microsoft Office files you have downloaded from SharePoint to view and edit them seamlessly.

Frequently Asked Questions
Can I move folders instead of just files using Power Automate?
Power Automate's standard actions focus on files. To replicate folder structures, you must create the folders dynamically in the destination before creating the files inside them. However, utilizing metadata tagging is generally preferred over traditional folders in modern SharePoint architecture.
What happens if a file with the same name already exists in the central library?
By default, the 'Create file' action may fail or overwrite the existing file depending on your flow configurations. It is highly recommended to implement a condition to check for existing files or append a unique identifier to the filename during the migration loop.
How do I create filtered views based on the Country metadata?
In your SharePoint central library, click 'Add column' to create a Choice column named 'Country'. After your Power Automate flow populates this metadata, click the filter icon on the column header, select a specific country, and click 'Save view as' to create a dedicated view.
Do I lose the original version history when moving files via Power Automate?
Yes, standard 'Create file' actions in Power Automate only copy the latest published version of the document. If preserving full version history is critical for compliance, you will need to use a dedicated migration tool like the SharePoint Migration Tool (SPMT) instead of a custom flow.




