Export everything you have here

Everything you have in the product is exportable, at any time, in a structured form.

How to do it

In the tenant admin, open Data and request an export. It runs as a job and you are told when it is ready.

You get your records in a structured form, your documents as files, and a manifest.

The manifest is the point

The manifest lists every relation with the number of rows exported and a digest of them, plus a separate count of documents.

That is what makes the export checkable rather than reassuring. Without it, an export is a folder you hope is complete. With it, a restore into another system can be compared against a number rather than against a feeling.

What proves it worked

Count what you received against the manifest, relation by relation. If they match, you have what we said you have.

The manifest also cannot claim to include documents and count zero of them. That specific check exists because the documents are the half that gets omitted: an "export" that is a spreadsheet of the database and none of the files is what most incumbents provide, and it is not an export.

Why this is not a retention lever

Your export does not require a request, a ticket, a notice period, or a conversation about staying. It is a button. If you are leaving, the fastest possible export is in our interest too, because the alternative is a slow leaver telling everybody about it.

If you are leaving

Suspension for non-payment does not close export, and neither does offboarding. Your data stays exportable through the whole process, and your unsubscribe links keep working for at least thirty days after you go, because the obligation attached to them is a duration rather than a link.

What an export is not

It is not a backup you can restore into this product with one click. It is your data, in a form another system can read. If what you want is a point in time restored inside the product, that is a different request and there are limits worth understanding before you need them: soft deletes have a stated undelete window, and field-level history can be replayed for the record types that keep old and new values.