## TL;DR
Let the data transfer finish or re-run it, then complete the offboarding. Workspace blocks user deletion until owned data has a new home.

## Error
```text
Google Workspace offboarding failed: data transfer incomplete
```

## Steps
1. Open the Admin console data transfer section and check the transfer status for the user. Expected: you see whether it is pending, in progress, or failed.
2. If it failed, re-run the transfer to the designated recipient (manager or archive account). Expected: the transfer completes.
3. If it is in progress, wait; large Drives take time. Expected: completion confirmed.
4. Retry the offboarding (suspend, then delete) and confirm the license is freed. Expected: offboarding completes.

## When to use
- Workspace offboarding fails on data transfer
- The user has a large Drive or many owned files
- The transfer was started but never finished

## When not to use
- The user is a super admin (demote first)
- The transfer is not the blocker (read the actual error)
- You want to keep the data with no recipient (assign an archive account)

## Tool compatibility
Google Workspace Admin console and Data Transfer API.

### Variant phrasings
### transfer stuck at the same percentage
The transfer may be retrying on a huge file. Check the transfer logs and consider excluding it.

### offboarding via API fails the same way
The API enforces the same prerequisite. Complete the transfer first.

## Why it happens
Workspace will not delete a user who owns data without a transfer destination. The offboarding workflow must sequence transfer before deletion, and any transfer failure stalls the whole flow.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ozTk_5UvWd-e_u_kUtAWqQ
