White Papers

Perspective on the paths to migrating InfoPath Forms to Microsoft 365 Power Apps

Perspective on the paths to migrating InfoPath Forms to Microsoft 365 Power Apps

In preparation for what will ultimately become an unsupported platform, thoughts of “what to do next?” will be a prevailing theme for consumers of Microsoft InfoPath forms. To this effect, SharePoint 2019, though InfoPath is included, it is considered a deprecated feature by Microsoft. The main difference between a deprecated feature and a removed feature is that Microsoft no longer continue investing in this feature and users are, in essence, discouraged from widespread utilization, as sustained backward compatibility will become an issue.

Once Microsoft deems a feature deprecated, it is clearly not going to be supported long term and will ultimately be removed from its feature set going forward. In the case of InfoPath, it has been widely publicized that it is well on its way to becoming a removed feature. What does this mean for InfoPath consumers?  It means that, though there is no need to panic and immediately move away from InfoPath, Microsoft has given InfoPath users ample warning that this feature is going away and organizations that rely upon it should begin the migration planning process sooner rather than later. To better understand the landscape, we should first understand the use of InfoPath in general.  Typically, there are two sets of equally relevant issues:

  • Completed forms - What to do with the existing repository of completed forms
  • Template itself - What to do going forward if InfoPath use is to continue

Within these two set of issues, there are bound to be varying types of scenarios in which an organization finds itself. Please note that this is not to imply an organization will experience one of these scenarios, but in fact, it is most likely to have a combination of these sets of conditions:

  • We have a set of old forms (completed docs) but the form itself is no longer in use
  • We are still using some InfoPath forms but about to end use of these forms
  • We have a set of completed forms and need to continue to use this form in the future
  • We need new forms and need to create something very soon

Of the scenarios above, option 4 would not include InfoPath per Microsoft’s product recommendation. Creation of new forms should be created in PowerApps, though there are still inherent issues/limitations. The real issue, however, centers on scenarios 1-3. This whitepaper aims to give some perspective on how to potentially address the complications of the migration from InfoPath to Power Apps.  There are options and processes in place that can create positive outcomes for organizations looking to get a jump on migrating away from InfoPath to Microsoft 365 Power Apps Platform. 

More »