A K2 upgrade needs a plan for the applications as well as the platform. We assess dependencies, compatibility and testing before agreeing the implementation scope.
Plan the upgrade around your applications
A Automation K2 upgrade affects more than the installer. Forms, workflows, integrations and authentication need to continue working for the people who depend on them.
We begin with an assessment of the installed environment and the applications it supports. The findings define the upgrade scope, prerequisites and testing required.
Establish the route
We review the installed version, relevant fixes, dependencies and the target release. The appropriate path is checked against current Nintex documentation; older installations may need intermediate steps.
Where the environment contains legacy functionality or custom development, we identify the work required before moving forward.
Prepare a controlled transition
The implementation plan should define responsibilities, a test environment, application acceptance checks and an agreed recovery approach. Business users need to verify the processes that matter to their work, including exceptions and integrations.
We agree the delivery scope after assessment, including any specialist infrastructure work that needs to be provided by your IT team or another supplier.
Make an informed decision
The newest release is one input to the decision. Product support, application compatibility, organisational priorities and the available testing window all matter.
