GUIDE · April 6, 2026 · Updated October 25, 2026 · 10 min read
InfoPath Is Retired: How to Export Your Form Data and Archive It as Searchable PDFs
If your organization used InfoPath forms in SharePoint, the retirement has already happened. On July 14, 2026, Microsoft removed InfoPath Forms Services from SharePoint Online entirely. The forms didn't just stop working. The underlying XML submissions are now effectively unreadable without the InfoPath client, which reached the end of its own support on the same date.
This isn't a theoretical risk. Thousands of organizations still have active InfoPath form libraries containing HR onboarding records, expense approvals, inspection reports, compliance forms, and other business-critical data. With the rendering engine gone, those XML files are opaque blobs, technically still there, but practically useless until they are converted.
InfoPath Forms Not Opening in SharePoint Online?
That's expected now. Since July 14, 2026, SharePoint Online no longer includes InfoPath Forms Services, so opening a submission from a form library no longer shows the form in the browser. Nothing is wrong with your tenant and nothing was deleted: each submission is still stored as an .xml file in its library, and the form's .xsn template is still there too. What's gone is the engine that combined the two into a readable form.
So the useful question is no longer how to fix the form, but how to get the data out. Here are the options.
How to Export InfoPath Form Data
There are three ways to get data out of an InfoPath form library, from free and manual to fully automatic:
- Download the XML files. Sync the form library to your PC with OneDrive, or use PnP PowerShell to download every
.xmlsubmission and the.xsntemplate. It's free and gives you the raw data, but XML isn't readable for people, and files attached to a form stay encoded inside it. - Open them in the InfoPath desktop client. A PC that still has InfoPath Filler or Designer 2013 may open downloaded submissions one at a time. The client is out of support since July 14, 2026 and doesn't scale beyond a handful of forms.
- Convert them to PDFs and a spreadsheet. MigrationFox InfoPath PDF Archive reads every submission with its template and writes a searchable PDF per form, recovers the attached files, and creates a CSV index (it opens in Excel) with one row per form and a column for every field. This is the route for records you must keep.
What Changed on July 14, 2026?
Here's what the InfoPath retirement means in practice:
- InfoPath Forms Services is removed from SharePoint Online. Browser-based form rendering stops completely.
- InfoPath form libraries remain, but the XML submissions inside them no longer display in the browser.
- The InfoPath 2013 desktop client is already out of extended support. While it may still open some files, it's unsupported and won't be updated.
- XSN template files still exist in SharePoint but serve no functional purpose without the rendering engine, except as the key to reading the XML.
- No automatic conversion: Microsoft does not convert your form data to any other format. Until you convert it, the data is inaccessible.
For organizations subject to regulatory compliance, legal holds, or data retention policies, this is an open problem today. You can't comply with records requests if you can't read the records.
Why Copying the Files Isn't Enough
Moving documents from one location to another doesn't help here, because InfoPath forms aren't simple files. They're a combination of:
- An XSN template that defines the form structure, layout, and field definitions
- XML submissions that contain the actual form data in a structured format
- Rendering logic that combines the two into a human-readable form
Copy the XML files from point A to point B and, at the destination, you still have unreadable XML. Moving the problem doesn't solve it.
What organizations actually need is data extraction and format conversion: taking the structured data from XML submissions, mapping it against the XSN template, and producing a human-readable output. That's a fundamentally different operation than file migration, and it's what MigrationFox InfoPath PDF Archive is built to do.
MigrationFox InfoPath PDF Archive: How It Works
MigrationFox provides a complete InfoPath XML-to-PDF archival pipeline. Here's what each step does:
Step 1: Point It at Your Forms
There are two ways in. If the form library is in SharePoint Online, connect your Microsoft 365 account and enter the form library name; MigrationFox reads the submissions and the template straight from the library. If the forms live somewhere else (an on-premises SharePoint farm, an export, or a file share), copy the .xml submissions and the .xsn template into a folder. On MigrationFox web, the File share agent (added from the Devices page) reads that folder and sends the forms to MigrationFox to be turned into PDFs, billed per form. In MigrationFox for Windows, point the app at the folder and the forms are turned into PDFs on the PC, under a MigrationFox Pro license or the free trial (14 days, 2 GB, 100 InfoPath forms).
Step 2: Read the Template
The XSN template is unpacked to recover the form's field definitions, question labels, data types, and dropdown choice lists, everything needed to understand the structure of each submission.
Step 3: Parse XML Submissions
Each XML submission is parsed against the template. Every field value is matched to its label, dropdown codes are resolved back to the answer text the person actually picked, dates are formatted, and repeating sections and nested groups are kept together.
Step 4: Generate Searchable PDFs
The extracted data is rendered into a clean, text-based (so fully searchable) PDF. Each PDF includes:
- All form field labels and values, grouped by section
- Repeating sections shown as numbered items (Item 1, Item 2, and so on)
- Formatted dates and preserved line breaks in multi-line text
- A header showing the form name, submission date, and source library, plus PDF document properties (title, author, subject, keywords) that search and records tools can read
Step 5: Recover Attached Files
InfoPath stores file attachments inside the XML as encoded text, so a plain copy of the XML gives you nothing you can open. MigrationFox decodes each attachment back to its original file (the spreadsheet, document, or image the person attached) with its original file name, and saves it next to the submission's PDF. The PDF lists each attached file by name and size.
Step 6: Save to Your Destination, With an Index
Each submission gets its own folder holding its PDF and any recovered attachments. Alongside them, MigrationFox writes a submission index as a CSV file (it opens in Excel): one row per form, with the submitted date, the submitter, the PDF and attachment file names, and a column for every form field. The PDF is the compliance record; the index is the view you sort, filter, and analyze. PDFs go to a SharePoint Online document library. When you archive from a folder with the Windows app, they can also go to another connected cloud destination or straight to a local folder or file share.
Why PDFs? The Case for a Universal Format
You might wonder: why convert to PDF instead of Excel, CSV, or another structured format? There are several compelling reasons:
- Universally readable: every device, browser, and operating system can open PDFs. No special software required.
- Searchable: SharePoint indexes PDF content, so your form data becomes full-text searchable in SharePoint Online.
- Compliance-friendly: PDFs are an accepted format for legal holds, audit trails, and regulatory compliance. Courts accept PDFs. They don't accept raw XML.
- Lockable: PDFs work with SharePoint retention labels and records settings, so the archive can be protected from modification.
- No dependency: unlike XML (which needs a template to interpret), PDFs are self-contained. They'll be readable in 10, 20, or 50 years.
- Readable by anyone: questions and answers appear in plain language, so a reviewer can understand the record without knowing the original form structure.
PDF is the record, but it isn't the only output. The submission index CSV gives you every field value as a spreadsheet for reporting, and recovered attachments come back as the original files.
Step-by-Step: Archive Your InfoPath Data with MigrationFox
Here's how to get your InfoPath form history archived:
1. Preview One Form Free
Drop one .xsn template and one .xml submission onto the free browser preview. You get the real PDF back, plus any attached files recovered from the submission. No signup needed.
2. Sign Up and Choose Your Source
Create a free MigrationFox account. For a SharePoint Online form library, connect your Microsoft 365 account and enter the form library name; on MigrationFox web the archive runs in our cloud, so your PC can be off. For forms you have copied to a folder (for example, exported from an on-premises SharePoint farm or a file share), use MigrationFox for Windows on a PC. Install it for Anyone using this computer if it should keep running with nobody signed in.
3. Configure the Destination
Choose the SharePoint site and document library where the archived PDFs will be stored. A dedicated "InfoPath Archive" library keeps things organized. In MigrationFox for Windows, you can also save to a local folder or file share.
4. Run the Archive Job
Start the job. MigrationFox processes each submission, generates the PDF, recovers its attachments, and saves them in a folder per submission, then writes the submission index CSV at the top of the archive. You can follow progress live, with file-level status for every submission.
5. Verify and Validate
Once complete, spot-check the generated PDFs against the original forms. Verify that field values, dates, repeating sections, and attachments match. The job report shows every file processed and any errors encountered.
A Practical Archive Plan
The retirement date has passed, so the order of work is what matters now:
| Step | Action |
|---|---|
| 1. Inventory | List your InfoPath form libraries. Identify which ones hold records you must keep. |
| 2. Preview | Run one real submission through the free browser preview to check the PDF output. |
| 3. Pilot | Archive one form library end to end. Validate field labels, dates and repeating sections. |
| 4. Archive | Archive the remaining libraries, highest-risk records first. |
| 5. Sign off | Keep the submission index CSV with the archive and decommission the old libraries once validated. |
Frequently Asked Questions
Can I still open InfoPath forms in SharePoint Online?
No. Since July 14, 2026, SharePoint Online can't display InfoPath forms in the browser. The submissions are still in their libraries as XML files, so you can download them or convert them to PDFs.
How do I export InfoPath form data to Excel?
Every MigrationFox archive run writes a submission index as a CSV file, one row per form with a column for every field, and it opens directly in Excel. To do it by hand instead, download the XML submissions and map their fields yourself with Power Query.
How many form submissions can MigrationFox process?
There's no cap on the number of submissions. Form libraries with thousands of submissions run as a single job.
Does this work with InfoPath forms on SharePoint Online?
Yes. If you have InfoPath form libraries on SharePoint Online, MigrationFox can archive those as well using OAuth-based connectivity.
What about forms with attachments?
Files attached inside a submission are extracted back to their original files, with their original names, and saved in the submission's folder next to its PDF. The attachment is kept in its native format rather than as an unreadable block of encoded text, and the submission index lists which files belong to which form. You can check this on your own form with the free preview, which offers each recovered file for download.
Can I export to formats other than PDF?
Every archive run also writes a submission index as a CSV file, one row per form with a column for every field, which opens directly in Excel. If you need the raw structured data, the XML files can also be migrated as-is to your destination for programmatic access.
What does it cost?
InfoPath PDF Archive is billed per form, pay as you go, with no subscription, and form credits never expire. Large orders get a lower per-form rate automatically. Archives run from the Windows app are included with MigrationFox Pro (the free 14-day trial covers up to 100 forms). See pricing for current rates. Use the free browser preview to validate the PDF output on one of your own forms before you buy.
Your Records Are Still Recoverable
The InfoPath retirement has happened, but the data hasn't gone anywhere: the XML submissions and XSN templates are still in your libraries. As long as they're there, they can be turned into readable records, and the sooner they are, the sooner a records request or audit stops being a problem.
The good news: archiving your InfoPath forms as PDFs is straightforward with the right tool, and you can validate the process for free before committing. Start with a single form library, verify the output, and scale from there.