Hi Joshua,

There's an article here Is there a way to deploy a Nintex Form from a script (like powershell or feature) instead of a Export/Import?  that may help you.

Jan

Hi Joshua Moore​,

Did you find a solution to your problem ?

I am searching for a solution every 6 months hoping that Nintex or someone would find a breathrough or at least workaround.

For now my solution is : NOT to use Nintex Forms or Workflows in every site collections/sites/sub-sites but instead have a "central site" where users use the forms and a workflow in the list that copies the item values into the "correct" target site/sub-site. Then I have a regular purge of the submitted items.

This way I only have 1 central place to maintain all my forms and the business can change them if needed.

The downside of course is that the items once in the target site(s) lost their CreatedBy since it's the name of the workflow author, and a form with lots of repeated sections are just showing as plain XML but at least the data is there so we can do reports on it.

This solution is only valid IF users do not need to modify the data, otherwise they will not be so happy to open it in the out-of-the-box SharePoint item form UI.

Would love to hear others with their workarounds on updating 50+ forms in sites.

thanks.

François.

There is now a Forms API as documented in the SDK Web Service Reference 

This allows 

Endpoint URL

DeleteForm

GetFormXml

PublishFormXml

Example 

Migrate Forms with the Nintex Forms Web Service API