Switching providers: procedures, formats and data register

Last updated: 13 August 2026

1. Available switching and porting procedures

• Self-service export: varies by data category — currently the payment-records export (CSV, where the payment feature is active) and the calendar feeds (iCalendar), both on every tier including the free tier. For the remaining categories, section 4 applies: API or export on request.
• API (REST v1): documented at zimun.online/docs/api, machine-readable description at /openapi.json (OpenAPI 3.x). For the purposes of switching, Zimun provides switching-scoped API access to the organisation and to the receiving provider free of charge on every tier (Art. 30(2) Data Act); in a switching case, a message to info@zimun.online suffices. Regular use of the API beyond that follows the booked tier.
• Export on request: data for which no self-service export function exists yet is exported by Zimun on request to info@zimun.online in a structured, commonly used and machine-readable format (Art. 30(5) Data Act).

2. Formats and relevant standards

• JSON via the REST API (described by OpenAPI 3.x, /openapi.json).
• CSV (RFC 4180, UTF-8) for tabular exports.
• iCalendar (RFC 5545) for calendar feeds.
• Timestamps per ISO 8601; time zones as IANA identifiers (e.g. Europe/Berlin); amounts as integer cents with ISO 4217 currency.

3. Register of data structures (Art. 26(b))

For each exportable category of Section 12 (7) of the Terms, the field structure is the one stated per endpoint in the API description at /openapi.json; it is machine-readable and stays current automatically with every change to the platform. Categories and their primary access routes:

• Organisation master data and settings — Settings / export on request.
• Locations, services and offerings including assignments — API (service and availability endpoints) / export on request.
• Team and member data — API (team endpoints).
• Resource and occupancy data — API.
• Working, opening and exception hours — API / export on request.
• Appointment and booking data including end-customer data — API (appointment endpoints).
• Booking-assistant conversation histories: not stored by Zimun and therefore not part of the exportable data.
• Billing records for platform payments — payment-records export in Settings (CSV).
• Calendar feeds — iCalendar subscription; configuration visible in the account.
• Records of acceptance of legal documents — export on request.

4. Known restrictions and technical limitations (Art. 26(a))

• For appointment, end-customer, service and team data there is currently no self-service export file; the route is the API or export on request. We say that here rather than hiding it behind "full export".
• Access secrets are never exported: API keys and OAuth access/refresh tokens for Google or Microsoft accounts are excluded; the organisation re-establishes those connections with the destination provider (Art. 30(6) Data Act).
• Internal security, rate-limiting and abuse-defence data is excluded from export under Section 12 (7) of the Terms (Art. 25(2)(f) Data Act).
• Zimun does not owe functional equivalence at the destination provider (that limb of Art. 30 concerns infrastructure services); what is owed is open interfaces and the formats described here.

5. Periods and charges

The three switching periods — notice period (at most two months), transitional period (30 calendar days, extendable once by the organisation) and retrieval period (30 calendar days after the transitional period) — are set out in Section 12 (6) of the Terms. Zimun charges no switching or data-retrieval fees; the regular tier charges remain payable during the transitional period.