How do I cancel iDBQuery and export my data?
You can cancel iDBQuery and take everything with you. Your underlying data already lives in your own sources — iDBQuery queries it in place rather than locking it away — and you can export the reports, dashboards and results you've built before your workspace is closed and its stored data deleted.
There's no lock-in trap with iDBQuery, largely because of how it's built.
The most important point: iDBQuery doesn't hold your source data hostage. It queries your MySQL, PostgreSQL, spreadsheets, files, APIs and warehouses in place, so the raw data never leaves your systems in the first place — cancelling doesn't strand it inside a proprietary store.
When you decide to leave:
- Export what you built. Reports, tables and dashboard results can be exported so the work you created in iDBQuery goes with you.
- Disconnect sources. Removing a source deletes its stored metadata, cached results and credentials.
- Close the workspace. On cancellation your workspace can be deleted, removing the associated stored metadata, cached results and logs. In self-hosted or air-gapped deployments, all of this already lives on your own infrastructure, so decommissioning is simply a matter of shutting the instance down.
Cloud plans are subscription-based with no obligation to keep paying to retain access to your own underlying data. Because every figure iDBQuery ever produced was cited back to your source rows, nothing you learned depended on a black box you can't reproduce later.
If you're planning a migration or an offboarding, our team can walk you through the export and deletion steps for your specific deployment.
Updated 2026-06-22