The process of building custom applications and tools that interact with Microsoft SharePoint, including SharePoint Online in Microsoft 365.
Please note that our forum is a public platform, and we will modify your question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.
Currently, I have not identified any official article that directly addresses the specific error “IpLabelPromotionModuleVersion attribute is not declared” when copying a Classic List via Site Manager (Content and Structure).
Based on my research, “attribute is not declared” is essentially a schema validation error. When you use Site Manager to copy a List, SharePoint internally performs an export of the List definition into an XML file, then imports that XML into the destination site. This error indicates that the exported XML contains the attribute IpLabelPromotionModuleVersion, but the validation framework used by Site Manager does not recognize or define this attribute.
The IpLabel prefix likely relates to Information Protection/Sensitivity Labels from Microsoft Purview. In recent updates, Microsoft has introduced hidden attributes to modern Lists and Libraries to support data protection and compliance features. However, Site Manager (sitemanager.aspx) is a Classic feature that has been deprecated for many years. Its underlying codebase and internal XML schema have not been actively updated to recognize newer metadata attributes such as IpLabelPromotionModuleVersion.
As a result, when Site Manager attempts to copy a List that contains these newer Information Protection attributes, the legacy XML parser fails schema validation. The tool encounters an unknown attribute, reports “attribute is not declared”, and immediately aborts the copy operation.
You could consider to these workarounds:
Use PnP PowerShell
This is the most stable and scalable approach, especially for large Lists or Lists with many attachments. It also avoids UI timeout issues.
Using PnP PowerShell, you can programmatically retrieve items from the source List and insert them into the destination List in batches.
Export to Excel and Re‑Import
If your List contains only simple columns (Text, Number, Choice, etc.) and does not include Attachments, you may use this method:
Navigate to the source List.
From the ribbon or command bar, select Export to Excel.
SharePoint downloads an Excel file containing all 4,000 rows. Save this file as your backup.
On the destination site, select Add an app > Import Spreadsheet.
Browse to the downloaded Excel file and select the data range.
SharePoint will automatically generate a new List with the imported items.
Note:
Attachments are not preserved.
System columns such as Created By, Created Date, and Modified By will be reset to the importing user and time.
For futher information, you can refer via:
Learn about sensitivity labels | Microsoft Learn
Sorry, something went wrong error on a Site Page with a Pages library web part added - SharePoint |…
Enable sensitivity labels for files in SharePoint and OneDrive | Microsoft Learn
PnP PowerShell | PnP PowerShell
How to duplicate SharePoint lists without breaking structure
Note: This information is provided as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.
Please note that this summary is based on my own findings and may not fully address your concerns. However, with your help and more detailed information, we can work together to find a solution.
Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread.