InfoPath forms after the retirement: what happens to your forms, and how to export form data to Excel or convert InfoPath XML to PDF

Microsoft’s notice records that InfoPath Forms Services in SharePoint Online is retired by July 14, 2026, and it says nothing about the form data already stored in your libraries. This page sets out what the notice says, what it leaves unsaid, the free routes to a spreadsheet or a PDF today, two paid routes stated neutrally, and one offline batch extractor that does not exist yet.

Covers: the retirement as Microsoft’s Message Center notice states it, the free ways to get stored form data into Excel or PDF, two paid routes with their prices where known, and an interest test for a proposed offline batch extractor. Doesn’t cover: repairing a broken form template, SharePoint permissions, or any promise that a particular tool will open a particular form. Guidance only, not a recommendation of any product. Independent guidance. Not affiliated with or endorsed by Microsoft. InfoPath and SharePoint are trademarks of Microsoft. Read the notice and the sources below (2 November 2026) and check the dates yourself.

What changed, and when

Two dates matter in Microsoft’s notice. InfoPath Forms Services in SharePoint Online is retired by July 14, 2026, and publishing new or updated forms was blocked after 18 May 2026. The notice points readers to Power Apps, Power Automate and Microsoft Forms for forms they need to keep using.

Message Center MC616550, as recorded:

retired by July 14, 2026

there is no migration tool provided

Source: Message Center MC616550, Microsoft 365 message centre (recorded copy on merill.net). Read 2 November 2026.

The notice is about the service and the forms. It says nothing about the submissions already stored in your libraries: the answers people typed into the forms. Microsoft’s suggested tools are for new or rebuilt forms, not for opening old submissions.

One point in the record is that stored data survives. That point is a third-party claim, not Microsoft’s. Lightning Tools published it on 14 August 2026; treat it as that company’s reading, not as a promise from Microsoft.

Lightning Tools, on stored data (a third-party claim, not Microsoft's):

Existing SharePoint list, library and XML data is not automatically deleted by the retirement

Source: Lightning Tools: InfoPath still working in SharePoint Online after the retirement. Published 14 August 2026. Read 2 November 2026.

Your routes today: getting the data out

Download the form files from the library

In SharePoint, open the library that holds the form, select the items and choose Download. InfoPath submissions are XML files in each item’s folder, with any attachments beside them. Copy what you find somewhere safe before you try anything, so a failed conversion never costs you the original.

Open the XML in Excel

Excel can open the downloaded XML directly. Open Excel, choose Data, then Get Data, then From File, then From XML, and pick one downloaded file. Excel offers the data as a table; load it. For a folder, repeat the step and append the tables into one sheet. Forms with repeating groups, such as several line items inside one form, usually arrive as extra tables or columns, so check one form against the screen before you trust the sheet.

Microsoft’s rebuild routes

Microsoft’s notice suggests Power Apps, Power Automate and Microsoft Forms. Those are for building a new form, or rebuilding an old one; they do not read the submissions you already have. Treat them as a route for the form, not for the stored answers.

The Microsoft Q&A thread

On a Microsoft Q&A thread about the end of InfoPath, an answer points to exporting XML or converting important forms to PDF. A later comment asks how to batch-export a whole library to PDF. The record this page uses shows no reply to that comment.

The Microsoft Q&A answer, dated 29 January 2026, as recorded:

You can also export XML submissions or convert important forms to PDF as a fallback

The follow-up comment, dated 3 March 2026, as recorded:

Can you please provide more details on how existing InfoPath submissions can be exported as PDFs? is there a tool that would allow batch print form submissions as PDFs for the whole library

Source: Microsoft Q&A: post InfoPath end of life. Read 2 November 2026.

Lightning Tools’ Form Migrator is the one priced product named in the record. It migrates forms to SharePoint lists or Dataverse. The recorded price starts at USD 3,750 for 25 libraries; the same record lists USD 6,550 for 50 libraries, USD 10,000 for 100 and USD 20,250 for 250, with mandatory 20% support in year one.

Form Migrator pricing, as recorded:

from USD 3,750 for 25 libraries

Source: Lightning Tools: SharePoint Form Migrator pricing. Read 2 November 2026.

Nutrient/Muhimbi converts InfoPath forms to PDF or Excel inside SharePoint or Power Automate workflows. That means an administrator and a tenant connection. We found no price for this route. Both are products named in the record; this page does not rate either of them.

Source: Nutrient: converting an InfoPath form to Excel. Read 2 November 2026.

An offline batch extractor we are testing

The idea is a Windows program you point at a folder of form files you have already downloaded. It reads each form, makes one Excel workbook for the folder and a PDF of each form, and uploads nothing: everything happens on your own machine. The price, if it is built, would be GBP 39 once.

This page is a test of interest, not a shop. There is no payment form and no email field anywhere on it. Pressing the button records one anonymous count for the day, and a short tag if the link you followed carried one. One press is allowed per page load; reload the page and you can press again.

Not on sale yet. This tool does not exist yet and may never be built. No payment is taken. Pressing only counts your interest.

How this page is checked

Every quoted line above is a line of the page’s one data file, and a test fails the build when a quote that is served is not a line of that file. Another test fails the build if a banned word appears. The quotations are copied exactly from the records, with the read date of each source; no web source was re-fetched for this build. If a source changes or we find an error, we correct this page and record it here. Read 2 November 2026.

No corrections yet (sources read 2 November 2026).