Comparisons
Check app portability with records, files and a restore trial
Evaluate what you can take with you and whether the exported material can recreate the workflow you need.
Zocri · 2 min read · Sources checked
Inventory the parts that must move
Supabase notes that database backups include file metadata but do not include the objects stored through its Storage API. That illustrates why a backup or export needs a defined scope. For a client portal, list records, attachments, users, configuration and business history separately. A code download can preserve the interface while leaving important operating information elsewhere.
Decide what you need portability for: reporting, an emergency recovery, a developer handoff or moving to another service. These goals require different evidence. A spreadsheet of customers may support reporting but cannot by itself recreate sign-in, document access and approval history.
Inspect the actual export format
Export a small authorized sample and open it in an appropriate tool. Check identifiers, dates, status values and relationships between records. Confirm that text is readable and that an attachment reference points to a retrievable file rather than an expired or inaccessible address.
Ask how the export handles archived records, deleted items and ongoing changes. If staff keep working during the export, decide how the final state is established. Record the export time and source environment so a later comparison does not confuse a stale snapshot with missing data.
Try recovery in a safe destination
Use a separate environment to test the supported restoration or migration process. Recreate a few representative records with their attachments and relationships. Then follow the intended workflow: find a request, open its file and inspect the relevant history from an authorized account.
Keep credentials and secret configuration out of general export archives where they do not belong. Plan their secure reconfiguration through the appropriate service controls. Also identify which account owns domains, billing and external connections, because a restored data set does not automatically transfer those responsibilities.
Judge portability by the result
Record what moved successfully, what required manual work and what could not be restored. Include the time and expertise needed without extrapolating a small trial into a guaranteed large migration. Verify current terms and supported export paths before making a purchase or exit decision.
Repeat a bounded recovery check when the app gains a new kind of data or service dependency. Portability is useful when the business can retrieve and use what it needs, with ownership clear. A collection of downloadable files is only the beginning of that evidence, especially when the app's value depends on how those files and records fit together.