PLATFORM
InfoPath PDF Archive
MigrationFox reads InfoPath XML submissions out of a SharePoint form library — works on both SharePoint Server (on-premises) and SharePoint Online — parses every field value, generates a searchable PDF per submission, and uploads the PDFs to a destination SharePoint library you choose. The original XML stays where it is — nothing is deleted. After the July 14, 2026 retirement the PDFs are still readable forever; the XML wouldn’t be.
What Gets Archived
- Every XML submission in the form library — one PDF per submission
- All form fields — text, dropdowns, checkboxes, dates, person/group fields, nested groups, repeating sections
- Field labels — pulled from the InfoPath schema so the PDF reads as a labeled form, not a raw key/value dump
- Original submission metadata — submitter UPN, submission timestamp, library item ID embedded in the PDF
- Filename based on the source item — predictable naming so audit + e-discovery search still work
How It Works
- Connect SharePoint — OAuth into the tenant that hosts the form library (source) and optionally a different tenant or library for the destination
- Pick the form library — the wizard browses your sites and surfaces every InfoPath form library; you select one per job
- Pick the destination folder — any SharePoint document library on the destination tenant. Same-tenant archive into a "FormsArchive" library is the most common pattern
- Start Archive — MigrationFox lists every submission, parses each XML, renders the PDF, uploads to the destination, marks the source item as archived, and emits a per-form progress event
- Receive the manifest — on completion you get a CSV that maps every source item ID to its destination PDF path so legal / compliance can audit the conversion
Why a Purpose-Built Tool
The other migration tools on the market are all built around file-and-folder copy. InfoPath isn’t a file format problem — the XML is small and easy to copy. The challenge is rendering: you need to know the InfoPath schema (XSN template) to label the fields correctly, and you need a PDF renderer that produces readable output. MigrationFox is the only tool we know of that ships this as a built-in feature; teams have historically solved it with CA$40k+ consulting engagements or custom PowerShell that produces unreadable text dumps.
Pricing
InfoPath PDF Archive is billed per submission converted to PDF, not by GB. One InfoPath form template can have thousands of filled-out submissions — each submission becomes one PDF, and each PDF is charged separately:
- CA$0.15 per submission on the Pay-As-You-Go plan
- CA$0.10 per submission for Enterprise volume (10,000+ submissions in a single project)
Example: a form template with 5,000 filled-out submissions = 5,000 PDFs × CA$0.15 = CA$750 on PAYG, or CA$500 on Enterprise volume pricing. SharePoint storage for the resulting PDFs uses your tenant’s own allocation — MigrationFox does not bill for destination storage.
There is no free tier for InfoPath Archive — the cost reflects the rendering engine + per-submission QA we run on every conversion. For a tenant with thousands of forms across multiple libraries, talk to us — hello@migrationfox.com — and we’ll scope a fixed-price engagement to run the conversion ahead of the deadline.
Related Reading
- Why InfoPath is dying — the full background on the July 2026 retirement
- SharePoint migration tool — covers libraries, lists, and metadata if you’re consolidating sites at the same time
- Copilot Readiness assessment — surfaces InfoPath as a deprecated artifact when evaluating M365 readiness