Upgrade or remove Pūnaha

Before an upgrade

Use an upgrade path qualified for the exact starting build, target package, operating system, and database. RC1 source support is not a guarantee for every older development installation.

1. Record the installed version, package, provider, node roles, and ports.
2. Stop new work under the approved maintenance plan and create a consistent recovery checkpoint.
3. Include all three databases, required shared files, and the corresponding protected installation state.
4. Verify the target package and read its platform instructions.
5. Review how to recover if the target fails readiness.

Keep upgrade separate from removal

A supported MSI upgrade preserves configuration and protected state. The Ubuntu upgrade wizard retains existing choices and saves a protected settings copy. That settings copy is not a database backup.

Same version replacement, downgrade, and incomplete installation recovery need their explicit platform procedure. Do not uninstall first as a shortcut for upgrading.

Check the result

Verify the target version, retained settings, registration status, every node, and service readiness. Check safe workflow, case, document, and sign in journeys before reopening normal work.

If the upgrade fails

Keep the installer evidence and recovery copies. Do not assume the installer automatically restores databases or downgrades safely. Use the approved recovery checkpoint.

Remove an installation

Export and back up required information while normal access is available. Revoke and uninstall additional Nodes before removing the Primary. Review the platform's data removal behaviour before confirming.

Loss of registration does not itself delete data. Expired allowance blocks ordinary exports, so renew first if an export is needed.

Next step

Use Make a safe production change and Verify a backup and restore.