Microsoft 365 Migration

Why SharePoint Shows System Account as Last Editor After Migration

Maira Mehtab Sep 22, 2026 869 views

Question details

Users migrating files to SharePoint notice that the metadata for the last file editor displays 'System Account' instead of the actual original user's name.

Product: SharePoint / Microsoft 365
Device & OS: not provided
Scenario: Migrating files and data to SharePoint using third-party platforms like BitTitan or native Microsoft migration tools.
Observed behavior: The Last Modified By or Last Editor field on migrated files is replaced with 'System Account', typically because the user mapping failed or metadata was applied by a background service process.

Before you start

Obtain the migration tool's log files and confirm the exact names of the affected files before escalating the issue to your Microsoft 365 administrator.

Solution 1Recommended

Investigate Metadata Issues via Microsoft 365 Admin Center

Since system metadata cannot be manually corrected by end-users, you must work with your Microsoft 365 administrator to open a support ticket for investigation.

During migration, if the original user cannot be resolved in the destination tenant, or if the migration tool relies on a background service process to stamp metadata, SharePoint defaults to 'System Account'. Fixing this requires backend investigation by Microsoft support or correcting the migration mapping.

Review Migration Logs

Check the SharePoint Migration Tool or BitTitan documentation and review your migration logs to identify if there were user mapping errors or unmapped accounts.

Contact Your Administrator

Reach out to your organization's Microsoft 365 administrator and provide them with the list of files showing the 'System Account' anomaly.

Open a Service Request

Have the administrator log into the Microsoft 365 admin center, navigate to 'Support', and select 'Help & support' to open a new service request with Microsoft's development team.

Free Microsoft Office alternative

A Lightweight and Compatible Office Suite for Your Team

While backend SharePoint migration issues require Microsoft support, optimizing your team's document creation workflow doesn't have to be complicated. WPS Office is a highly compatible, free alternative to Microsoft Office that easily handles your everyday document needs without expensive subscriptions.

1. Download WPS Office: Visit the official WPS Office website and download the installer for your operating system.
2. Install the Application: Run the installation file and follow the on-screen prompts to set up the software.
3. Open Your Office Files: Launch WPS Office and directly open your existing Word, Excel, and PowerPoint documents with full formatting preserved.

Fully compatible with Microsoft Office formats (DOCX, XLSX, PPTX)Free and lightweight suite with a familiar, easy-to-use interfaceSeamless integration with major cloud storage servicesSmooth transition with a zero learning curve for your team

microsoft office alternative - wps office

Frequently Asked Questions

Can I manually change the last editor back to the original user in SharePoint?

No, standard SharePoint permissions do not allow end-users to manually edit system metadata like the 'Last Modified By' field. Correcting this requires specialized migration tools or administrative scripts.

Why did my migration tool fail to map the original user?

User mapping failures typically happen if the source user account does not exist in the destination Microsoft 365 tenant, if there is a mismatch in the mapping file, or if the migration tool lacks permissions to impersonate users.

Does the System Account metadata affect file permissions?

No. The 'Last Editor' field is only informational metadata. The actual viewing and editing permissions of the file are determined by the SharePoint site's access control lists and sharing settings.

Migration & Recovery