Large screen
Small screen
NAHPU exports project data, media, statistics, backups, and settings in formats tailored to each task. Project exports start from the project Dashboard menu; Backup database, Export user configs, and Import user configs are also available from the home screen menu.
Which export do I need?
Section titled “Which export do I need?”| You want to… | Use | You get |
|---|---|---|
| Move a project to another device, or keep a full copy | Export project B | A project archive that NAHPU can import or merge |
| Combine a teammate's project file with yours | Merge project A | Their records merged into the open project |
| Send records to a database, spreadsheet, or script | Export records D | A CSV, TSV, Excel, or JSON table |
| Publish or archive data with its files | Bundle records C | A Darwin Core bundle or NAHPU Data Package |
| Print labels, tags, catalogs, or field books | Export documents E | A PDF |
| Report counts, such as specimens per species | Export statistics | A summary table as CSV, TSV, Excel, or JSON |
| Pull out photographs and other media files | Export images | One file, or a TAR.GZ or ZIP archive of many |
| Protect everything on this device | Backup database F | One archive of the whole installation |
| Share your settings, vocabularies, and presets | Export user configs G | A JSON or JSON.GZ config file |
Only three of these can bring data back into NAHPU:
- a project export, via
Import projecton the home screen orMerge projectin an open project (Project transfer); - a NAHPU Data Package, which carries the same project transfer payload;
- a database backup, which replaces the whole installation (Restoring a database).
Record tables, Darwin Core bundles, documents, and statistics are one-way: NAHPU cannot rebuild a project from them. Importing a project-info JSON or QR code creates only the project's name and metadata, without records or media.
Backup strategy
Section titled “Backup strategy ”Keep a verified copy of each field day's work off the device you collect on. Combine two kinds of backup:
| Backup | How often | Holds |
|---|---|---|
| Project export | Every field day | One project, with its media in TAR.GZ or ZIP |
| Database backup | Weekly, and before importing, merging, or replacing data | Every project, file, and setting on the device |
- Open the project
Dashboardmenu and selectExport project. - Check the record counts and any missing-file warnings. Leave
Light exportoff and chooseTAR.GZorZIPso media are included;Light export(JSON.GZ) holds records only and is not a full backup. - Save the archive with the project name and date (or turn on
Append date), then copy it to separate storage or another device. - Open the copy to verify it is readable, and periodically test-import it on another installation.
- At your regular checkpoint, create a
Backup databaseF. Keep the previous checked backup until the new one is verified.
To recover a single project, use Import project on the home screen or Merge project inside an existing project.
Backup database
Section titled “Backup database ”Backup database saves the entire installation in one TAR.GZ (default) or ZIP archive H: the SQLite database plus the project, personnel, and settings folders, including files no current record links to. A bare .sqlite3 file holds records only, without media or other files.
Open Backup database from the home screen menu, the project Dashboard menu, or Settings > Database.
- Select
Backup databaseF. - Choose
TAR.GZorZIPH, enter aFile name(optionally turn onAppend date), and choose a destination folder on desktop. - Review the backup summary and select
Save backupI. You can cancel while the archive is being written. - Copy the archive off the device and verify it before removing an older backup.
Export user configs
Section titled “Export user configs ”Export user configs G saves your configuration so another device—or a future installation—uses the same setup without touching project data. You can open Export user configs from the home screen menu, the project Dashboard menu, or Setup NAHPU.
Choose which sections to export:
Controlled vocabularies and settingsTabular export presetsDocument templatesDocument layout presetsTemplate table preview columnsCustom fields(including selecting specific custom field definitions)
- Open
Export user configsfrom the home screen menu, the projectDashboardmenu, orSetup NAHPU. - Select the configuration sections to include. If
Custom fieldsis checked, choose which definitions to export. - Review what will be written under
Will export(under thePreviewtab on phones). - Choose
JSON (.json)or the smallerJSON.GZ (.json.gz), set theFile name(with optionalAppend date), and choose a destination folder on desktop. - Select
Export user configs. UseShare, open the folder, or save a copy once the file is written.
Restoring a database
Section titled “Restoring a database ”Restoring a database replaces everything in NAHPU on this device with a backup.
- Open
Settings. - Under
Database, selectReplace database. - Under
Replace with, selectBrowseand choose a.sqlite3file, aZIParchive, or aTAR.GZarchive. - Compare the two databases. NAHPU shows schema version, records, files, and size side by side. Older backups upgrade automatically after restore; files from a newer NAHPU version cannot be restored until you update NAHPU.
- Keep
Back up current data firstturned on so NAHPU saves your current data as aTAR.GZarchive in its backup folder. - Select
Replace databaseand confirm the warning.
What a restore does:
- Replaces the active database with the one in the backup.
- From an archive, copies project files into NAHPU's documents folder and imports settings from the archive. Personnel photos from older backups move to the personnel photo folder.
- Overwrites a media or settings file with the same name as one in the archive; identical files are left alone.
- Keeps files that exist only on this device, so they appear in later backups.
Restoring user configs
Section titled “Restoring user configs ”Import a user-config file to apply controlled vocabularies, presets, templates, layouts, or custom fields from another device or backup. Like exporting, Import user configs is available from the home screen menu, the project Dashboard menu, and Setup NAHPU.
- Open
Import user configsfrom the home screen menu, the projectDashboardmenu, orSetup NAHPU. - Choose a
.jsonor.json.gzuser-config file. - Select the sections to import and review them under
Will import(under thePreviewtab on phones). IfCustom fieldsis checked and a project is open, setCustom field destinationtoGlobalorCurrent project. - Select
Import selected configsand confirm withImport.
Selected sections replace the matching settings on this device, except Custom fields, which match by template ID and merge so existing definitions are kept. Unselected sections stay unchanged. If imported document templates reference fonts not installed on this device, NAHPU prompts you to pick replacements.
This changes settings only, not project records. To restore both together, restore a ZIP or TAR.GZ database backup. For technical storage details, see Data import and export.
Archiving a project
Section titled “Archiving a project ”An archive keeps a finished project usable years later by people who did not collect it. Store the data together with enough context to identify what it is, when it was made, which software created it, and who curates it.
Before archiving:
- Finish curating the data and fix or document known issues. See Data Management.
- Create a fresh database backup.
- Export user configs if controlled vocabularies, record-export presets, document templates, print-layout presets, or custom fields are needed to reproduce the work.
- Create a full project export with
Light exportoff so media are included, checking record counts and missing-media warnings first. - Add tabular record exports or a data package if the data will be analyzed, published, or reused outside NAHPU.
Name files clearly with the project, export type, and date, such as BorneoMammals_project_20241015.tar.gz. Store the project export, database backup, user-config file, and a short readme together.
Keep at least two copies in separate locations, and retain the original until the archive opens cleanly on another device. Record the archive date, contents, storage locations, and any access restrictions, and periodically test-open or test-restore the files. Follow your institution's retention policies for both digital files and printed documents.
Before sharing data
Section titled “Before sharing data ”Before sending NAHPU data to a museum, collaborator, or another device:
- Create a fresh database backup.
- Choose the right project export:
Light export(JSON.GZ) when the recipient needs records without media (such as over a slow connection);TAR.GZorZIPwhen media or a complete copy must travel with the project.
- Export user configs if the recipient needs your controlled vocabularies, presets, templates, layouts, or custom fields.
- Include any tabular exports, bundles, or documents the recipient requested.
- Verify that at least one restore path works before deleting anything from the source device.



