Skip to content

Export

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.

You want to…UseYou get
Move a project to another device, or keep a full copyExport project BA project archive that NAHPU can import or merge
Combine a teammate's project file with yoursMerge project ATheir records merged into the open project
Send records to a database, spreadsheet, or scriptExport records DA CSV, TSV, Excel, or JSON table
Publish or archive data with its filesBundle records CA Darwin Core bundle or NAHPU Data Package
Print labels, tags, catalogs, or field booksExport documents EA PDF
Report counts, such as specimens per speciesExport statisticsA summary table as CSV, TSV, Excel, or JSON
Pull out photographs and other media filesExport imagesOne file, or a TAR.GZ or ZIP archive of many
Protect everything on this deviceBackup database FOne archive of the whole installation
Share your settings, vocabularies, and presetsExport user configs GA JSON or JSON.GZ config file

Only three of these can bring data back into NAHPU:

  • a project export, via Import project on the home screen or Merge project in 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.

Keep a verified copy of each field day's work off the device you collect on. Combine two kinds of backup:

BackupHow oftenHolds
Project exportEvery field dayOne project, with its media in TAR.GZ or ZIP
Database backupWeekly, and before importing, merging, or replacing dataEvery project, file, and setting on the device
  1. Open the project Dashboard menu and select Export project.
  2. Check the record counts and any missing-file warnings. Leave Light export off and choose TAR.GZ or ZIP so media are included; Light export (JSON.GZ) holds records only and is not a full backup.
  3. Save the archive with the project name and date (or turn on Append date), then copy it to separate storage or another device.
  4. Open the copy to verify it is readable, and periodically test-import it on another installation.
  5. At your regular checkpoint, create a Backup database F. 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 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.

  1. Select Backup database F.
  2. Choose TAR.GZ or ZIP H, enter a File name (optionally turn on Append date), and choose a destination folder on desktop.
  3. Review the backup summary and select Save backup I. You can cancel while the archive is being written.
  4. Copy the archive off the device and verify it before removing an older backup.

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 settings
  • Tabular export presets
  • Document templates
  • Document layout presets
  • Template table preview columns
  • Custom fields (including selecting specific custom field definitions)
  1. Open Export user configs from the home screen menu, the project Dashboard menu, or Setup NAHPU.
  2. Select the configuration sections to include. If Custom fields is checked, choose which definitions to export.
  3. Review what will be written under Will export (under the Preview tab on phones).
  4. Choose JSON (.json) or the smaller JSON.GZ (.json.gz), set the File name (with optional Append date), and choose a destination folder on desktop.
  5. Select Export user configs. Use Share, open the folder, or save a copy once the file is written.

Restoring a database replaces everything in NAHPU on this device with a backup.

  1. Open Settings.
  2. Under Database, select Replace database.
  3. Under Replace with, select Browse and choose a .sqlite3 file, a ZIP archive, or a TAR.GZ archive.
  4. 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.
  5. Keep Back up current data first turned on so NAHPU saves your current data as a TAR.GZ archive in its backup folder.
  6. Select Replace database and 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.

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.

  1. Open Import user configs from the home screen menu, the project Dashboard menu, or Setup NAHPU.
  2. Choose a .json or .json.gz user-config file.
  3. Select the sections to import and review them under Will import (under the Preview tab on phones). If Custom fields is checked and a project is open, set Custom field destination to Global or Current project.
  4. Select Import selected configs and confirm with Import.

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.

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 export off 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 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.GZ or ZIP when 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.