What Form Migrator reads from Nintex Forms
Controls and SharePoint bindings
Inventory labels, text inputs, choices, lookups, people fields, dates, buttons, attachments, calculated controls, and the SharePoint internal fields they use.
Classic and responsive layout metadata
Read fixed-position coordinates for classic forms and responsive column or section metadata for responsive forms so the generated app starts with source-aware placement.
Rules, formulas, and references
Identify visibility, disabling, validation, set-value, and calculated-value logic, along with stale control references and tenant-specific resources that require review.
A practical Nintex Forms migration workflow
Upload XML or a ZIP portfolio
Upload one exported Nintex Forms XML definition or a ZIP containing multiple forms. The portfolio analyzer inventories every detected form.
Review and select a form
Compare readiness, controls, SharePoint bindings, rules, formulas, references, and warnings, then choose the form to continue with.
Validate the SharePoint schema
Connect Microsoft 365, select the real SharePoint list or library, and compare Nintex internal field names with the destination columns before generation.
Generate and test the .msapp
Download the first-pass Power Apps package, repair or select its SharePoint connection, and validate layout, formulas, defaults, and save behavior in Power Apps Studio.
Controls that map well
Standard inputs
Text, multiline text, number, currency, date, Yes/No, labels, panels, separators, HTML, images, and standard buttons have practical Power Apps equivalents.
Choice and lookup controls
Single-select Nintex dropdowns can remain non-searchable Power Apps Dropdown controls, while people fields and multi-select sources use record-aware ComboBoxes.
SharePoint form behavior
Required fields, existing record loading, standard save/cancel behavior, and supported document-library metadata can be scaffolded against the validated SharePoint target.
What still needs builder review
- Repeater controls usually need a gallery plus a collection, child list, related table, or another persistence design.
- Custom JavaScript cannot be copied directly into a canvas app and must be recreated with Power Fx, Power Automate, connectors, or a manual app pattern.
- Complex cascading lookups, group-membership checks, user-profile lookups, and environment-specific URLs or list IDs require destination-specific validation.
- Orphaned rule targets, custom CSS, and pixel-perfect layout expectations are reported rather than silently discarded.
What the generated package includes
Compatibility analysis
A structured inventory of forms, controls, bindings, rules, references, warnings, and readiness classifications.
Normalized field and control mapping
A selected-form model that preserves field names, source control presentation, layout intent, required state, and supported rule scaffolds.
First-pass Power Apps package
An importable .msapp package when the selected form reaches an exportable state, plus builder guidance for items that still need manual work.
Common questions
What Nintex Forms file should I upload?
Upload an exported Nintex Forms XML definition for one form, or a ZIP portfolio containing multiple exported XML definitions. Form Migrator identifies the forms by their Nintex Forms XML structure rather than by file name alone.
Does Form Migrator support classic and responsive Nintex Forms?
Yes. Both classic and responsive exports can be analyzed. The generator preserves classic coordinates or responsive section metadata as a first pass, but the final layout should still be validated in Power Apps Studio.
Which Nintex Forms product is this built for?
The current beta is built for exported Nintex Forms for SharePoint XML definitions and ZIP portfolios. It is not presented as a converter for Nintex Automation Cloud forms.
Does this migrate Nintex workflows too?
No. Form Migrator focuses on the form experience. Workflow and approval modernization belongs in Power Automate; Horton Scientific's Flow Migrator product addresses Nintex workflow analysis and migration separately.
Does Form Migrator publish the app automatically?
No. It generates a first-pass .msapp package when supported. A maker must import it, reconnect data sources, test the behavior, and publish it through the customer's Power Platform process.
Do I need access to the SharePoint list or library?
For reliable generation, yes. The Nintex export provides field bindings, but live Microsoft 365 discovery is used to validate the actual SharePoint target, column types, choices, lookups, and internal names.