Supported8 min readUpdated June 5, 2026

Prepare SharePoint lists and libraries before export

Create or confirm the primary list/library, supporting lookup lists, required columns, and sample data before generating the app.

Quick answer

In short

Form Migrator works best when the destination SharePoint list or library already exists with the columns the new Power Apps form will save to.

Most likely cause

Dropdowns and form saves fail most often because a supporting lookup list is missing, empty, or has different column names than the original InfoPath data connection expected.

What to do next

Create the primary target first, then create supporting lists, then use Microsoft 365 discovery to load the real inventory into Required Settings.

Minimum SharePoint setup

  • Primary list or library for the generated form.
  • Columns for every field that should be saved.
  • Supporting lists used by dropdowns, people/role lists, statuses, states, categories, or other lookup values.
  • Sample rows in lookup lists so dropdowns can open during testing.
  • Permissions that allow the connected Microsoft 365 user to read list metadata and rows.

When a script helps

For test migrations, a non-PnP Microsoft Graph PowerShell script can create the lists, libraries, columns, and sample data inferred from an XSN. Treat generated scripts as a test scaffold; production environments should still review column types, required settings, permissions, and real lookup values.

Do not skip sample data

A generated dropdown can be correctly wired and still look broken when the supporting SharePoint list is empty. Add at least one test row to each lookup list so users can confirm the dropdown opens and saves the expected value.

Keep reading the next most relevant guides for this form pattern.