OpsLog/wiki/Import-and-Export-ADIF.md

Import and Export ADIF

OpsLog is ADIF 3.1.7 compliant: a full field dictionary, 30 promoted columns, a generic "extra fields" editor for anything not promoted, and standard/all export modes.

Import

Import an .adi / .adif file into the active profile's logbook. On import, OpsLog parses every field, maps standard fields to columns and keeps unknown but valid ADIF fields in a per-QSO extras store (editable later). Country / zones are enriched from cty.dat where missing. A file without a header (records pasted from another log) imports fine.

• Field remapping: the import dialog can move a field as it reads it — e.g. the RSGB IOTA contest exports the island reference in STATE; add a STATE → IOTA row and it lands where the award looks.
• Fill from profile: optionally stamps your station fields and your default confirmation statuses (paper QSL, LoTW, eQSL, Club Log, HRDLog, QRZ.com) on QSOs the file leaves empty — a WSJT-X log carries almost none. Existing values are never overwritten.

Export

• Whole log, selected rows, or the filtered view (no limit) — see Recent QSOs and Filters.
• Standard mode exports the common promoted fields; All mode also exports every extra field; Choose fields… opens a picker that separates the official ADIF 3.1.7 fields (by category) from the OpsLog / non-standard tags actually present in your log, with All/None per group. Your selection is remembered.
• Cabrillo export for contest submission.

Round-trip safety

Award references you assign manually are stored in an ADIF extra field (APP_OPSLOG_AWARDREFS), so exporting your full log and re-importing it does not lose your award-reference assignments.

Tips

• To move a batch of QSOs between logs, export selected → import into the other profile.
• Use Find duplicates (Tools) after importing to catch overlaps.