Updated August 2026

Microsoft InfoPath has been discontinued. InfoPath 2013 reached the end of support on July 14, 2026, and InfoPath Forms Services was removed from SharePoint Online after that date. Microsoft recommends migrating existing InfoPath forms and workflows to supported Microsoft 365 solutions.

If your organization still relies on InfoPath, the important questions are now: What happened to InfoPath? What does the retirement mean for existing forms? And what should you use instead?

The answer depends on how your InfoPath forms are being used. Simple forms may be replaced with modern SharePoint forms or Microsoft Forms. More complex applications may require Power Apps, a third-party InfoPath replacement, or a low-code forms and workflow platform such as NITRO Studio.

This guide explains when InfoPath was discontinued, what happened to InfoPath Forms Services, what the retirement means for existing forms, what replaces InfoPath, and how to choose the right replacement for your organization.

Is InfoPath Discontinued?

Yes. Microsoft InfoPath 2013 reached the end of support on July 14, 2026. InfoPath Forms Services was also removed from SharePoint Online after July 14, 2026. Microsoft recommends migrating existing InfoPath forms and workflows to supported Microsoft 365 solutions.

InfoPath is therefore no longer a supported long-term platform for building and maintaining business forms.

For organizations that still have InfoPath forms in production, the retirement is a signal to move those business processes to a modern forms and workflow platform.

The important distinction is that InfoPath discontinuation does not mean every existing InfoPath form will immediately disappear or stop functioning in every environment. The impact depends on where the forms are hosted.

For SharePoint Online, InfoPath Forms Services was removed after July 14, 2026.

For SharePoint Server Subscription Edition, Microsoft states that InfoPath Forms Services was supported through July 14, 2026. After that date, it is no longer supported. Microsoft recommends exploring alternatives such as Power Apps.

When Was InfoPath Discontinued?

Microsoft InfoPath 2013 reached the end of support on July 14, 2026.

InfoPath Forms Services in SharePoint Online was also removed after July 14, 2026.

The retirement was the end of a long transition away from InfoPath. Microsoft had previously announced that InfoPath 2013 would be the final release of the product and had encouraged organizations to move to newer technologies.

The July 14, 2026 date is therefore an important milestone for organizations with legacy InfoPath applications.

InfoPath Retirement Timeline

Date What happened
2013 Microsoft released InfoPath 2013, the final version of InfoPath
2023 Microsoft announced the retirement of InfoPath Forms Services in SharePoint Online
May 18, 2026 Microsoft began blocking the publishing of new or updated InfoPath forms in SharePoint Online
July 14, 2026 InfoPath 2013 reached the end of support
July 14, 2026 InfoPath Forms Services reached the end of support in SharePoint Server Subscription Edition
After July 14, 2026 InfoPath Forms Services was removed from SharePoint Online

What Happened to InfoPath?

InfoPath was Microsoft’s forms technology for creating structured forms that could collect and manage business information, particularly in SharePoint environments.

Organizations used InfoPath for processes such as:

  • Employee requests
  • Purchase requests
  • Expense reports
  • IT requests
  • Approval forms
  • HR processes
  • Compliance forms
  • Document workflows
  • Departmental requests
  • Business process applications

Over time, many organizations built large collections of InfoPath forms that became tightly connected to SharePoint lists, libraries, workflows, data sources, and business processes.

Microsoft eventually moved away from InfoPath and toward newer technologies such as Power Apps and Power Automate.

Because many organizations still depend on legacy InfoPath applications, the end of support creates a modernization requirement.

The challenge is that an InfoPath application is often more than a form.

A single InfoPath solution may contain:

  • Form fields
  • Business rules
  • Conditional formatting
  • Calculations
  • Data connections
  • Lookups
  • Repeating sections
  • Attachments
  • Multiple views
  • Permissions
  • Approvals
  • Notifications
  • Workflows
  • External integrations
  • Custom code

That is why replacing InfoPath requires more planning than simply creating a new form.

What Does InfoPath Discontinuation Mean for Existing Forms?

The impact of InfoPath’s retirement depends on the environment in which the forms are running.

InfoPath in SharePoint Online

InfoPath Forms Services was removed from SharePoint Online after July 14, 2026.

Organizations using InfoPath Forms Services in SharePoint Online should therefore migrate those forms and associated business processes to supported solutions.

InfoPath in SharePoint Server

InfoPath Forms Services was deprecated in SharePoint Server Subscription Edition and remained supported through July 14, 2026. Microsoft recommends that organizations begin exploring alternatives.

After the support date, continuing to rely on InfoPath creates a long-term supportability risk because Microsoft is no longer providing support for the technology.

This does not necessarily mean every existing form will stop functioning immediately in every SharePoint Server environment. However, unsupported legacy technology becomes increasingly difficult to maintain as the surrounding Microsoft environment changes.

Can You Still Use InfoPath After July 14, 2026?

InfoPath is no longer a supported technology after July 14, 2026.

The exact behavior of existing forms depends on the environment.

For SharePoint Online, InfoPath Forms Services was removed after the retirement date.

For SharePoint Server Subscription Edition, Microsoft states that InfoPath Forms Services is no longer supported after July 14, 2026.

Organizations should therefore avoid treating InfoPath as a long-term solution for business-critical processes.

If an organization needs additional time to migrate a complex application, it should assess the risks of continuing to operate the unsupported technology while developing a migration plan.

The goal should be to move critical business processes to a supported platform rather than waiting for an unsupported InfoPath application to become a business disruption.

What Replaces InfoPath?

There is no single InfoPath replacement that is right for every organization or every form.

The right replacement depends on the complexity of the form, the workflows behind it, the organization’s Microsoft 365 environment, licensing requirements, development resources, and long-term maintenance strategy.

Common InfoPath alternatives include:

  • Power Apps
  • SharePoint forms
  • Microsoft Forms
  • NITRO Studio
  • Custom applications

Each option has different strengths.

Power Apps

Power Apps is Microsoft’s primary low-code application platform and can be used to recreate many types of InfoPath forms and business applications.

It can be a strong choice for organizations that already have Power Platform expertise and want to build applications using Microsoft’s broader Power Platform ecosystem.

However, organizations should evaluate development requirements, licensing, governance, and ongoing maintenance before choosing Power Apps for a large InfoPath replacement project.

SharePoint Forms

Modern SharePoint forms can be appropriate for relatively simple SharePoint list scenarios.

If an InfoPath form primarily collects and displays basic SharePoint list information, a modern SharePoint form may provide enough functionality.

More complex InfoPath applications may require additional capabilities for business rules, workflow automation, integrations, and advanced user experiences.

Microsoft Forms

Microsoft Forms is useful for surveys, quizzes, and straightforward information collection.

However, Microsoft Forms is not a direct replacement for complex InfoPath applications.

InfoPath was designed to support more sophisticated business forms and processes, including integration with SharePoint and workflow scenarios.

NITRO Studio

NITRO Studio is a low-code forms and workflow automation platform designed for Microsoft 365, SharePoint, and Teams environments.

It can be used to build modern forms and automate the business processes behind them.

For organizations replacing InfoPath, NITRO Studio can provide a way to recreate forms while also modernizing associated workflows, approvals, notifications, and business rules.

InfoPath Replacement Comparison

InfoPath alternative Best for Key considerations
Power Apps Organizations invested in Microsoft Power Platform Development, licensing, governance, and maintenance requirements
SharePoint Forms Simple SharePoint list forms Limited compared with complex InfoPath applications
Microsoft Forms Surveys and simple information collection Not designed as a full replacement for complex InfoPath applications
NITRO Studio Microsoft 365 and SharePoint organizations needing forms and workflow automation Low-code forms, workflows, approvals, and business process automation
Custom application Highly specialized applications Greater development and maintenance requirements

The best choice depends on the requirements of the individual application.

Organizations with dozens or hundreds of InfoPath forms may also find that different forms require different replacement strategies.

A simple survey may not need the same platform as a complex approval application.

What Is the Best InfoPath Replacement?

The best InfoPath replacement depends on what your existing forms actually do.

If you have simple forms with limited business logic, Microsoft Forms or SharePoint forms may be sufficient.

If you need more sophisticated business applications and already have Power Platform expertise, Power Apps may be a good choice.

If your organization has complex SharePoint-based forms and workflows and wants a low-code approach that stays closely connected to Microsoft 365 and SharePoint, NITRO Studio is another option.

The most important consideration is not simply whether a platform can recreate the visible form.

The replacement should support the entire business process, including:

  • Data
  • Business rules
  • Workflows
  • Approvals
  • Notifications
  • Permissions
  • Integrations
  • Reporting
  • User experience
  • Ongoing maintenance

What Happens to Existing InfoPath Data?

Replacing an InfoPath form does not necessarily mean replacing or abandoning the data stored by the existing application.

During an InfoPath replacement project, organizations should determine:

  • Where existing form data is stored
  • Which historical records need to remain accessible
  • Whether data needs to be migrated
  • Whether existing SharePoint lists can continue to be used
  • Whether attachments need to be preserved
  • How users will access historical records
  • How long records must be retained
  • Whether compliance requirements apply

In many cases, the existing SharePoint data can remain in place while a new form and workflow solution is built around it.

This can reduce migration complexity and help organizations preserve historical information while modernizing the user experience and business process.

Does Replacing InfoPath Mean Rebuilding Everything?

Not necessarily.

A successful InfoPath replacement should begin with an assessment of what each form actually does.

Some forms may be obsolete and can simply be retired.

Some may be simple enough to recreate quickly using a modern form.

Others may contain complex business logic and workflows that need to be rebuilt more carefully.

This is why organizations should avoid assuming that every InfoPath form needs to be recreated exactly as it exists today.

Instead, evaluate each application and ask:

  1. Is the form still needed?
  2. Is the current business process still correct?
  3. Which functionality must be preserved?
  4. Which functionality can be simplified?
  5. What data must be retained?
  6. What workflows and approvals are required?
  7. Which replacement platform best fits the requirements?

This approach can reduce unnecessary work while creating a better long-term solution.

How to Replace InfoPath

Replacing InfoPath should start with an inventory of your existing forms.

1. Catalog your InfoPath forms

Identify every InfoPath form currently in use and document its owner, purpose, users, data, workflows, integrations, and business importance.

2. Eliminate unnecessary forms

Some legacy forms may no longer be needed.

Retiring obsolete forms before beginning a rebuild can significantly reduce the scope of the project.

3. Assess form complexity

Identify simple forms versus applications that contain extensive business rules, workflows, data connections, and integrations.

4. Evaluate replacement options

Consider Power Apps, SharePoint forms, Microsoft Forms, NITRO Studio, and custom development based on the requirements of each application.

5. Rebuild the forms and workflows

Recreate the required functionality in the selected platform.

6. Test with users

Have actual users test the new application and identify missing requirements or process improvements.

7. Deploy and decommission the legacy solution

Once the replacement is working correctly, move users to the new solution and establish a plan for the legacy InfoPath application and historical data.

InfoPath Replacement Does Not Have to Mean Leaving SharePoint

For organizations that have invested heavily in SharePoint, replacing InfoPath does not necessarily require abandoning SharePoint.

Many InfoPath applications use SharePoint lists, libraries, permissions, and data as the foundation for the business process.

A replacement solution can continue to use that Microsoft 365 and SharePoint environment while modernizing the forms and workflows on top of it.

This can be particularly valuable when an organization has a large investment in SharePoint and wants to modernize its forms without moving business data into an entirely separate system.

Why Organizations Are Moving From InfoPath to NITRO Studio

For organizations looking for an InfoPath replacement that works within Microsoft 365 and SharePoint, NITRO Studio provides low-code tools for creating forms and automating business processes.

NITRO Studio can support:

  • Modern forms
  • SharePoint integration
  • Business rules
  • Workflow automation
  • Approvals
  • Notifications
  • Data management
  • Microsoft Teams integration
  • Custom actions
  • Reporting and dashboards

This can allow organizations to modernize InfoPath applications while maintaining a strong connection to the Microsoft ecosystem.

Rather than treating the project as simply replacing an old form, organizations can use the transition to improve the underlying business process.

InfoPath Discontinued: What Should You Do Now?

If your organization still relies on InfoPath, the July 14, 2026 end-of-support date should be treated as a reason to move forward with modernization.

Start by determining:

  • Which InfoPath forms are still being used
  • Which forms are business critical
  • Which forms can be retired
  • Which workflows depend on InfoPath
  • Where the underlying data is stored
  • Which integrations need to be preserved
  • Which forms are simple enough for a basic replacement
  • Which applications require a more sophisticated platform

Then create a migration plan based on business impact and technical complexity.

You do not necessarily need to replace every InfoPath form with the same technology.

The best approach is to match each business process with the platform that can support its requirements while providing a sustainable path forward.

Frequently Asked Questions About InfoPath Discontinued

Is InfoPath discontinued?

Yes. InfoPath 2013 reached the end of support on July 14, 2026, and InfoPath Forms Services was removed from SharePoint Online after that date. Microsoft recommends migrating existing InfoPath forms and workflows to supported Microsoft 365 solutions.

When did InfoPath end of life?

InfoPath 2013 reached the end of support on July 14, 2026. InfoPath Forms Services also reached the end of support in SharePoint Server Subscription Edition on July 14, 2026, while InfoPath Forms Services was removed from SharePoint Online after that date.

What happened to InfoPath Forms Services?

InfoPath Forms Services was removed from SharePoint Online after July 14, 2026. Microsoft also ended support for InfoPath Forms Services in SharePoint Server Subscription Edition on July 14, 2026.

Can I still use InfoPath?

InfoPath is no longer a supported technology after July 14, 2026. The exact behavior of existing forms depends on the environment, but organizations should not treat InfoPath as a long-term supported platform for business-critical applications.

What replaces InfoPath?

There is no single replacement for every InfoPath application. Options include Power Apps, SharePoint forms, Microsoft Forms for simple information collection, NITRO Studio, and custom applications. The appropriate replacement depends on the complexity and requirements of the existing form and business process.

Is Power Apps the replacement for InfoPath?

Power Apps is one of Microsoft’s recommended modern options for replacing InfoPath forms, particularly for organizations already using Power Platform. However, it is not an automatic conversion tool, and organizations should evaluate licensing, development, governance, and maintenance requirements before selecting it.

Does Microsoft Forms replace InfoPath?

No. Microsoft Forms is not a direct replacement for complex InfoPath applications. Microsoft Forms is primarily designed for surveys, quizzes, and straightforward information collection. Complex InfoPath applications may require Power Apps, SharePoint forms, NITRO Studio, or another solution.

Is there a tool to automatically convert InfoPath forms?

No. There is no universal one-click Microsoft tool that automatically converts an existing InfoPath form and all of its associated business logic and workflows into a complete modern replacement. Organizations generally need to assess the existing application and rebuild its required functionality in the selected platform.

What happens to existing InfoPath forms?

The impact depends on the environment. InfoPath Forms Services was removed from SharePoint Online after July 14, 2026. InfoPath Forms Services in SharePoint Server Subscription Edition is no longer supported after July 14, 2026. Organizations should assess their existing forms and plan migration to a supported solution.

How do I replace InfoPath?

Start by cataloging your existing InfoPath forms and evaluating their business purpose, data, rules, workflows, integrations, and complexity. Retire forms that are no longer needed, select a replacement platform for the remaining forms, rebuild and test the required functionality, and then move users to the new solution.

Ready to Replace InfoPath?

The end of InfoPath support does not have to mean rebuilding your business processes from scratch.

The first step is understanding what you have today and determining which forms and workflows your organization actually needs to preserve.

NITRO Studio provides a low-code approach to building modern forms and workflows within Microsoft 365, SharePoint, and Teams.

If you are planning an InfoPath replacement project, evaluate your existing forms, identify your most critical applications, and create a migration plan based on complexity and business impact.

Request more info here:

Privacy Notice:
By submitting this form, you consent to Crow Canyon Software collecting and processing your personal information to respond to your inquiry. Do not include sensitive health or personal data unless specifically requested.