Plan your exit before you commit to a builder

Collect the code ZIP and table CSVs separately

Overskill’s export help distinguishes the app source ZIP from per-table CSV downloads. It documents a 50,000-row limit per table export and says scheduled exports and live spreadsheet synchronization are not provided by that export feature. That is more specific than a general promise that you own your data. For a request tracker, inventory requests, comments and users separately, then check whether your sample keeps the relationships between them. A source archive and several spreadsheets are inputs to recovery, not proof of a working replacement.

• Record table counts and export time.
• Check whether files, configuration and relationships need additional handling.

Check the documented table-export limit

Overskill documents CSV export one table at a time, with up to 50,000 rows in each export. That can matter before a dataset reaches the limit, not only when leaving. Compare exported row counts with the source view using a supported method. If a table is larger, establish the supported complete-export procedure rather than assuming the first download contains everything.

Rehearse with harmless sample data

Open the export locally, inspect field names and confirm that identifiers and relationships remain understandable. Try restoring a small fictional sample into an isolated destination if you have the appropriate tools and permission. Do not upload customer data to another service just to test portability. Write down transformations and missing pieces so the next person does not have to reconstruct them during an outage.

Keep the old system until recovery is proven

Do not cancel the original account merely because a download succeeded. Confirm access to the required code, records and assets and test the critical workflow in the destination. Connected domains, email and payment services may need separate changes. Recovery costs and contractual obligations are project-specific. This checklist helps expose them; it does not establish that an Overskill export is automatically deployable on any host.

• Keep an export inventory with file date, table name, row count, field list and relationship notes. Store it securely and exclude secrets; a backup without recovery instructions can be misleading.