Fix SharePoint lastModifiedBy Not Updating After Moving Files
Question details
The user needs to understand why a file moved from one drive to another retains its original lastModifiedBy metadata instead of updating to show the user who executed the move.

- Product
- SharePoint / OneDrive
- Device & OS
- not provided
- Scenario
- Moving a document between different drives or SharePoint sites.
- Observed behavior
- The lastModifiedBy value remains identical to its state before the move rather than reflecting the account of the person who moved the file.
Determine whether the file was moved manually through the SharePoint interface or automatically via a background script or Power Automate flow, as this determines how metadata is processed.
Investigate Custom Power Automate Flows
Use this solution to check if an automated background process moved the file, which frequently causes metadata to be retained or updated incorrectly.
In standard manual cross-site or cross-OneDrive moves, the createdBy and modifiedBy fields normally update to reflect the user performing the action. If they do not, it is highly likely that a custom Power Automate flow or another automated migration process is handling the move. Many automation tools are explicitly configured to retain original metadata during file transfers.
Navigate to the Power Automate portal, locate any flows tied to the specific SharePoint document library, and check the Run History around the time the file was moved.
Look at the document's version history in SharePoint. Compare the lastModifiedBy values immediately before and after the move operation was recorded.
If a flow is responsible, open the flow in edit mode and inspect the 'Move file' or 'Copy file' action. Check if it is running under a system account or if it is configured to carry over file metadata.

Perform a Manual Move Test
Manually moving a file helps isolate whether the issue is systemic to your SharePoint environment or isolated to a specific automated process.
Try WPS Office for Seamless Document Management
While SharePoint handles complex backend metadata like the lastModifiedBy property, WPS Office provides a lightweight, free alternative for creating, editing, and managing your daily documents. Enjoy a smooth experience without the heavy system requirements of other Office suites.
- 1. Download the installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the software: Run the installer and follow the simple on-screen instructions to set up WPS Office on your device.
- 3. Open and edit seamlessly: Launch WPS Office and open your existing Office documents directly to start editing with full format retention.

Frequently Asked Questions
Does copying a file in SharePoint update the modified by property?
Yes, copying a file usually creates a brand-new instance of the document. As a result, both the createdBy and lastModifiedBy properties will typically update to reflect the user who performed the copy action.
How do administrators preserve original metadata when moving SharePoint files?
To preserve original metadata such as creation dates and authors, administrators often use specialized third-party migration tools or the official SharePoint Migration Tool (SPMT) rather than the native web interface.
Can I manually edit the lastModifiedBy value of a document?
No, standard users cannot manually edit the lastModifiedBy field. It is a system-generated, read-only property that SharePoint updates automatically based on backend operations and user actions.




