Skip to Content
ModulesExtensionsPurging extension data

Deleting an extension’s data

Destructive. Toggling an extension OFF disables the UI but keeps its data. Deleting its data drops every record that extension has stored for your organization. There is no undo.

The extension itself stays enabled after the delete — the most common reason to do this is clearing out test records before going live, where you want a clean slate, not the feature off.

Who this is for: org admins and owners. The extension must support bulk delete (most data-heavy ones do); consultancy extensions need ChAImp.

Steps

  1. Open Settings → Organization → Data.
  2. The Extension data card lists every enabled extension that supports bulk delete, each with a Delete data… button.
  3. The confirmation modal spells out what’s about to happen. Type DELETE to confirm.
  4. Permanently delete data. You’ll get a toast with the number of records removed. The extension stays on, ready for real data.

Settings-type records are kept — for example your funding filters, comms styles, or fraud thresholds survive a data delete; only the data rows (requests, donors, gifts, expenses, and so on) are removed.

Why delete

  • Demo / test cleanup — wipe trial records before your team starts for real.
  • Compliance — a retention decision requires the records gone.
  • Big mistake — the data is wrong and starting clean beats fixing it.

Common issues

  • An extension isn’t listed — it’s disabled, or it doesn’t support bulk delete yet. Consultancy extensions need ChAImp.
  • Need to recover data after a delete — you can’t. Export first: Exporting your data lives on the same Settings page. Treat every delete like the previous step in the runbook is “export first”.

Last updated: 2026-06-11 · Applies to: CartonCrew v1.120+

Requesting a consultancy extensionGlossary