What the deadline means
The deadline affects organizations still depending on SharePoint Online browser forms powered by InfoPath Forms Services. The impact varies by tenant and form pattern, so the first step is to determine which forms still exist and which business processes depend on them.
Inventory first
Find form libraries, list forms, promoted fields, secondary lists, and business-critical processes that still launch InfoPath.
Classify by risk
Separate simple SharePoint list forms from multi-view, rule-heavy, code-backed, or integration-heavy forms.
Replace in waves
Start with high-volume and low-complexity forms, then schedule complex forms for builder review and user acceptance testing.
Recommended migration sequence
Collect packages
Export or gather .xsn packages and any supporting notes from the existing SharePoint sites.
Run free analysis
Use Form Migrator to identify views, fields, rules, media, data connections, and SharePoint targets.
Group forms by effort
Use compatibility results to create quick-win, standard, and manual-review migration waves.
Export, validate, and publish
Generate packages for supported forms and validate the Power Apps result in the destination tenant.
What to watch for
- Forms that rely on custom script or code-behind should be scoped for manual rebuild patterns.
- Secondary data connections need destination SharePoint lists or alternative Power Apps connectors.
- Single-view forms with hidden sections may need to become multiple Power Apps screens for a cleaner user experience.
- Form libraries may need a different migration strategy than simple list forms because submitted XML and promoted columns are separate concerns.
Common questions
What should we do first?
Start with an inventory and free analysis. Do not wait until rebuild work begins to discover custom code, missing lists, or unsupported controls.
Is Power Apps the only replacement?
No, but it is the most natural Microsoft 365 replacement path for many SharePoint-backed forms, especially when the data already lives in SharePoint lists or libraries.
Can we wait until 2026?
Waiting increases delivery risk. The forms that look simple may have hidden rules, secondary lists, or XML patterns that need time to validate.