Ownership has an operational test
Inventory the assets before delivery: domains, mailboxes, CRM, enrichment subscriptions, automation accounts, recordings, source records, templates and vendor contracts. Assign a client owner and an access recovery route to each. Clarify which agency tools are licensed services that cannot be transferred and what replacement path exists.
Keep named accounts rather than shared credentials. Document custom objects, field meanings, permissions, integrations and failure handling. A raw export is valuable, but it does not explain how a workflow runs. The internal operator should be able to trace an account and reproduce a routine task using the transferred material.
| Decision | Evidence to use | What changes next |
|---|---|---|
| Administration | Internal admin can grant and revoke named access | The agency is not the only recovery route |
| Data | Export, identifier and retention arrangements are tested | Records remain interpretable outside one vendor |
| Workflow | Logic, approvals, dependencies and recovery are documented | An internal person can operate after access transfer |
Work through the decision
Illustrative exit test: the client's administrator exports a small account cohort, checks that identifiers and source notes are intact, and uses the playbook to route a reply. Next, a controlled missing-field error is introduced in a test record. The operator follows the recovery guide without live agency help.
Only after these checks should agency access be removed. If a proprietary workflow cannot be transferred, identify it before signing and agree a replacement or ongoing license. Calling that asset client-owned without an operational route would be misleading.
The client owns the data but cannot use it
A folder of CSVs can satisfy a superficial handover while leaving the operating system unusable. Include field definitions, account identifiers and example tasks. Test data interpretation with someone who did not build the original workflow.
A concrete next step
Build the asset inventory now, while the engagement is being scoped. For each item, record owner, administrator, export method, dependency and the person who will operate it later.
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