Skip to content

Transfer a Project

A project transfer moves a NAHPU project—with its records and media—from one installation to another. Export project writes the archive; the receiving device reads it in one of two ways:

On the receiving deviceUseResult
The project does not exist yetImport project on the home screenA new local project
The project already existsMerge project in that projectImported records combined with existing ones

Both flows accept a project export or a NAHPU Data Package, which carries the same project transfer payload. Record tables, Darwin Core bundles, and documents cannot restore a project. Importing a project-info JSON or QR code creates only the project's name and metadata, without records or media. To replace the entire installation instead, see Restoring a database.

  1. Open the project on the source device.
  2. Open the Dashboard menu and select Export project.
  3. Review Archive contents C: counts for personnel, taxonomy, sites, events, specimens, narratives, and media, plus total Media size (when media are included) and any missing-media warnings.
  4. Choose what to include:
    • For a full transfer or backup, leave Light export off and choose TAR.GZ (default) or ZIP A. Media are included.
    • Over a slow connection, turn on Light export B. NAHPU writes a smaller JSON.GZ file without media.
  5. Check the File name (optionally turn on Append date) and choose a destination folder on desktop.
  6. Select Export project D. You can cancel while the archive is being built. Once finished, share, open the folder, or save a copy.
  • Every record belonging to the project, including specimen parts, symbionts, custom fields, and each specimen's taxon-specific attributes (for invertebrates: ecological interactions, environmental parameters, optional morphometrics, sex, and remarks).
  • Only the taxa referenced by the project's specimens.
  • Personnel photos, project media, and taxon media present on disk. Any missing file is listed as a warning and its file link is left out.

Use Import project to set up a project on a new device or recover it on a replacement device.

  1. Keep the source archive and back up any existing data on the receiving device.
  2. On the home screen menu, select Import project, then Choose archive. Pick a project JSON.GZ, ZIP, or TAR.GZ file, or a NAHPU Data Package.
  3. Check the project details and Destination project name. If the project already exists on this device, select Open Merge project instead. A different project sharing the same name needs a unique destination name.
  4. Acknowledge the backup reminder. Review personnel, taxonomy, and specimens, and resolve every item marked Needs attention.
  5. Review the final summary and any missing-file warnings, then select Import project.
  6. Open the imported project and spot-check sites, events, specimen IDs, narratives, and attachments.

A JSON.GZ file contains no media. Keep the source archive until you have verified the imported project.

Use Merge project to combine a teammate's copy of the project with yours.

  1. Open your copy of the project.
  2. Open the Dashboard menu and select Merge project.
  3. Select Choose archive E and pick a JSON.GZ, ZIP, or TAR.GZ project export, or a NAHPU Data Package.
  4. Acknowledge the backup reminder G.
  5. Review each section in turn: project info, personnel, taxonomy, sites, events, specimens, and narratives.
  6. Choose how to handle each match or conflict.
  7. Check the final summary and select Merge project.

Nothing is written while you step through the wizard. NAHPU commits all changes together at the final step; if the merge fails, the database stays unchanged and newly copied media files are cleaned up.

When an imported record matches one already on this device, NAHPU keeps yours unless you choose otherwise:

ChoiceWhat happens
Keep currentYour record stays. Imported records that depend on it link to yours.
Use importedThe imported record replaces yours, along with the data it owns.
Import as newThe imported record is added separately, with a new UUID if needed and a unique suffix on duplicate site IDs.
SkipThe record is not imported. Dependent records that cannot be relinked are skipped too.
RecordMatched by
Project infoCompared field by field
Personnel, specimensUUID
TaxonomyGenus and specific epithet
SitesSite ID (when not empty)
EventsSite, start date, and ID suffix (start time is ignored)
NarrativesSite, date, time, and writer

Personnel and taxa are shared across every project on the device, so the wizard warns whenever replacing one could affect another project. A specimen UUID belonging to a different project cannot be replaced; import it as new or skip it.

Merging normally requires the archive's project UUID to match the open project. A mismatch is blocked because it usually means the wrong project is open.

If both archives genuinely belong to the same field project, turn on Force merge into the active project and type the open project's name to confirm. NAHPU reassigns the imported records to the open project's UUID. Conflicts are never overwritten automatically; every conflict choice above still applies.