Upload the correct kind of file
Open Add Dive and choose Import from file. The shared dropzone detects a dive-entry CSV separately from profile CSV, UDDF, FIT, KML, or KMZ sources.
A normal entry CSV contains one dive per row. A profile CSV contains sampled elapsed-time/depth rows; do not use one format in place of the other.
Map source columns and source units
For each CSV header, choose the matching dive field or leave it Ignored. Select whether depth values are metres or feet and whether temperatures are Celsius or Fahrenheit.
The preview sample helps verify that headers were assigned correctly. Required information must be mapped before the final row preview can be reliable.
Review row states before committing
Select only rows you intend to create, then choose Commit selected. The application creates entries only at that point; upload and mapping never silently add final dives.
- New means the row is ready for normal review.
- Duplicate means it resembles an existing logbook entry; decide whether it should still be imported.
- Warning means the row can require attention but may remain selectable.
- Error means the row cannot be committed until its source or mapping is corrected.
- Committed means the row was already created from this batch.
Replace, remap, or delete the batch
Use Edit mapping when a header or source unit is wrong. Replace file starts with a different upload. Delete batch removes the staged import without deleting dives already committed.
After commit, open the created dives and verify sites, times, units, status, and optional details before treating the imported records as complete.
If something goes wrong
- If a CSV is detected as a profile, check whether its headers describe sampled elapsed seconds and depth rather than one dive per row.
- If all rows show errors, recheck the date, site, maximum-depth, duration, and unit mappings.
- If values are unexpectedly large or small, the selected depth or temperature source unit is probably wrong; remap before commit.