1. Export a copy before you change anything
If the history already lives in a spreadsheet, Subsurface, or another logbook, keep that original file. A migration is easier to trust when you can compare the new records against the source instead of hoping the first import was complete.
2. Use CSV when you need a practical round trip
CSV is the DiveAtlas import path and one of the export options. It is the right choice for a spreadsheet-shaped history: dates, sites, depths, durations, and notes in columns you can inspect in any editor.
Open Data Transfer in the app, import the CSV, then spot-check a handful of dives from different trips before you treat the move as finished.
- Import dive records from a CSV file
- Export saved dives to CSV as an independent copy
- Compare dates, sites, depths, durations, and notes after import
- Keep the original source file until the sample looks right
3. Choose Subsurface XML and UDDF as distinct exports
DiveAtlas does not blend Subsurface XML and UDDF into one generic file. The Data Transfer screen offers them separately. Subsurface XML is the Subsurface-oriented export; UDDF is the Universal Dive Data Format export. Pick the format the destination tool documents rather than assuming the two files are interchangeable.
4. What this website does not do
DiveAtlas is a local-first logbook. The public website does not upload, convert, or inspect your dive files. The conversion happens on your device, which is why a small sample import is still worth doing before a full history move.
