Data Preservation Across Downgrades, Updates, and Uninstall
This article summarizes the preservation-first contract for higher-tier settings, Workspaces, connections, job history, Recovery data, preview history and stored configuration across entitlement changes and lifecycle events.
What you need to know
- QCSB is preservation-first: normal upgrades install the outer package over the current installation, and downgrade/uninstall behavior does not intentionally erase stored configuration/history merely because a feature is no longer usable.
Preservation-first behavior
| Event | Expected preservation behavior |
|---|---|
| Plan downgrade / Effective tier falls | Stored higher-tier settings, connections, Workspaces/history are retained; premium controls become unavailable rather than being erased. |
| Normal package update | Install the outer package over the existing installation. Provisioning/migrations may run, but existing customer data/configuration is preserved. |
| Intentional uninstall | The corrected 1.01.08 lifecycle does not run install/update repair logic while files/plugins are being removed; QCSB is designed not to intentionally erase stored operational data as a side effect. |
| Max Preview / All Access ends | Effective capabilities fall appropriately without rewriting the underlying Base tier or resetting preview history. |
What preservation does not mean
Preserving a saved configuration does not mean the current lower Effective tier may still use that premium feature. QCSB separates retaining customer data from authorizing the feature now.
Community Discussion
For practical QCSB workflows and discussion with other Joomla site owners, visit the QC Storage Bridge Community. For private support, bug reports, account-specific entitlement issues, or feature requests, use the QuantaCade support system.