# InfoPath support ended: replace your forms with a SharePoint list form > For the full documentation index, see https://250highstreet.com/llms.txt > InfoPath is past its Microsoft support date. Replace each InfoPath form with a SharePoint list form, customized in Power Apps if it needs rules. Short answer: InfoPath 2013 is past its Microsoft support date, so rebuild each InfoPath form as a SharePoint list form. A plain list form needs no extra tool. If the form needs rules or a custom layout, customize it in Power Apps. Microsoft's support page also says Microsoft Forms does not replace InfoPath. ## What the dates say Microsoft's lifecycle page shows extended support for InfoPath 2013 ended in July 2026, with the note "Support for Microsoft InfoPath 2013 is extended as shown in order to ensure compatibility with SharePoint Server 2016." Any InfoPath form you still use now runs on an unsupported product, so plan the rebuild now. ## What Microsoft names as the replacements Microsoft's support page "Does Microsoft Forms replace InfoPath?" says: "Microsoft Forms is a basic, lightweight app for quickly collecting information via surveys and quizzes." It says InfoPath is being replaced by other Microsoft products, naming SharePoint Lists, flow and PowerApps. Microsoft's Learn migration page says Power Automate and Power Apps are "the recommended approach for extending lists by SharePoint power users." For forms driven by extensive code, it points to the add-in model and client-side development, which needs developer resources. ## Step 1. List what each InfoPath form does Before you build, write down for each form: 1. The fields, with the type of each: text, number, date, choice, person. 2. Required fields. 3. Rules, such as hiding a field or locking it based on another field. 4. Where the data goes: a list, a library, an email. 5. What happens after it is saved: an approval, a notification. Microsoft's InfoPath assessment scan page warns about three things that need rework: SOAP calls, managed code, and people picker fields. It says people picker fields "need to be updated with the new user's identity" after a move because an on-premises identity does not match the Microsoft 365 identity. If your form used any of these, flag it now. ## Step 2. Build the list with the right columns 1. Create a new list in SharePoint. Name it after the form. 2. Rename the Title column to the main name of the item, such as Request or Task. 3. Add one column per field from Step 1: Single line of text, Number, Date and time, Choice, Person, Yes/No. 4. For Choice columns with an order, number the choices, such as 1 Open, 2 In progress, 3 Closed. 5. Add the required setting on the columns that must be filled. Exact names may differ on your screen. The list gives you a working new item form with no further tools. See "[Make a SharePoint column required based on another](/guides/make-sharepoint-column-required-based-on-another/)" for a rule you can set without Power Apps. ## Step 3. Customize the form if you need more Use Power Apps only when the plain form is not enough. From Microsoft's tutorial: 1. Open the list. 2. On the command bar, select Integrate, then Power Apps, then Customize forms. 3. Power Apps Studio opens with your form on the canvas. If the Welcome dialog opens, select Skip. 4. Change the fields. Microsoft's tutorial shows how to make a field view-only and how to hide a field based on a condition. Cards such as Title are "locked by default" and need to be unlocked first. 5. Save the app. Select Publish to SharePoint, then confirm by selecting Publish to SharePoint again. 6. Open the list and test. Microsoft says: "The version of the custom form that appears in SharePoint is the most recently published version." See "[Power Apps vs list forms](/guides/power-apps-vs-lists-forms/)" and "[Customize SharePoint list form sections](/guides/customize-sharepoint-list-form-sections/)". ## Step 4. Rebuild the after-save steps If the InfoPath form was tied to a workflow, rebuild it in Power Automate. In the list, select Automate, then Power Automate, then Create a flow. Microsoft's Learn page lists examples such as sending an email when a new item is created. If your flow fires on item created or modified and updates the same item, it can trigger itself. Our advice, not a Microsoft rule: add a Yes/No column named "Sent" and set its default value to No; the flow checks it is No, acts, then sets it to Yes. See "[Power Automate flow triggers itself, infinite loop](/guides/power-automate-flow-triggers-itself-infinite-loop/)". ## When Microsoft Forms still fits Microsoft's page limits Forms to surveys and quizzes. If your old form was only a survey that people outside the team fill in once, Forms may fit. To send answers into a list, see "[Microsoft Forms to a SharePoint list](/guides/microsoft-forms-to-sharepoint-list/)". For forms with rules, saved edits or approvals, build a list form instead. ## Choose by number of fields and rules Our advice, not a Microsoft rule: - A few fields and no rules: a plain list form. - A long form in sections, some hidden or locked: Power Apps Customize forms. - A survey with no edits afterward: Microsoft Forms. Test each choice with one real sample item before you retire the old form. ## When to get help You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: \$5,000 for one, built in 2 weeks. See "[What a SharePoint tracker costs to build](/guides/what-a-sharepoint-tracker-costs/)". Bring one example of the problem to a free call. I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything. See trackers I built: [Tools I built](/portfolio/) ## FAQ ### What replaces InfoPath for SharePoint? Microsoft names SharePoint Lists, flow and PowerApps. Its Learn page calls Power Automate and Power Apps the recommended approach for SharePoint power users. ### Does Microsoft Forms replace InfoPath? Microsoft says no. It describes Forms as a basic, lightweight app for surveys and quizzes. ### When does InfoPath 2013 support end? It ended. Microsoft's lifecycle page shows extended support ended in July 2026. ### How do I customize a SharePoint list form without InfoPath? Open the list, select Integrate, then Power Apps, then Customize forms. Save, then select Publish to SharePoint. ### Do InfoPath forms with a people picker move over cleanly? Microsoft's migration scan page says people picker fields need to be updated with the new user's identity, because the on-premises identity does not match the Microsoft 365 identity. ## Sources - [Microsoft Learn, Infopath 2013 Microsoft Lifecycle](https://learn.microsoft.com/en-us/lifecycle/products/infopath-2013) - [Microsoft Support, Does Microsoft Forms replace InfoPath?](https://support.microsoft.com/en-us/forms/does-microsoft-forms-replace-infopath) - [Microsoft Learn, Migrate InfoPath forms to SharePoint](https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/migrate-infopath-forms-to-sharepoint) - [Microsoft Learn, Migration Assessment Scan InfoPath](https://learn.microsoft.com/en-us/sharepointmigration/migration-assessment-scan-infopath) - [Microsoft Learn, Customize a form for a SharePoint list](https://learn.microsoft.com/en-us/sharepoint/dev/business-apps/power-apps/get-started/create-your-first-custom-form) - [Microsoft Support, Automate a list](https://support.microsoft.com/en-US/SharePoint/lists/automate-a-list) ## Related guides - [SharePoint Designer 2013 support ended: what to use for workflows and forms now](/guides/sharepoint-designer-2013-end-of-support-alternative/) - [Power Apps or a SharePoint list form: which one do you need?](/guides/power-apps-vs-lists-forms/) - [New column not showing in the SharePoint list form](/guides/sharepoint-list-new-column-not-showing-in-form/) Source: https://250highstreet.com/guides/infopath-forms-retired-replace-with-sharepoint-list-form/