Large screen
Small screen
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 device | Use | Result |
|---|---|---|
| The project does not exist yet | Import project on the home screen | A new local project |
| The project already exists | Merge project in that project | Imported 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.
Export a project
Section titled “Export a project ”- Open the project on the source device.
- Open the
Dashboardmenu and selectExport project. - Review
Archive contentsC: counts for personnel, taxonomy, sites, events, specimens, narratives, and media, plus totalMedia size(when media are included) and any missing-media warnings. - Choose what to include:
- Check the
File name(optionally turn onAppend date) and choose a destination folder on desktop. - Select
Export projectD. You can cancel while the archive is being built. Once finished, share, open the folder, or save a copy.
What a project export contains
Section titled “What a project export contains”- 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.
Import onto another installation
Section titled “Import onto another installation ”Use Import project to set up a project on a new device or recover it on a replacement device.
- Keep the source archive and back up any existing data on the receiving device.
- On the home screen menu, select
Import project, thenChoose archive. Pick a projectJSON.GZ,ZIP, orTAR.GZfile, or a NAHPU Data Package. - Check the project details and
Destination project name. If the project already exists on this device, selectOpen Merge projectinstead. A different project sharing the same name needs a unique destination name. - Acknowledge the backup reminder. Review personnel, taxonomy, and specimens, and resolve every item marked
Needs attention. - Review the final summary and any missing-file warnings, then select
Import project. - 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.
Merge into the matching project
Section titled “Merge into the matching project ”Use Merge project to combine a teammate's copy of the project with yours.
- Open your copy of the project.
- Open the
Dashboardmenu and selectMerge project. - Select
Choose archiveE and pick aJSON.GZ,ZIP, orTAR.GZproject export, or a NAHPU Data Package. - Acknowledge the backup reminder G.
- Review each section in turn: project info, personnel, taxonomy, sites, events, specimens, and narratives.
- Choose how to handle each match or conflict.
- 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.
Resolve conflicts
Section titled “Resolve conflicts ”When an imported record matches one already on this device, NAHPU keeps yours unless you choose otherwise:
| Choice | What happens |
|---|---|
| Keep current | Your record stays. Imported records that depend on it link to yours. |
| Use imported | The imported record replaces yours, along with the data it owns. |
| Import as new | The imported record is added separately, with a new UUID if needed and a unique suffix on duplicate site IDs. |
| Skip | The record is not imported. Dependent records that cannot be relinked are skipped too. |
How records are matched
Section titled “How records are matched”| Record | Matched by |
|---|---|
| Project info | Compared field by field |
| Personnel, specimens | UUID |
| Taxonomy | Genus and specific epithet |
| Sites | Site ID (when not empty) |
| Events | Site, start date, and ID suffix (start time is ignored) |
| Narratives | Site, 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.
Force merge a different project UUID
Section titled “Force merge a different project UUID ”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.



