4 min read· DirtFleet team
No data lock-in: every endpoint that lets you leave
We don't trap your data. Here's the full list of export endpoints — the GDPR archive, the per-asset CSV, the OSHA 300 export, certified payroll, work-order history — and what we promise post-cancellation.
Every fleet software pitch ends with “you can export your data.” Most of them mean a CSV of the asset list and a smile. Here is the full list of DirtFleet export endpoints, what they emit, and what we commit to post-cancellation.
The endpoints
| Endpoint | What it emits |
|---|---|
/api/export/org-archive | Full org dump as JSON: every member, asset, log, flag, work order, project, incident, certification. The GDPR-style “everything you have on me” export. |
/api/export/assets | CSV of the fleet roster — drop into a new system on day 1. |
/api/export/hours | CSV of hours / odometer logs over a date range. Pair with GPS metadata when captured. |
/api/export/service-rollup | Repair logs + service-task completions merged into one accountant-friendly CSV. |
/api/export/osha300 | OSHA Form 300-aligned CSV of recordable incidents in a date window. JSON variant available for programmatic use. |
/api/export/certified-payroll | Davis-Bacon weekly worker × week × asset rollup for any project. |
/api/v1/assets + sibling REST endpoints | JSON via your API key — the same data the in-app dashboard reads. No second-class “export view.” |
The promises
- 30-day post-cancellation export window. If you cancel, your data stays accessible (read-only) for 30 days so you can run any of the exports above. After 30 days we purge per the privacy policy.
- No proprietary file formats. Everything is CSV or JSON. No vendor-locked schemas, no “contact support to arrange the migration” nonsense.
- API access through cancellation date. Your API keys keep working until the subscription ends. Drain at your own pace; we don't cut you off mid-script.
- Help if you need it. Email support@dirtfleet.app; we'll help you script the migration to whatever you pick next. The same crew that built the export endpoints knows them.
What we don't do
- We don't generate competitor-specific import files. Most fleet platforms accept generic CSV; the mapping is on you (or your new vendor's onboarding team).
- We don't back up the photos at the photo-storage layer for you post-cancellation. They're included in the org archive as base64 (when on the DB backend) or as references when on S3/R2 — pull them while the window is open.
Why we put this on the website
Every salesperson tells you their software has “great export” until you ask for it. We list the endpoints so you can curl them yourself before signing. If something on this page is missing or misleading, file a ticket — we'll fix the page or the endpoint, whichever is wrong.