Info-path forms and SharePoint Designer Workflow Conversion to Nintex Forms and Workflows

In this blog post, we discuss best practices for converting Info-path forms to Nintex form and SharePoint Designer workflows to Nintex Workflows. This approach can be applied to any sort of software conversion, software rewrite, or software upgrade.

  1. Write PowerShell Scripts to get the inventory of info-path forms, and SharePoint Designer workflows with associated metadata which may include number and type of UI controls or actions.
  2. Develop a SharePoint Site to Manage the waves of conversions. The site manages the day-to-day tasks of the conversion process such as Assignment for Conversion, Status of the conversion, and a form to track issues on the conversion. It can include workflows to notify end users about the status of their sites.
  3. Create a staging environment for the conversion. This environment is used to convert the Info-path forms and designer workflows; one site collection per wave of conversion is sufficient.
  4. Copy the List/Libraries to the staging environment.
  5. Determine the complexity of the form and workflows. The Info-path form complexity is determined by the number of UI Controls and the weight of the Control Types. For example, a form having 1-6 UI controls is simple, 7-12 is medium, more than 13 is complex. Complexity of designer workflows is determined by the number and type of actions in the workflow.
  6. Prioritize Info-path forms and designer workflows inventory into waves. Duration of a wave is typically 2 weeks. Within these 2 weeks development and testing by the development team is completed. The wave will be handed over to end users for validation, which can last up-to 2 weeks.
  7. Assign conversion tasks to development teams. Each developer in the conversion team picks and assigns several forms/workflows for each wave.
  8. The conversion (development) team maintains the status of each form and workflow conversions.
  9. Send automated workflow notification to end users. After development and testing is completed by the conversion team, the status of the form and workflows is set to “Ready for validation” which sends notification to end users for validation.
  10. End users log any defects during validation to a defect tracker. The defect will automatically be routed to the developer that was assigned to work on the conversion.

The above 10 step approach is based on my personal experience in leading the conversion of info-path forms and designer workflows. The approach proved to be successful and can be applied with some enhancement to other types of software conversion, upgrade, re-write initiatives.