SharePoint Document Issues

How to Fix SharePoint Metadata Lost When Copying Files

Anum MushtaqAnum Mushtaq Nov 3, 2026 872 views

Question details

Users lose metadata in custom columns when copying or moving files between SharePoint document libraries or Microsoft Teams.

How to Fix SharePoint Metadata Lost When Copying Files
Product
SharePoint
Device & OS
not provided
Scenario
Copying or moving files and folders from one SharePoint document library or Teams channel to another.
Observed behavior
Custom metadata column values (such as 'Form Ref') become blank in the destination library, even though the destination has a column with the exact same name and order.
Before you start

Ensure you have Site Owner or Full Control permissions in both the source and destination SharePoint sites to view and edit site columns and term store settings.

Solution 1Recommended

Verify and Align Site Columns and Term Sets

Matching column names do not guarantee metadata transfer; the underlying site columns and internal IDs must be configured consistently.

When files are copied between document libraries, SharePoint maps metadata based on the column's internal GUID (Globally Unique Identifier), not its display name. If you manually created a column with the same name in the destination library, it will have a different GUID, causing the metadata to be dropped.

1
Check the column type

Navigate to the source library, click on the Gear icon, and select 'Library settings'. Click 'More library settings' and look under the Columns section to see if the affected column is a 'Managed Metadata' column or a standard choice/text column.

2
Verify Site Column configuration

Go to Site Settings > Site columns. Ensure the column was created at the Site Level rather than the List Level so that it can share the same internal ID across different libraries within the site collection.

3
Check Term Store Management

If the column uses managed metadata, open the Term Store Management Tool from the SharePoint Admin Center. Ensure the destination site has access to the exact same term set as the source site.

4
Re-add the column from existing site columns

In your destination library, delete the manually created column. Then, go to Library settings > Add from existing site columns, and select the shared site column used in the source library. Test copying a file again to see if the metadata is preserved.

Verify and Align Site Columns and Term Sets
Cross-Site Collection Limitations: If you are copying files to a completely different site collection or Team, local site columns will not share GUIDs. You must use the Content Type Hub or enterprise-level Term Store to publish the columns across different site collections for metadata to transfer successfully.
Free Microsoft Office alternative

Try WPS Office for Seamless Document Management

While SharePoint handles complex site metadata and libraries, WPS Office provides a lightweight, highly compatible, and free alternative for creating, editing, and managing your everyday Office documents.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Free and lightweight, avoiding the heavy resource usage of standard Office applications.Familiar user interface with built-in cloud sync for easy and organized document file management.Includes a powerful built-in PDF editor and converter at no extra cost.
microsoft office alternative - wps office

Frequently Asked Questions

Why does a column with the exact same name not retain its data when moved?

SharePoint uses internal GUIDs (Globally Unique Identifiers) to map columns, not display names. If the column was manually created in the destination library, its GUID won't match the source, resulting in blank metadata when files are copied or moved.

Does moving files instead of copying them preserve metadata?

No. Moving files uses the same underlying mechanism for metadata transfer across different libraries. If the site columns and term sets do not share the exact same internal configuration, the metadata will still be lost.

How do I ensure columns share the same internal ID across different libraries?

You need to create the column as a Site Column at the parent site level or in the Content Type Hub. Once created, add it to both the source and destination document libraries using the 'Add from existing site columns' option instead of creating new local columns.