Data export and offboarding

For

Company admins and security reviewers

Owner

Security and compliance

Outcome

Export required data and remove access or connections without losing audit truth.

Last verified

2026-08-30

Next review

2026-11-28

Status

supported

Customer journey

Export and offboard

Estimated time

20 min

Permissions and roles

Company admin

Open the completion checklistSteps, proof, and recoveryClose checklist

Prerequisites

• Company admin access
• An approved retention and ownership decision
• An approved export destination and evidence owner

Permissions in practice

• Company admin: create the approved export and remove access or connections.
• Security reviewer: approve retention, destination, ownership transfer, and deletion timing.

Steps

• Confirm the requester, workspace, records in scope, retention rule, and export destination.
• Reassign open customers, deals, tasks, campaigns, automations, and failed work.
• List users, API clients, mailboxes, providers, numbers, webhooks, and scheduled work to remove.
• Create the approved export and verify workspace, record types, counts, and destination.
• Pause dependent work, deactivate clients and providers, then remove user access.
• Record evidence retention and confirm required audit or compliance records remain available.

Success proof

• The export belongs to the correct workspace and contains the approved record types.
• Every open item has a new owner or an approved closure decision.
• Access and provider removal are recorded without deleting required audit evidence.

Common failures

• Open work is removed before ownership moves.
• The export is stored in an unapproved location or cannot be reconciled.
• A provider is disconnected before a fallback or queued-work decision exists.

Recovery

• Stop access removal and preserve the current workspace state while ownership and export gaps are corrected.
• Use the support path for an export or audit question. Do not share the export in chat.

Rollback

• Keep the approved export, ownership record, and provider list before disconnecting anything.
• Restore the last approved access or fallback path only through the named administrator.

Next task

Review release notes and record the final support owner.

Open next guide

Offboarding is an ordered control process. Confirm retention and ownership before removing a user, provider, API client, or workspace dependency.

Prepare the decision

1. Confirm the approved requester, records in scope, retention rule, and export destination.
2. Reassign open customers, deals, tasks, campaigns, and automation ownership.
3. List the users, API clients, mailboxes, providers, numbers, webhooks, and scheduled work to remove.

Export and verify

1. Create the approved export from the company data settings.
2. Confirm the export belongs to the correct workspace and contains the expected record types.
3. Store it in the approved location and record its retention or deletion date.

Remove access and connections

1. Pause dependent automation and provider work.
2. Deactivate API clients and integrations before deleting their configuration.
3. Remove user access after ownership has moved.
4. Confirm that audit and compliance records remain available as required.

Do not delete data only to test this procedure.