SOLVED
Home

InfoPath replacement in SharePoint 2016

%3CLINGO-SUB%20id%3D%22lingo-sub-239714%22%20slang%3D%22en-US%22%3EInfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239714%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20in%20process%20of%20migration%20from%20SharePoint%202010%20to%20SharePoint%202016.%20In%20our%20environment%20we%20have%20a%20lot%20of%20InfoPath%20forms.%20I%20know%20we%20can%20migrate%20the%20InfoPath%20forms%20from%20SharePoint%202010%20to%20SharePoint%202013%20and%20then%20to%202016.%20Given%20that%20InfoPath%20will%20be%20deprecated%2C%20we%20don't%20want%20users%20to%20create%20more%20InfoPath%20forms%20as%20this%20will%20be%20difficult%20for%20any%20future%20migrations.%20Are%20there%20any%20alternative%20in%20SharePoint%202016%20from%20Microsoft%20for%20InfoPath%20forms%3F%20We%20would%20avoid%20using%20third%20party%20tools.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20your%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-239714%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Einfopath%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Designer%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240105%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240105%22%20slang%3D%22en-US%22%3E%3CP%3ECorrect%2C%20InfoPath%202019%20still%20supports%202019%20as%20part%20of%20the%20Microsoft's%20commitment%20to%20support%20that%20technology%20until%202026%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240090%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240090%22%20slang%3D%22en-US%22%3EThanks%20for%20your%20response.%20I%20know%20that%20PowerApps%20and%20Flow%20are%20replacing%20the%20Infopath%20and%20SharePoint%20designer.%20We%20are%20in%20process%20of%20adopting%20SP%202016.%20I%20know%20SP2019%20is%20still%20in%20Preview%20and%20it%20might%20take%20sometime%20to%20get%20it%20stable.%20SP2019%20is%20out%20of%20question%20as%20of%20now.%20Does%20SP%202019%20supports%20InfoPath%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-240078%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-240078%22%20slang%3D%22en-US%22%3ELooks%20like%20Custom%20development%20is%20the%20only%20option.%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3EThanks%20for%20your%20response%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239928%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239928%22%20slang%3D%22en-US%22%3EWell%2C%20I%20woul%20say%20that%20you%20can%20use%20PowerApps%20with%20SP%202019%20in%20the%20same%20way%20you%20can%20do%20with%20SP%202016%20Today....PowerApps%20is%20still%20a%20cloud%20service%20so%20what%20you%20can%20just%20do%20is%20consume%20SP%20OnPrem%20from%20your%20PowerApp%20and%20you%20could%20have%20SP%202016%20or%20SP%202019%20behind%20the%20gateway%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239923%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239923%22%20slang%3D%22en-US%22%3E%3CP%3ERishi...something%20to%20consider%20is%20SharePoint%202019%20will%20support%20PowerApps%20and%20Flow%20(InfoPath%20as%20well).%26nbsp%3B%20This%20would%20be%20a%20great%20replacement%20for%20the%20InfoPath%20forms%20you%20have%20developed%20so%20far%20and%20a%20good%20going%20forward%20strategy.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FAnnouncing-Availability-of-SharePoint-Server-2019-Preview%2Fba-p%2F214427%26nbsp%3B%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-SharePoint-Blog%2FAnnouncing-Availability-of-SharePoint-Server-2019-Preview%2Fba-p%2F214427%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESteve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239763%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239763%22%20slang%3D%22en-US%22%3EDon%E2%80%99t%20forget%20there%20is%20a%20cloud%20based%20replacement%20for%20InfoPath%20using%20Microsoft%20Flow%20and%20PowerApps.%20This%20may%20not%20be%20suitable%20for%20your%20organisation%2C%20unless%20you%20consider%20hybrid%2C%20but%20for%20other%20Community%20users%20this%20is%20definitely%20the%20route%20if%20heading%20to%20the%20cloud...Good%20luck%20and%20watch%20out%20for%20SharePoint%20Server%202019%20(now%20in%20preview)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239759%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239759%22%20slang%3D%22en-US%22%3ENo%20replacement%20provided%20by%20Microsoft%20so%20your%20chances%20here%20are%3A%3CBR%20%2F%3E(1)%20Custom%20Development%20if%20this%20is%20something%20feasible%20for%20your%20company.%3CBR%20%2F%3E(2)%20Third%20party%20tool%20that%20you%20mention%20you%20want%20to%20avoid%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-680055%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-680055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16525%22%20target%3D%22_blank%22%3E%40Rishi%20Gupta%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20know%20you%20mentioned%20no%20third%20party%20tools.%20But%20I'd%20recommend%20taking%20a%20look%20at%20ClaySys%20AppForms.%20As%20you%20said%2C%20it's%20better%20to%20move%20away%20from%20Infopath%20even%20though%20Microsoft%20will%20continue%20supporting%20it%20for%20a%20few%20more%20years.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20600px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F117613iA64C6220F629A13C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22appform1.gif%22%20title%3D%22appform1.gif%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20has%20presented%20PowerApps%20as%20a%20replacement%20for%20InfoPath%2C%20but%20we%20know%20that%20it's%20not%20an%20advanced%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%3A%20AppForms%20supports%20SP%202016%2C%202019%20%26amp%3B%20Office%20365%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheck%20this%20out%20if%20you%20are%20interested%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.claysys.com%2Fappforms%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.claysys.com%2Fappforms%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783721%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783721%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16525%22%20target%3D%22_blank%22%3E%40Rishi%20Gupta%3C%2FA%3E%26nbsp%3BIt%20seems%20that%20Microsoft%20will%20continue%20to%20support%20InfoPath%20Forms%20Services%20in%20Sharepoint%20Server%202016%20(as%20well%20as%20Sharepoint%20365)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-833832%22%20slang%3D%22en-US%22%3ERe%3A%20InfoPath%20replacement%20in%20SharePoint%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-833832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16525%22%20target%3D%22_blank%22%3E%40Rishi%20Gupta%3C%2FA%3Eback%20in%20the%20time%20when%20this%20question%20was%20asked%2C%20there%20were%20no%20options%2C%20but%20now%20we%20have%20Microsoft%20Forms%20which%20will%20come%20in%20handy%2C%20but%20if%20you%20have%20some%20custom%20rules%20in%20Infopath%20form%2C%20then%20you'll%20only%20be%20able%20to%20replace%20it%20with%20third%20party%20apps%20like%20Nintex%20Forms%20(try%20the%20new%20responsive%20designer%2C%20its%20amazing)%20or%20another%20less%20expensive%20solution%20would%20be%20Infowise%20Forms.%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E
Rishi Gupta
Contributor

We are in process of migration from SharePoint 2010 to SharePoint 2016. In our environment we have a lot of InfoPath forms. I know we can migrate the InfoPath forms from SharePoint 2010 to SharePoint 2013 and then to 2016. Given that InfoPath will be deprecated, we don't want users to create more InfoPath forms as this will be difficult for any future migrations. Are there any alternative in SharePoint 2016 from Microsoft for InfoPath forms? We would avoid using third party tools. 

 

Thanks in advance for your help!

10 Replies
No replacement provided by Microsoft so your chances here are:
(1) Custom Development if this is something feasible for your company.
(2) Third party tool that you mention you want to avoid
Don’t forget there is a cloud based replacement for InfoPath using Microsoft Flow and PowerApps. This may not be suitable for your organisation, unless you consider hybrid, but for other Community users this is definitely the route if heading to the cloud...Good luck and watch out for SharePoint Server 2019 (now in preview)

Rishi...something to consider is SharePoint 2019 will support PowerApps and Flow (InfoPath as well).  This would be a great replacement for the InfoPath forms you have developed so far and a good going forward strategy.

 

https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/Announcing-Availability-of-SharePoi...

 

Steve

Well, I woul say that you can use PowerApps with SP 2019 in the same way you can do with SP 2016 Today....PowerApps is still a cloud service so what you can just do is consume SP OnPrem from your PowerApp and you could have SP 2016 or SP 2019 behind the gateway
Looks like Custom development is the only option. :)
Thanks for your response
Thanks for your response. I know that PowerApps and Flow are replacing the Infopath and SharePoint designer. We are in process of adopting SP 2016. I know SP2019 is still in Preview and it might take sometime to get it stable. SP2019 is out of question as of now. Does SP 2019 supports InfoPath?
Solution

Correct, InfoPath 2019 still supports 2019 as part of the Microsoft's commitment to support that technology until 2026

@Rishi Gupta 

 

I know you mentioned no third party tools. But I'd recommend taking a look at ClaySys AppForms. As you said, it's better to move away from Infopath even though Microsoft will continue supporting it for a few more years.

 

appform1.gif

 

Microsoft has presented PowerApps as a replacement for InfoPath, but we know that it's not an advanced solution.

 

PS: AppForms supports SP 2016, 2019 & Office 365

 

Check this out if you are interested: https://www.claysys.com/appforms/

@Rishi Gupta It seems that Microsoft will continue to support InfoPath Forms Services in Sharepoint Server 2016 (as well as Sharepoint 365)

Highlighted

@Rishi Guptaback in the time when this question was asked, there were no options, but now we have Microsoft Forms which will come in handy, but if you have some custom rules in Infopath form, then you'll only be able to replace it with third party apps like Nintex Forms (try the new responsive designer, its amazing) or another less expensive solution would be Infowise Forms. Thanks

Related Conversations
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
30 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies