How to Fix Created By and Modified By Metadata After SharePoint Migration
Question details
The user needs to correctly preserve author metadata during a SharePoint migration to prevent generic administrator accounts from appearing in the user fields.

- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- Migrating files from a local file server to SharePoint Online using a migration tool.
- Observed behavior
- The Created By and Modified By columns in SharePoint Online incorrectly display BUILTIN\Administrators instead of the actual SharePoint administrator or original author account.
Ensure you have global administrator or SharePoint administrator permissions in Microsoft 365 and have the latest version of the SharePoint Migration Tool (SPMT) installed.
Use a User-Mapping CSV File in the SharePoint Migration Tool
Applying a user-mapping file during migration forces the tool to link local on-premises identities to the correct Microsoft 365 cloud accounts.
When moving data from an on-premises file server to the cloud, local user accounts (like BUILTIN\Administrators) do not inherently exist in Azure Active Directory. To preserve accurate file history, you must explicitly map the source identities to their corresponding target SharePoint accounts before running the migration.
Open a spreadsheet editor like WPS Spreadsheet or Notepad. Create a two-column CSV file where the first column contains the source local identity (e.g., the local administrator SID or login name) and the second column contains the target Microsoft 365 User Principal Name (UPN).
Launch SPMT and follow the prompts to select your source file server and target SharePoint Online site.
Navigate to the migration settings step within SPMT. Look for the 'Users and Groups mapping' or 'Identity mapping' section and choose the option to upload your custom CSV file.
Start the migration process. Once synchronized and completed, navigate to your SharePoint document library to confirm that the Created By and Modified By fields now display the correct target users.

Edit Your Migrated SharePoint Files with WPS Office
While Microsoft tools handle the heavy lifting of server migrations, you still need a fast, reliable way to view and edit your migrated documents. WPS Office is a robust, free alternative to Microsoft Office that offers seamless compatibility, ensuring your workflow remains uninterrupted post-migration.
- 1. Download WPS Office: Visit the official WPS website to download and install the free, lightweight office suite on your device.
- 2. Access Migrated Files: Download or sync your newly migrated files from SharePoint Online to your local computer.
- 3. Open and Edit Seamlessly: Open your files in WPS Office to view and edit them with formatting perfectly preserved.

Frequently Asked Questions
Why does the SharePoint Migration Tool display BUILTIN\Administrators?
This happens because the files were originally created or modified by a local server administrator account on your on-premises file server. Without a mapping file, SharePoint Online cannot translate this local identity to a Microsoft 365 cloud account, so it displays the original local group name.
Can I edit the Created By and Modified By fields after the migration is finished?
No, SharePoint Online does not allow users or administrators to manually edit the Created By or Modified By metadata fields through the standard user interface to preserve audit integrity. You must resolve this by deleting the affected files and migrating them again with a correct mapping file.
What is the correct format for the SPMT user-mapping file?
The user-mapping file must be a comma-separated values (.csv) file. It generally requires two columns: the first column for the source user's login name or Security Identifier (SID), and the second column for the target Microsoft 365 email address (User Principal Name).




