Ausstieg und Datenübertragbarkeit
Ausstiegsregelungen
When a contract ends, you keep your data, your documents and the knowledge needed to run the service with another supplier or your own team. This page covers what we hand back, in which formats, and how we run the exit.
What exit means for each way we deliver
We deliver in four ways, and one contract can use several of them.
- On your infrastructure
- The systems and their databases already run on servers you control, and the data does not move unless you ask. We hand over the configuration, deployment scripts and runbooks, then remove our own access.
- Hosted by RODMENA
- Each customer of a service we host has its own tenant or database. At exit we export your data, you confirm that it loads, and we then delete our copy as the Data Processing Agreement sets out.
- Software we write for you
- Where the contract gives you the code we wrote for you, we hand over the repositories with their full history, the build and deployment instructions, and the specification and ticket behind each change.
- Our open-source libraries
- Libraries such as stabilize, datashard and scriptplan are published on GitHub under the Apache 2.0 licence. Code that depends on them keeps working after you leave because their source stays public.
What you get back
- Databases
- Most of our products keep their data in PostgreSQL. We give you a full export made with
pg_dump, which any PostgreSQL installation of the same or a later major version can restore without RODMENA software. - Records in open formats
- Records also come out in open formats that a spreadsheet or another system can read. Ledger and Trace export CSV and JSON, Siambr exports its audit trail and reports as CSV, Provenance exports CycloneDX, SPDX and VEX, and the knowledge base exports Markdown and JSON.
- Documents and files
- Uploaded documents and attachments come back as the original files together with a list that ties each file to its record.
- Audit trails and approvals
- Audit logs and approval records travel with the data they describe. After you leave, you can still show who did what and when.
- Configuration and keys
- We hand over the configuration of each system, any encryption keys that belong to you, and a list of the accounts, integrations and scheduled jobs to move or switch off.
How the exit runs
- Planned at the start
- We draft the exit plan with you when the contract starts and update it when the service changes. It names the data sets, their formats, who receives them and the order of work.
- Exit period
- The contract sets the exit period, typically 30 to 90 days depending on the size of the engagement. It also states which exit work is included and how further assistance days are charged.
- Trial export
- Before the final export we send a trial one. You or the incoming supplier can load it and raise any problem while there is still time to fix it.
- Knowledge transfer
- The engineers who built and ran the service hold handover sessions with your team or the incoming supplier, walk through the runbooks and answer questions until the exit period ends.
- Parallel running
- Where the contract provides for it, we keep the service running until its replacement is live and you have checked the migrated data against the original.
- Closing access
- At the end we remove our accounts, hand back or revoke any credentials we held, and confirm in writing that our access has ended.
Löschbescheinigung
Nach dem Ausstieg löschen wir die personenbezogenen Daten und Kundendaten, die wir vorhalten, oder geben sie auf Wunsch zurück und bescheinigen die Löschung auf Anfrage schriftlich, wie in unserem Auftragsverarbeitungsvertrag (AVV) zugesagt.
Fragen zur Ausstiegsplanung: legal@rodmena.co.uk.
The Service and SLA page describes how we support a running service. The Trust Centre lists our certificates, insurance and policies.