Transfer identity, meaning and execution together
First confirm who owns the workspace, subscriptions and administrator recovery. Then inventory objects, fields, identifiers, permissions, integrations and secrets management. Keep credentials out of the playbook itself; document the approved access process instead.
Export a small sample and verify that relationships, sources and states remain interpretable. Demonstrate routine operation and a failed integration recovery. For nontransferable dependencies, agree a replacement or continuing license before the exit. Active opportunities need named successors and accurate buyer context.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Prepare | Inventory, internal admin and dependency map | Resolve ownership before revoking access |
| Verify | Sample export, field meaning and workflow demonstration | Prove records and logic are usable |
| Transition | Successor ownership, recovery and access review | Remove unnecessary access without breaking continuity |
Work through the decision
Illustrative transfer: the administrator verifies an export containing account identifiers, source notes and suppression. A successor then routes a controlled reply through the workflow. A missing-field error tests the recovery guide without using a real buyer.
If the automation runs under the departing person's account, reassign or replace it before removal. Record vendor limitations and the client owner. The transfer is complete only when the system continues under client control and the team can interpret what it does.
Revoking the builder breaks an undocumented integration
Map service identities and dependencies before access removal. Use named access and controlled transitions. Security cleanup and continuity should be planned together, not treated as opposing last-minute tasks.
A concrete next step
Run the transfer sequence on a small controlled cohort and one integration. Document any missing field, identity or dependency before applying the process to the full workspace.
Sources and research notes
- Attio: Back up workspace dataProduct documentation
- Attio: Sharing and permissionsProduct documentation
Primary sources reviewed October 6, 2026. The operating recommendations and worked scenarios are Daavid’s analysis. Illustrative numbers are assumptions, not measured client results. Company marks identify sources and prior experience; they do not imply a customer relationship or endorsement.
Schematic