Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Exit readiness

A checklist that keeps a public body ready to leave its supplier, its host or Exponential itself at any time - code and access you control, documented exports tested, keys and backups in your hands, contract terms and a…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/checklists/exit-readiness.md

On this page

Exit readiness

This checklist is for the contract manager and site administrator of a public body. Being able to leave is what keeps a supplier relationship fair. Exponential's license and exports make leaving possible; this checklist keeps it practical. The export tools come from Migrating away from Exponential.

Backups: a full site backup or the database and files, the base of an exit plan
Backups: a full site backup or the database and files, the base of an exit plan

Note This page describes features and common practice; it is not legal advice. Check your contract with your legal counsel.

Contents

  1. What you control
  2. Exports tested
  3. Keys and backups
  4. Contract
  5. Plan

What you control

  • To do: The software is GPL; you may give it to another supplier without permission (Licensing questions).
  • To do: Your custom extensions, designs and settings are in a repository your organization owns (Develop with Git).
  • To do: Named staff of your organization have administrator accounts on the site and access to the hosting.
  • To do: Documentation of the content model, roles, settings and deployment is in your hands.
  • To do: No kernel files changed in place; Setup > Upgrade check confirms it (The upgrade check).

Exports tested

Run an export test at least once a year, on a copy:

  • To do: Site archive of every class: ./console ext:xrowextract:archive --set=everything --format=zip --output=<dir>; manifest opened, row counts compared with the admin's counts (Migrating away from Exponential).
  • To do: The storage directory copied with it.
  • To do: A database dump with the engine's tool (Database backups per engine).
  • To do: Layouts, if used: ./console exp:layouts export --all --output=<file.zip>.
  • To do: Form submissions, consent records and the audit log exported where needed.
  • To do: Redirect list from URL aliases and wildcards (section 4).
  • To do: Note: the site archive never contains password hashes; users set new passwords on a new system unless it can verify standard PHP hashes (section 5).

Keys and backups

  • To do: Backups reach a place your organization controls, not only the host's (Backup readiness).
  • To do: Keys that cannot be recreated are in your hands: audit signing keys, the e-mail preferences secret, TLS keys (Keys and secrets).
  • To do: Domain names and DNS registered to your organization.

Contract

  • To do: Exit clauses: handover period, cooperation with a successor, data return and deletion (Exit plans).
  • To do: Notice periods and end dates known (The end of a contract).
  • To do: No clause that claims ownership of the code you paid for, or forbids giving it to another supplier.

Plan

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x