Why every product ships the same export
There is a school of thought that says making data easy to extract weakens your position, because a customer who can leave might. We take the opposite view, and not only for ethical reasons — the export is one of the most-used features in every product we ship.
1 min readOadbox
The spreadsheet is a legitimate tool
Finance teams, auditors and owners work in spreadsheets. They will continue to, regardless of what reporting the product offers, because a spreadsheet answers a question nobody anticipated.
Fighting this produces a stream of report requests, each one built for a single question asked once. Accepting it means every grid exports cleanly and the report backlog shrinks to the things that genuinely need to be reports.
What a good export does
- Exports what is on screen, including the filters applied — no surprises.
- Keeps numbers as numbers and dates as dates, not as text.
- Includes the identifiers needed to join back to other data.
- States the tenant, the filters and the timestamp in the file itself.
- Handles large result sets asynchronously rather than timing out.
It is also a migration promise
A customer's data belongs to the customer. A complete export — not just grids but master data and transactional history, in a documented format — should be available without a support request or a negotiation.
This gets discussed at renewal far more often than at purchase, and being able to answer it plainly is worth more than the small number of customers who might use it to leave.
Same behaviour everywhere
Because export lives in the shared core, it behaves identically in all eleven products. A finance lead who learned it in one place does not relearn it in another.
That consistency is invisible when it works and immediately obvious when it does not, which is a reasonable description of most infrastructure worth building.
Written by the Oadbox team. Something here not match how it works in your business? We would genuinely like to hear it — connect@oadbox.com.