> For the complete documentation index, see [llms.txt](https://docs.cdpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cdpi.dev/technical-notes/cloud-agnostic-deployment-of-dpi-and-data-portability/data-portability-as-core-principle.md).

# Data Portability as Core Principle

Data portability extends beyond technical capability to represent a fundamental right in modern DPI architecture. This principle manifests at multiple levels:

#### User-Level Portability

Citizens must retain ownership and control of their data:

**Standards-Based Export**: Data export capabilities using standardized formats — such as JSON, CSV, W3C Verifiable Credentials and FHIR for health records — ensure users can move their information between services without proprietary lock-in.

**Machine-Readable Formats**: Data must be provided in formats that enable automated processing — such as JSON, XML, JSON-LD, or Protocol Buffers — not merely human-readable representations like PDF reports or scanned documents.

**Complete Data Access**: Portability requirements should encompass all user data, including metadata, relationships, and derived data products.

#### System-Level Portability

DPI systems themselves must support operational data portability:

**Backup and Recovery**: Regular backups in provider-neutral formats enable recovery in different environments.

**Migration Capabilities**: Data export mechanisms should support bulk migration scenarios, not merely individual user requests.

**Referential Integrity**: Exported data must preserve relationships and constraints to enable functional restoration in new environments.

#### Interoperability Standards

True data portability requires more than export capabilities---it demands standardized formats that enable interoperation:

**Common Data Models**: Industry-standard schemas for identity, credentials, payments, and other DPI building blocks enable cross-system portability.

**API Standardization**: Standardized API specifications allow components to be replaced without disrupting dependent systems.

**Protocol Compatibility**: Open protocols for authentication, authorization, and data exchange reduce integration barriers.