Skip to main content

Exit, portability & handover

A vendor exit must be possible without technical lock-in. The exit capability is part of the operating requirements and is verified before admission.

No technical lock-in​

Three requirements, all mandatory:

1. Data export in open formats​

Your application exports all application data in open, documented formats, for example SQL dump, CSV or JSON. The export must be complete and executable without vendor assistance.

2. A documented data model​

You provide a complete description of the data model and the required metadata, sufficient for the export to be interpretable without your help.

3. No forced dependencies​

No mandatory dependencies on proprietary services or APIs that would make a migration impossible in practice. This overlaps with the cloud-agnosticism requirement.

When a contract ends​

At the end of the contract, or on GovTech's instruction:

  • Orderly shutdown of the application
  • Complete data export (see above)
  • Deletion or handover of data as instructed, including affected backups, with verifiable evidence of deletion or handover

Transition support​

You are obliged to provide transition support: knowledge transfer and migration assistance, typically as a defined number of person-days. The concrete scope and duration are set in the Leistungsbeschreibung (Anlage 1) of your procedure.


Guidance, not contract

General guidance. The binding requirements are in the contract documents of your procedure, which may contain further or more specific requirements.