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

Exit plan template for an Exponential site

A copy-and-fill exit plan for a public website or intranet on Exponential - inventory, deliverables with formats, roles, timeline, verification, personal data rules, redirects and sign-off - to attach to the contract…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/procurement/exit-plans/exit-plan-template.md

On this page

Exit plan template for an Exponential site

This page is for the project manager who writes the exit plan, usually as an annex to the contract with the implementation, hosting or support supplier. Copy the blocks into your document and fill the blanks. The deliverables and their formats come from Migrating away from Exponential and Backups: what to back up.

Template - adapt to your procurement rules; not legal advice.

Contents

  1. Part 1 - Scope and roles
  2. Part 2 - Inventory
  3. Part 3 - Deliverables
  4. Part 4 - Timeline
  5. Part 5 - Verification
  6. Part 6 - Personal data and deletion
  7. Part 7 - Sign-off
  8. Testing the plan

Part 1 - Scope and roles

System:            <site names and addresses>          Exponential version: <...>
Contract:          <reference>, ends <date>
Exit trigger:      end of contract | termination | change of system | supplier failure
Exit owner (us):   <role>        Supplier exit lead: <role>        Receiving party: <role or new supplier>
Data protection:   <role>        Security: <role>                  Records: <role>

Part 2 - Inventory

Keep this current; review it yearly.

Sites and siteaccesses:          <list>                     (Setup > System information shows them)
Languages:                       <list>
Content classes:                 <count, list>             (Setup > Classes)
Active extensions:               <list, with versions>      (Setup > Extensions)
Custom extensions and designs:   <list, Git repositories>
Integrations:                    <systems, direction, protocol>
Database engine and version:     <...>
Engine:                          Velocity | Apache/nginx with PHP-FPM | FrankenPHP
Hosting:                         <provider, location of data and backups>
Scheduled jobs:                  <cron entries>             (Setup > Cronjobs)
Third-party services:            <analytics, captcha, maps, mail, ...>

Part 3 - Deliverables

#DeliverableFormatSource
D1Site archive of all contentxrowextract archive: CSV per class, manifest.json, README.txt (ZIP or TAR)Data export formats
D2Full database dumpengine's dump tool, or exp:ezsqldumpschemaDatabase backups per engine
D3Filesvar/storage/ and var/<site>/storage/Backups: what to back up
D4Settingssettings/override/, settings/siteaccess/ (private transfer)Keys and secrets handover
D5CodeGit repositories of custom extensions and designs, with historyDocumentation handover
D6Layouts (if used)exp:layouts export ZIPLeaving Exponential
D7Form submissionsext:bccie:export CSVsame
D8Consent recordsexp:mailconsent CSVsame
D9Audit trailaudit directory with signed manifests; exp:audit exportAudit trail
D10Address list for redirectsfrom the archive plus ezurlalias_ml, ezurlwildcardURL redirects after exit
D11Documentationcontent model, settings, integrations, runbooksDocumentation handover
D12Versions noteExponential, PHP, database, engine, extensionsCustomer offboarding

Part 4 - Timeline

T-<n> weeks   exit plan reviewed; receiving party named
T-<n> weeks   test export delivered and verified (D1-D3)
T-<n> days    content freeze announced to editors
T             maintenance mode on; final export D1-D12; maintenance off (or site handed over)
T+<n> days    receiving party confirms completeness in writing
T+<n> days    supplier deletes data as agreed and confirms in writing

Part 5 - Verification

  • To do: manifest.json of D1 opened; row counts per class match the counts in the administration.
  • To do: A sample of files from D3 opens; images referenced in D1 exist in D3.
  • To do: D2 restored once on a test machine; the site starts (Restore and restore tests).
  • To do: D9: the audit chain verifies (./console exp:audit verify).
  • To do: D5 builds; no file is missing compared with production.

Part 6 - Personal data and deletion

  • Which personal data goes to the receiving party, and on which legal basis: <...>
  • Password hashes: not in the site archive; users reset passwords on the target unless agreed otherwise (Personal data at exit).
  • Supplier deletes: production, staging, backups, logs - on <date>, confirmed in writing.

Part 7 - Sign-off

Exit completed: <date>     Our exit owner: <name, signature>     Supplier: <name, signature>
Open items: <list>

Testing the plan

Run Parts 3 and 5 once a year on a copy, with the supplier. An export that was never tested is a hope, not a 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