Hi Praveen,

I am not entirely sure if there is a practice promoted by Nintex for deployment (other guys in the forum might have a different opinion on this) I guess it all boils down how you would normally do SP deployment across your environments.

I can describe a few steps on how we do it out here, which obviously is in no way exhaustive and any process should be tweaked so that it is repeatable and not add unnecessary steps which don't add any value.

In my case if its a new project I have build all the Lists, libraries, Content Types, Site Columns, Lookup lists etc (i.e. the basic blocks of SP) via a PS scripts and this obviously is version controlled and is passed onto different environments for deployment. Any changes done obviously would be regressed and passed onto the environment again (similar to any code deployment process) For Nintex elements both the forms, workflows (and site workflows) are again exported and passed on between environments and are also version controlled. If there are any manual steps that could go in the release document. (If there are tons of manual steps you might want to automate a few so as to reduce the probability of error during deployment)

If its not a new project you can again export all of your Nintex elements and pass it between environments (and this code could also be version controlled). 

I guess the principles for pushing code between environments would probably always remain the same irrespective of what development tools you use. If you see there are lot of manual steps which is causing most of your errors from the support team then it boils down to automating some of them.

hth.

regards,

Shrini