Example patterns
Administrative action list form
A SharePoint list-backed form with dropdowns, checkboxes, approval fields, and secondary user-role lists.
Multi-view library form
An InfoPath form-library template where each view should become a screen and buttons or images need layout review.
Responsive Nintex form
A Nintex Forms export where responsive sections, dropdown presentation, rules, and SharePoint field bindings drive the first-pass app layout.
Application dashboard form
A single-view form with large visual sections controlled by show/hide rules, best treated as virtual screens.
What to compare
- How many views or major sections the source form has.
- Whether controls are bound to the primary SharePoint target or secondary lists.
- Whether dropdowns use static choices, list-backed values, or filters.
- Whether buttons only navigate or also set values, submit, or close the form.
How to use these examples
Run your own InfoPath .xsn or Nintex Forms XML/ZIP analysis, then compare the results to these patterns. If the form resembles one of the complex examples, reserve extra time for builder validation and user acceptance testing.
Common questions
Are these exact customer forms?
No. They are representative migration patterns drawn from common InfoPath and Nintex Forms structures and testing scenarios.
Can I submit my form as an example?
Yes. Contact support if you want help reviewing a compatibility gap or anonymized sample.
Which example is the best fit?
Start with the one that matches your form structure: list form, form library, multi-view approval, or single-view show/hide.