Data
Local backup, CSV export, and JSON restore
Use Local Backup & Transfer for full-device JSON restores, and use CSV Transfer for spreadsheet-style exports and imports.
Updated May 29, 2026 5 min read
The Export / Import screen now separates two different jobs. Local Backup is the full JSON restore path for moving the shop between devices without Google Drive. CSV Transfer is for spreadsheet work, bulk row imports, and accountant-friendly exports.
Local backup vs CSV transfer
| Need | Use |
|---|---|
| Move the whole shop to another phone | JSON Local Backup & Restore |
| Keep a recent manual offline backup | JSON Local Backup & Restore |
| Open records in Excel or Sheets | CSV export |
| Bulk-import rows from another system | CSV import |
JSON local backup and restore
- Open Settings → App Settings → Local Backup & Transfer.
- Use Export JSON to create one file containing the shop database, settings, technicians, manufacturers, quotes, orders, repairs, customers, and the stored shop logo bytes.
- Use Import JSON only on the destination device you want to replace. The import restores the full app state, not a few selected rows.
- After a successful JSON import, RepairNode closes so the restored state can reopen cleanly.
CSV transfer workflows
- CSV export is split by entity: customers, repairs, orders, and quotes.
- CSV import is best for bulk row creation or migration from another spreadsheet-driven tool.
- Use an exported CSV as the template so the column names stay exactly in the format RepairNode expects.
- Importing the same CSV twice can duplicate records, so treat CSV import as a manual transfer tool, not as a sync system.
What is not included
Was this article helpful?