ZBIX CRM 1.2.0

Prepare a CRM upgrade

Product Zbix CRM · Version 1.2.0 · Source reviewed · Reviewed 28 October 2026
Audience Administrators and implementation teams · Deployment Release specific self hosted

Overview

An upgrade changes the application release and may apply forward-only database migrations. Preparation must establish the current identity, target identity, a usable recovery point and an approved response if migration or readiness fails.

Purpose

Make a release change reviewable before interrupting service or changing the database.

Prerequisites

A release owner, database/recovery owner and approved maintenance window.
The target package, trusted digest and release-specific upgrade guidance.
Access to the current installation’s version, schema, backup evidence and operational monitoring.

Procedure

Record the current package version, source identity where available and database migration. Record the target release and supported upgrade route. Resolve ambiguous version labels before proceeding.
Verify the target package and review its migration, configuration and operational changes. Keep the existing configuration, external keys and persistent storage protected.
Create a fresh recovery point from the current installation. Complete independent verification and an isolated restore test for that exact artifact.
Arrange an approved off-host copy or destination and independent key custody. Confirm the recovery team can retrieve what is needed if the host becomes unavailable.
Rehearse the target upgrade against an isolated restored environment when the approved change process requires it. Record preserved data, schema result, readiness, worker behavior and relevant business checks.
Agree the service interruption window, communications, validation steps and decision owner. Define when to remain stopped, recover, or perform a reviewed forward repair.
Retain the prior package and the recovery evidence. Begin the upgrade only after the prerequisite review is complete.

Expected result

The change record contains matching current/target identities, verified recovery evidence, validation steps and an approved failure response.

Important notes

A package download, database dump or recovery-point identifier alone does not prove recovery readiness.
Do not replace encryption keys or remove volumes during an upgrade.
Historical acceptance of one upgrade does not qualify every source/target version pair. The 27 October report documents a specific v1.2 upgrade.

Troubleshooting

If a restore rehearsal fails, resolve it before cutover and preserve the last usable point.
If release documentation conflicts, use the exact package/source identity and obtain release-owner clarification; do not combine instructions from old v0.x and v1.x packages.
Escalate missing recovery keys, unsupported schema paths and unverified target packages before service interruption.

Download manuals ↓

Need a hand?

Search the guides or talk to the ZBIX team.

Find support