Verified backup
A backup captures a consistent SQLite snapshot inside a SHA-256 envelope. Before a restore replaces live data, StoreCrow checks the envelope, schema, SQLite integrity, foreign keys, facility scope and business invariants, stages the replacement, and retains a pre-restore safety snapshot.
Portable full-history export
The format-v2 portable package contains 13 documented operational datasets with stable IDs, ordered column definitions, relationship contracts, integer-cent accounting semantics, row counts and deterministic hashes. It retains payment and reversal chains, legal-history references, statuses, privacy events and the facility's normalized logo.
Security exclusions
The portable package excludes the local passcode verifier and other defined security-only fields. It can still contain sensitive tenant, financial and operational data. Treat the package like the live database: use an encrypted destination, control access and never email it unprotected.
A reviewable exit path
- Run Data Health and resolve unexplained integrity, relationship or ledger findings.
- Create a verified StoreCrow backup for recovery before beginning a migration.
- Create the portable full-history export and retain its verification result.
- Map StoreCrow fields and relationships to the chosen receiving system.
- Reconcile every dataset count, relationship, payment, reversal chain and sampled balance after import.
- Keep the original verified backup until the receiving system has passed operator acceptance.
What has been proved
StoreCrow's standalone verifier and importer have reconstructed the portable package into generic SQLite and reconciled the declared datasets, relationships and accounting chains. A named third-party destination still requires its own mapping, rehearsal and operator sign-off.
Read the concise portability evidence or review common operator questions.