Nintex to Power Automate migration
Sign up / Sign in
Getting started

How to complete Required settings correctly

Required settings are there to close the gap between what the source export can tell us automatically and what the destination flow package still needs to import cleanly. If export says required settings are incomplete, the fix is usually to align the visible rows with the exact workflow references, not to guess at random URLs.

8 min readUpdated Apr 3, 2026required settingssharepointexport
Quick answer
In shortFill the required fields in the right order so export does not fail later on missing SharePoint or task configuration.
Most likely causeThe easiest way to work through Required settings is to start at the missing list and clear one requirement family at a time. Trigger behavior, SharePoint site URLs, and workflow task handling are separate decisions and should not be blended together mentally.
What to do nextUse this article while you move through Upload, Analyze, Required settings, and Export.

Treat the page as a checklist, not a form dump

The easiest way to work through Required settings is to start at the missing list and clear one requirement family at a time. Trigger behavior, SharePoint site URLs, and workflow task handling are separate decisions and should not be blended together mentally.

If the page says everything is complete but export still complains, re-run analysis after any parser or reference-matching fix. Required Settings is populated from the analyzed run, so stale analysis can preserve stale assumptions.

  • Complete trigger behavior first if the workflow depends on a mapped trigger template.
  • Fill SharePoint site URLs with the site root, not the full list view URL.
  • Choose the workflow task strategy intentionally instead of accepting a default you do not understand.

Use the exact SharePoint site that owns the list or library

A common mistake is to paste a list settings URL or a direct item URL when the product is asking for the site URL. The converter needs the site root so it can build stable list and library references in the destination package.

If a list name appears with a slightly different suffix than you expected, keep the site URL aligned to the real SharePoint site and let the exporter match the canonical list name during packaging.

Example: use https://contoso.sharepoint.com/sites/operations, not .../Lists/Order%20Workflow%20Tasks/AllItems.aspx

Re-analyze after structural fixes

If a workflow previously surfaced the wrong list names, duplicate SharePoint rows, or stale task placeholders, the safest path is to re-analyze after applying the fix. Export validation and the visible Required settings page need to agree on the same reference set.

Once the rows look correct and remain in stable workflow order, export should stop failing on hidden or mismatched references.

  1. Apply the latest parser or reference-matching fixes if relevant.
  2. Re-analyze the workflow to refresh visible references.
  3. Confirm the missing list at the top of the page disappears as you fill the correct site URL.
  4. Export again only after the required banner is clear.

Related articles

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

SharePoint & document patterns6 min read • Updated Apr 3, 2026

How to set SharePoint site URLs in Required settings

Use site roots, keep rows in workflow order, and fix mismatched reference names before export.

sharepointrequired settings
Export & import6 min read • Updated Apr 3, 2026

How to fix 'Required settings incomplete' export errors

If export still says a list or library is missing, the problem is usually stale analysis data or reference-name mismatch, not the idea of the site URL itself.

required settingsexport error
Export & import7 min read • Updated Apr 3, 2026

How to generate and import your first package

Use Analyze and Required settings to reduce surprises, then validate the imported package in Power Automate before calling the migration done.

exportimport