Version History Issues

Can You Convert XLSM to XLSB in SharePoint Without Losing Version History?

Steve KSteve K Nov 4, 2026 868 views

Question details

The user needs to convert an existing XLSM file to an XLSB file format within SharePoint without losing the original file's version history.

Can You Convert XLSM to XLSB in SharePoint Without Losing Version History?
Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Changing an Excel file's extension from XLSM (Macro-enabled) to XLSB (Binary) in a SharePoint document library.
Observed behavior
SharePoint treats the newly saved XLSB file as a completely new document, severing the link to the original XLSM file's version history.
Before you start

Before attempting to convert file formats in a shared environment, ensure you have downloaded a local copy of your original XLSM file and documented any critical historical versions.

Solution 1Recommended

Manage XLSM to XLSB Transitions by Archiving

Because SharePoint intrinsically treats different file extensions as entirely separate files, you cannot merge their version histories. You must use an archival approach.

SharePoint identifies files by their specific name and extension. When you convert an XLSM file to an XLSB file, SharePoint registers the XLSB as a new upload. Consequently, the previous version history remains attached only to the original XLSM file.

1
Convert and upload the new XLSB file

Open the original XLSM file in the Excel desktop app, select 'Save As', and choose 'Excel Binary Workbook (*.xlsb)'. Upload this new file to your SharePoint library.

2
Archive the original XLSM document

Instead of deleting the old XLSM file, rename it to include 'Archive' or move it to a dedicated archive folder in SharePoint. This keeps the original version history accessible for future reference.

3
Submit a service request for advanced assistance

If your organization has strict compliance policies requiring unified version history, navigate to the Microsoft 365 admin center and submit a service request to explore potential backend auditing solutions.

Manage XLSM to XLSB Transitions by Archiving
SharePoint Limitation: There is currently no native feature in SharePoint to bypass this limitation. Changing an extension always results in a new version history timeline.
Free Microsoft Office alternative

Try WPS Office for Seamless Excel File Management

While SharePoint and Microsoft Office have strict limitations on how file extensions and version histories are handled, WPS Office provides a lightweight, flexible, and free alternative. Experience seamless compatibility with all major Excel formats.

  1. 1. Download the software: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install WPS Office: Run the installer and follow the on-screen prompts to complete the setup.
  3. 3. Open your Excel files: Launch WPS Spreadsheet and open your XLSM or XLSB files directly to enjoy seamless editing.
Fully compatible with Microsoft Excel formats including XLSX, XLSM, and XLSB.Free to download, offering a rich set of spreadsheet tools without the subscription fees.Familiar user interface ensuring a smooth migration from Microsoft Office.Excellent local file management and backup features to help protect your document history.
microsoft office alternative - wps office

Frequently Asked Questions

Why does SharePoint drop my version history when saving as a new format?

SharePoint tracks a file's version history based on its unique document ID and file extension. When you use 'Save As' to change a file from XLSM to XLSB, SharePoint generates a new document ID, effectively starting a fresh version history for the new file.

Can I simply rename the file extension directly in SharePoint?

No, SharePoint's web interface does not allow you to directly edit a file's extension (e.g., renaming 'file.xlsm' to 'file.xlsb'). You must open the document in the desktop application to save it under the new format.

Will Microsoft Support be able to merge my version histories?

Generally, version histories cannot be merged between two different file types, even by support. However, submitting a service request through the Microsoft 365 admin center may provide you with alternative audit logs or compliance workarounds depending on your enterprise plan.