Data export for leaving customers

Project: Engineering
Type: Epic
Status: Done Done
Priority: Medium
Organization: Pellham Transport
Reporter: Ana Ruiz <ana.ruiz@acme-hq.example>
Assignee: Marek Nowak <marek.nowak@acme-hq.example>
Labels: pellhamdata-export
Components: identity-serviceportal
Fix versions: identity-service 2026.08.24portal 4.9
Created: 5 Aug 2026, 08:00 UTC
Updated: 24 Aug 2026, 13:30 UTC
Resolved: 24 Aug 2026, 13:30 UTC

Description

Shaped in Emargen: Data export for leaving customers. Product page: Confluence PROD › Data export for leaving customers.

Why

Pellham Transport left on 31 July, partly because they couldn't take their data with them. We made them a one-off export by hand (ENG-1542): about four engineering days (SUP-1011). Every customer should be able to take everything we hold for them, at any time.

What we build

Settings › Export your data, for administrators. ACME can also start it for a customer at the end of a contract.
A ZIP of CSV files, one per kind of record: people, depots, roles and assignments, access requests with every decision, the audit log, single sign-on settings without secrets; and a README describing each file.
Made in the customer's region. The download link works for 7 days and needs an administrator's sign-in.
Each export is written to the audit log.
After a contract ends: data deleted 30 days later; backups age out within 35 days after that.

Not in this epic

Passwords, recovery codes and API key secrets: never exported. Another product's format.

Done when

Any customer's administrator can export their data. Target 24 August.

Child issues

ENG-1602 Export everything for a client as CSV files in a ZIP, with a README Done
ENG-1603 Settings: export your data Closed
ENG-1604 Download link valid 7 days, behind an administrator sign-in, logged Done
ENG-1605 Runbook: an export at the end of a contract, and deletion 30 days later Done
ENG-1606 Portal: Settings › Export your data Done
ENG-1647 Export over 2 GB fails Done
ENG-1651 Times in the export are UTC without saying so Done
ENG-1662 Data export: include the approvals audit log Done

Linked issues

relates to SUP-1011 Pellham: full data export before leaving Done
relates to OPS-40 Pellham Transport: delete their data 30 days after the contract ended Done
relates to ENG-1542 Pellham: one-off export of all their data before they leave Done
relates to SUP-1119 Greenhollow: a full data export for our own records? Done

Comments (1)

Ana Ruiz · 24 Aug 2026, 13:30 UTC

Live for everyone. Pellham's data is deleted on Monday 31 August, the first working day 30 days after their contract ended (OPS-40). Closing.