EU Data Act
Data portability and provider switching
Last updated: August 3, 2026
This register describes the standard procedure and the usual data categories, structures and formats for switching a data processing service operated by WZ-IT.
Scope
This information is the technical standard for WZ-IT managed hosting and comparable data processing services. The specific scope, data actually present and service-specific deviations are defined by the applicable contract and service schedule. Pure consulting, development or maintenance services without a supplied data processing service are not automatically covered.
Standard procedure
- 1
Switching request
The customer submits a switching, transfer or deletion request through the ticketing system specified in the contract. If that system is demonstrably unavailable, the independent fallback channel specified in the contract applies.
- 2
Identity and inventory check
WZ-IT verifies authorisation, the affected service, target system, exportable categories, dependencies and known technical risks. Required information and customer actions are documented in the ticket.
- 3
Export and transition
The export is created in the agreed formats or the standard formats below and supplied through a secure transfer method. Contracted continuity is maintained during the transition.
- 4
Validation and retrieval
The customer can check the export for completeness and technical readability. After the transition, the supplied data remains available for retrieval for at least 30 calendar days unless the contract specifies a longer period.
- 5
Deletion
After the retrieval period, WZ-IT deletes the affected production copies unless a statutory retention duty or documented instruction requires otherwise. Technically unavoidable copies in rolling backups are blocked and overwritten through the regular cycle.
Data categories
Usually exportable
- files and objects supplied by the customer or generated through the service
- customer-specific database contents, including the schema information required for interpretation
- customer-specific application, system, role and access configurations where technically exportable
- customer-specific logs within the agreed retention period
- customer-owned VM or container images and backups where included in scope
- metadata required to understand the structure and allocation of exported data
Usually excluded
- WZ-IT internal billing, capacity and administrative data
- non-customer-specific internal telemetry, security rules and detection logic
- internal orchestration secrets, credentials and cross-tenant configuration
- internal notes, runbooks and trade secrets where exclusion does not impede switching
- non-transferable third-party components or licence rights
The exhaustive service-specific list is maintained in the applicable service schedule. Exclusions are not applied in a way that prevents or delays a legally required switch.
Data structures and standard formats
| Category | Standard format | Notes |
|---|---|---|
| Files and objects | original format, tar.gz or ZIP | Directory structure and file names are preserved where technically possible. |
| Relational databases | native dump or SQL; CSV or JSON where agreed | Schema and character encoding are documented. Engine and version dependencies may apply. |
| Configuration | YAML, JSON, TOML or text | Secrets are transferred only where owned by the customer and capable of secure export. |
| Virtual machines | QCOW2, RAW or OVA where supported | Drivers, firmware, licensing and the target platform may require conversion. |
| Containers | OCI image and YAML/JSON manifests | External images and registry contents remain subject to the applicable usage rights. |
| Logs and metrics | JSON, CSV or text | Limited to the contracted retention period and customer-specific data actually present. |
For different services, WZ-IT documents the specific format, structure, relevant standards and known technical limitations in the switching ticket or service schedule. Proprietary target systems may require additional transformation work.
Transfer method
The standard method is an encrypted download or transfer to a secured destination supplied by the customer. Large or particularly sensitive exports may be transferred through SFTP, object storage or a secured network connection. Credentials are transmitted separately.
Time periods
Initiation may be subject to a notice period of no more than two months. The standard transition period is no more than 30 calendar days. Where this is technically infeasible, the information and extension rules in the contract and EU Data Act apply. The standard retrieval period after transition is 30 calendar days.
Charges
The standardised data export is free of charge. Until and including January 11, 2027, additional switching assistance required by law may be charged only at demonstrable costs directly caused by the switch. From January 12, 2027, WZ-IT does not impose switching charges. Ordinary service fees during notice and transition, and voluntary additional work, remain unaffected.
Requests and technical information
Binding switching requests and technical questions are submitted through the ticketing system named in the contract. This allows authorisation, deadlines, export scope and handover to be assigned to a customer and service with a reliable audit trail. General questions may be sent to [email protected]; an email does not start a contractual SLA response time.