InfoPath Is Officially Dead.
Here's Your Complete 2026 Migration Guide.

What Actually Happened on April 14, 2026

Microsoft ended mainstream support for InfoPath 2013 back in October 2020. Extended support — which provides security updates but no new features — ran until April 14, 2026. Now that that date has passed, here's what changed:

• No more security patches — any vulnerability discovered in InfoPath from this point forward will not be fixed by Microsoft.
• InfoPath Forms Services in SharePoint Online — Microsoft removed InfoPath Forms Services from SharePoint Online in 2019. If you're still using InfoPath forms in SharePoint Server on-premises, April 2026 ended your security coverage.
• InfoPath Filler — the client application that opens .xsn files still works but receives no updates. It will continue functioning until Windows incompatibilities make it unrunnable.
• Browser-compatible forms in SharePoint — if your forms relied on InfoPath Forms Services rendering in the browser, those stopped working in SharePoint Online years ago. On-premises SharePoint customers using SharePoint Server 2019 or earlier need to treat this as urgent.

Signs Your Organisation Is Still Using InfoPath

Many organisations don't even know they're still on InfoPath. Here are the signs:

• SharePoint lists with a customise form button that opens InfoPath Designer
• .xsn files in SharePoint document libraries or shared drives
• Forms that open in a browser with an "InfoPath" watermark or error message
• Workflows built in SharePoint Designer 2013 that feed data from InfoPath forms
• Users who have InfoPath Filler 2013 installed and use it to fill forms locally
• Form templates referenced in Central Administration (SharePoint Server on-premises)

If any of these apply, you have work to do. The good news: the replacement options in 2026 are significantly better than InfoPath ever was.

What to Replace InfoPath With — The Decision Matrix

The right replacement depends entirely on what you were using InfoPath for. InfoPath was used for very different things across different organisations — from simple HR surveys to complex multi-step forms with conditional logic, calculated fields, and workflow integration.

Power Apps for SharePoint List Forms — The Closest Direct Replacement

If your InfoPath forms were used to customise how data is entered into SharePoint lists — which covers the majority of InfoPath use cases — the closest direct replacement is the Power Apps-customised list form. Here's exactly how it works:

1. Open your SharePoint list → + New → Customise with Power Apps
2. Power Apps Studio opens with the list's default form pre-loaded as a starting canvas
3. Add conditional visibility rules, custom labels, dependent dropdowns, and calculated fields using Power Fx
4. Publish — the customised form replaces the default SharePoint form and appears when any user clicks "+ New" in the list
5. Data still goes to the SharePoint list — no schema changes required

This pattern handles the single most common InfoPath use case with no server-side code, no on-premises infrastructure, and no new licensing requirements beyond your existing Microsoft 365 plan.

Microsoft Forms — For the Simple Stuff

Not every InfoPath form needs Power Apps. If you were using InfoPath to collect internal feedback, run simple polls, or capture survey responses, Microsoft Forms is the correct replacement — and it's dramatically simpler.

Microsoft Forms gives you:

• Branch logic (show different questions based on previous answers)
• Multiple choice, ratings, ranking, text, date, file upload question types
• Real-time response dashboard with charts
• Excel export and Power BI integration
• Co-author mode for team-built forms
• External sharing — non-M365 users can respond

What it doesn't give you: deep SharePoint list integration, calculated fields, multi-screen workflows, or complex conditional logic trees. If your InfoPath form had any of those, you need Power Apps instead.

One More Thing: SharePoint Designer Is Gone Too

InfoPath and SharePoint Designer 2013 were often used together — InfoPath for the form, SharePoint Designer for the workflow. SharePoint Designer 2013 support ended January 13, 2026 (two months before InfoPath). If you have SharePoint Designer workflows still running, they're in the same position: unsupported and scheduled for removal.

Microsoft removed SharePoint Designer-based workflows from SharePoint Online tenants progressively in 2024. The replacement is Power Automate. If you're still running 2013 Workflow Platform workflows on SharePoint Online and they haven't broken yet, they will — check your tenant for active 2013 workflows now.

InfoPath Migration Checklist

Use this checklist to complete your InfoPath exit:

• Audit — search your SharePoint farm or SharePoint Online tenant for active InfoPath form libraries and list customisations. Export the list of .xsn files in use.
• Classify each form — simple survey, SharePoint list customisation, multi-step approval, or external-facing. Each class maps to a different replacement.
• Document the business logic — export each InfoPath form template and document the conditional rules, calculated fields, and workflow triggers before rebuilding. This is the hardest part of the migration.
• Rebuild simple surveys in Microsoft Forms — highest volume, lowest effort. Complete these first.
• Rebuild SharePoint list forms in Power Apps — use the "Customise with Power Apps" option from the list. Rebuild the conditional logic using Power Fx Switch/If expressions.
• Rebuild complex forms as Canvas Apps — multi-screen, approval-routed, or externally used forms need a full Canvas App build with Power Automate flows.
• Test with end users — InfoPath forms often had hidden dependencies (calculated fields referencing other SharePoint lists, workflow variables, People Picker fields). Test each rebuilt form with real users before decommissioning the InfoPath version.
• Decommission InfoPath filler — remove InfoPath Filler 2013 from managed devices via Intune or Group Policy once all forms are migrated. An unsupported application running on managed machines is a compliance finding.
• Migrate SharePoint Designer workflows — list your active SPD workflows and rebuild them in Power Automate. See our Power Automate guide for the current approach.

How Long Does a Migration Take?

Rough time estimates by form complexity:

• Simple survey / 5-field form → Microsoft Forms: 30–60 minutes per form
• SharePoint list customisation → Power Apps list form: 2–8 hours per form depending on rule complexity
• Multi-screen approval form → Power Apps Canvas App + Power Automate: 1–3 weeks per flow
• Complex enterprise form with external access → Power Pages: 4–8 weeks including testing and identity provider setup

For organisations with 20+ InfoPath forms in production, a structured migration project with a dedicated Power Platform resource is the fastest path. Trying to migrate alongside day-to-day work typically results in half-finished forms and regression issues that delay the project by months.