On this page
Start with a service job, not “all customer data”
A replacement team may need current service obligations, equipment identifiers, open jobs, authorised contacts and relevant history. It may not need every prospect note, employee record or unrelated file held by the outgoing partner.
The U.S. Federal Trade Commission (FTC)’s business guidance emphasises understanding information flows, limiting what is kept and controlling service-provider access. Those security principles do not decide who owns your customer relationship or whether a particular transfer or deletion is lawful.
Define a usable and permitted handover
Make a record-category register with the responsible business and systems owners. This is an ELN continuity exercise, not a grant of access or a universal retention schedule.
| Category / question | Evidence for the rehearsal |
|---|---|
| Current obligations | Open orders/jobs, status, required follow-up and responsible company |
| Data and permissions | Fields needed, permitted recipients/use and privacy/contract review |
| Usable export | Format, identifiers, attachments and a way to verify completeness |
| Access transition | Accounts, keys or integrations to change through authorised administrators |
| Retention or return | Applicable obligations, disputes/holds and agreed return/deletion process |
Prove that the next team can use the record
Fictional rehearsal: an authorised sample contains 20 open service jobs. The receiving team matches 18 to the correct equipment and obligations; two lack identifiers and three attachments cannot be opened. The sample has exposed practical gaps even though a file was exported.
Resolve the gaps and repeat the check within the approved scope. Record who verified the result and what was excluded. A sample test does not establish that the whole database is complete, accurate or legally transferable.
Coordinate continuity and access changes
Give the owner a plan for the actual exit date: required records, authorised recipients, responsible people, technical steps and unresolved legal/security questions. Avoid leaving shared credentials active simply because one export was incomplete.
Equally, do not assume every record should be erased on the last service day. Actual retention obligations, claims and rights need checking. Management dependence can assign the jobs and backups; the educational tool neither stores the customer database nor decides the permission question.
Scope
- Commercial continuity and security preparation, not a customer-ownership decision, privacy-transfer permission, legal hold assessment or universal deletion rule.
Next step
Use Management dependence to name the records-handover lead, technical administrator and legal/privacy checker. Keep the authorised record-category register and rehearsal evidence in your own secure systems.
Sources & review notes
U.S. Federal Trade Commission
Passage, dates and research notes
official-guidance · Take Stock; Scale Down; Lock It; service-provider access and retention
Selected full sections read. Security practices do not establish ownership, transfer permission or a universal deletion date.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.