Database architecture and transaction integrity

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

Overview

PostgreSQL stores organization identities, users, sessions, CRM records, permissions, commercial documents and durable automation state. Seven core modules share a records table with typed common columns and module-specific JSON. Dedicated tables hold commercial snapshots, custom values, templates, scheduling, approval processes and revenue agreements. This is a relational application with selected JSON structures, not a document-only database.

Purpose

Use this reference to understand data ownership, migration boundaries and why supported application operations are necessary for consistent changes.

Prerequisites

• Authorized database administration responsibility.

• Release-specific migration and recovery evidence.

Procedure

1. Confirm the running migration using System Health runtime identity or the installation runbook. Compare it with the intended release before maintenance.

2. Identify the business object and its related records through the application. Common CRM links include account, contact, deal, parent and related record.

3. Treat document snapshots, history and scheduled work as part of the object lifecycle. Updating a single database value can leave those records inconsistent.

4. Before a release change, use a verified coordinated recovery point and rehearse the forward migration on isolated targets.

5. After authorized maintenance, compare migration state and health with the approved plan and perform representative read-only business checks.

Expected result

Database maintenance preserves the relationship graph, commercial history and durable work expected by the application.

Screenshots and diagrams

Important notes

• Composite organization/reference constraints prevent cross-organization relationships for modeled links; service checks also validate module type and business consistency.

• Money uses fixed-precision values with explicit currencies. Do not add different currencies without a documented conversion rule.

• JSON fields and application validation are part of the schema contract. The presence of a database column does not make direct editing a supported workflow.

• A database dump alone omits private file bytes and external recovery keys. Follow the coordinated recovery guide.

Troubleshooting

• A relationship update is rejected: check organization, module, visibility and account/contact consistency.

• Migration and application versions differ: stop the change and reconcile the release plan before writing data.

Related articles

• CRM and commercial data relationships

• Private files and generated document storage

• Backend architecture and application services