Version History Issues

Fix SharePoint Version History Details Hidden After Moving a File

Natalie Taylor Sep 30, 2026 869 views

Question details

Users are unable to view or expand detailed properties of a document's previous versions after moving the file between different SharePoint document libraries.

SharePoint Version History Details Hidden After Moving a File

Product: Microsoft SharePoint
Device & OS: not provided
Scenario: Moving documents from a source SharePoint library to a destination library while attempting to retain and view past version properties.
Observed behavior: The version history remains available, but detailed properties for versions created in the original source library cannot be expanded or viewed in the destination library.

Before you start

Ensure you have the necessary permissions in both the source and destination SharePoint libraries to view version history and manage file properties. Verify that versioning is fully enabled in the destination library before moving any important documents.

Solution 1Recommended

Use the Version History View Command

Directly open and inspect the contents of previous versions to access the information you need, bypassing the hidden properties menu.

Since the metadata properties from the original library cannot be expanded in the new location, the most reliable workaround is to directly view the file state at that point in time.

Open Version History

Hover over the moved file in the destination SharePoint library, click the three vertical dots (ellipsis) next to the file name, and select 'Version history'.

Locate the Target Version

Scroll through the version list to find the specific date and time of the older version whose details you wish to check.

View the File

Click the dropdown arrow next to the timestamp and select 'View'. This will open the document in its previous state.

Information: This workaround allows you to inspect the file's content directly, even though the metadata properties from the original library remain hidden in the SharePoint interface.

Solution 2

Restore an Older Version in the Destination Library

Restoring an older version creates a new current version that will correctly inherit and display the properties of the destination library.

Solution 3

Submit Feedback to the Microsoft Portal

Since this is a known systemic limitation in SharePoint, reporting it can help prioritize future fixes for archiving compliance.

Free Microsoft Office alternative

Experience Seamless Document Management with WPS Office

While SharePoint and Microsoft Office can sometimes present frustrating limitations with file migrations and version metadata, WPS Office provides a lightweight, highly compatible alternative for everyday document editing. Enjoy a familiar interface, native support for Microsoft formats, and built-in local version history features without the heavy enterprise overhead.

Fully compatible with Microsoft Word, Excel, and PowerPoint file formats (.docx, .xlsx, .pptx).Built-in local backup and file history features to easily manage document versions without metadata loss.Lightweight design ensuring fast installation and smooth performance on any device.Familiar, intuitive user interface that requires zero learning curve for seamless migration.

Frequently Asked Questions

Why do version properties disappear when moving files in SharePoint?

SharePoint handles metadata differently between libraries. When a file is moved, the raw file versions are migrated, but the associated metadata properties tied to the original library's specific columns often fail to map or expand properly in the new library's data structure.

Does the 'Copy to' function preserve version history better than 'Move to'?

No. Using 'Copy to' typically only copies the latest version of the file by default. You must use 'Move to' if you want to bring over the version history, despite the metadata property limitation.

Is there any SharePoint admin setting to fix the hidden version properties?

Currently, there is no known built-in SharePoint admin setting or toggle that natively restores the expandability of these original version properties in the destination library.

Can I retrieve the lost properties if I move the file back to the original library?

Moving the file back may sometimes restore access to the original library's metadata properties, but this depends on whether the original columns and metadata entries remained intact. Inspecting the version directly using the 'View' command is usually more reliable.

Document & File Issues