2.4.2 Export — Data Extraction and Backups

Export functionality in Praisma Hub allows tenants to extract their data in a structured and controlled manner. Exports support operational needs such as reporting and archiving, as well as legal, contractual, and continuity requirements.

Exports are designed to be tenant-scoped, complete, and reproducible.

Purpose of Export

Exports are used to:

Retrieve content data for external analysis or reporting

Support data portability and vendor independence

Create structured backups for long-term retention

Fulfill legal or archival obligations

Exported data reflects the same schema and structure used internally by the CMS.

Export Scope and Structure

Exports can include:

Content entries and their versions

Field data and metadata

Relations between entries

Media references and associated files

Localization variants per language

All exports are generated within the boundaries of the active tenant.

Backup-Oriented Exports

For backup and continuity purposes:

Exports can be generated as complete tenant snapshots

Data is packaged in predictable, documented formats

Media and content metadata remain linked

These exports can be stored externally as part of an organization’s retention strategy.

Security and Access Control

Export operations:

Require explicit permissions

Are restricted to authorized roles

Are logged for audit purposes

Sensitive data is never exposed to unauthorized users.

Consistency and Reliability

Exports are generated from stable data states:

Active drafts and published content are handled consistently

Localization and relations are preserved

Export processes do not impact live operations

This ensures that exported data can be reliably re-imported or analyzed.

Summary

The export capabilities of Praisma Hub provide tenants with full control over their data. By offering structured, secure, and auditable exports, the platform supports transparency, continuity, and compliance.