Compatibility
Compatibility at a glance
Form Migrator is focused on moving InfoPath forms into Power Apps with a clear view of what is already supported, what is partial, and what still needs manual work.
Entry points
3 Supported2 Partial2 Planned1 Not available
Launch patterns, hosting models, and opening context.
Form features
12 Supported10 Partial2 Planned1 Not available
Layout, fields, rules, data connections, and submit behaviors.
Legend
SupportedPartialPlannedNot available
Status is shown per item with notes where relevant.
Package support
Power Apps package generation is aimed at InfoPath form packages and related exports. Layout, rules, data connections, and legacy behaviors may still require manual review depending on the source form and target environment.
Entry points
Expand a group to view the current status for each entry-point pattern.
Embedded2 items0020
Embedded
2 items
| Entry point | Status | Notes |
|---|---|---|
| SharePoint page embed | Planned | Planned for future packaging guidance. |
| Teams tab launch | Planned | Requires tenant-specific deployment steps. |
Legacy behaviors1 items0001
Legacy behaviors
1 items
| Entry point | Status | Notes |
|---|---|---|
| Re-open from email / routed link | Not available | Requires custom navigation or custom app logic in Power Apps. |
SharePoint3 items2100
SharePoint
3 items
| Entry point | Status | Notes |
|---|---|---|
| Display / read-only form | Partial | Read-only experiences may need manual tuning after import. |
| Edit item form | Supported | — |
| New item form | Supported | — |
Standalone2 items1100
Standalone
2 items
| Entry point | Status | Notes |
|---|---|---|
| Browser launch | Supported | — |
| Query-string / context parameters | Partial | Parameter mapping may need review after import. |
Form features
Expand a category to view the current status for each feature.
Data connections5 items2210
Data connections
5 items
| Feature | Status | Notes |
|---|---|---|
| Office 365 Users | Supported | — |
| REST / HTTP-based integrations | Partial | Connection details and authentication often need manual review. |
| SharePoint lists / libraries | Supported | — |
| SOAP / legacy web services | Planned | Legacy SOAP patterns usually require custom modernization work. |
| SQL / database sources | Partial | Depends on the connector and environment strategy. |
Fields & controls5 items3110
Fields & controls
5 items
| Feature | Status | Notes |
|---|---|---|
| Attachment controls | Supported | — |
| Choice / option controls | Supported | — |
| Ink / signature patterns | Planned | Usually requires a different Power Apps control strategy. |
| Rich text / formatted content | Partial | Rich-text fidelity can vary and may need manual cleanup. |
| Text, number, date, boolean fields | Supported | — |
Layout5 items3200
Layout
5 items
| Feature | Status | Notes |
|---|---|---|
| Alternate views | Partial | May map to screens, tabs, or conditional containers depending on the design. |
| Multi-section forms | Supported | — |
| Repeating sections / repeating tables | Partial | Usually maps to galleries or collections and may need layout cleanup. |
| Section containers | Supported | — |
| Single-page layout | Supported | — |
Rules & logic6 items3201
Rules & logic
6 items
| Feature | Status | Notes |
|---|---|---|
| Calculated/default values | Partial | Complex formulas may need formula cleanup after import. |
| Conditional formatting | Supported | — |
| Custom code / script | Not available | Requires manual rebuild in Power Fx, Power Apps, or custom components. |
| Required field validation | Supported | — |
| Role-based experiences | Partial | Depends on how identity logic is modeled in the source form. |
| Show / hide logic | Supported | — |
Submit & handoff4 items1300
Submit & handoff
4 items
| Feature | Status | Notes |
|---|---|---|
| Approval-style handoff | Partial | Typically requires follow-on automation or manual app design. |
| Email submit | Partial | Often maps to a connector-driven action rather than a native submit behavior. |
| Multiple submit destinations | Partial | May require explicit branching or follow-on flows. |
| Single submit destination | Supported | — |
How to interpret the statuses
A quick guide to what each status means in practice.
- Supported: Generates a Power Apps package or equivalent structure directly with minimal expected cleanup.
- Partial: Conversion runs, but you should expect manual review for formulas, data connections, or app behavior.
- Planned: Not yet mapped in Form Migrator, but intended for future support.
- Not available: Power Apps does not offer a direct equivalent today, or the pattern requires a custom rebuild approach.
Have a form with unsupported elements?
Send us the package and the compatibility report output. Real form packages help us expand coverage fastest.