Skip to main content

Import from Ham2K PoLo

The supported path from Ham2K Portable Logger (PoLo) to Hamtrax is Full ADIF Export. PoLo does not publish a supported third-party logbook-read API for Hamtrax to connect to, so Hamtrax does not request PoLo account credentials.

Export an operation from PoLo​

  1. Open PoLo and select the operation containing the contacts you want to move.
  2. Open the Operation tab.
  3. Select Export Log Files.
  4. Choose Full ADIF Export. Activity-specific files are optimized for submitting to services such as POTA or SOTA and may intentionally omit fields; Full ADIF Export produces PoLo's broadest standard ADIF file.
  5. Save or share the resulting .adi file somewhere you can select from Hamtrax.
Review private data before importing

PoLo warns that Full ADIF Export can include personal lookup data and private QSO notes. Hamtrax can preserve names, locations, and comments from an ADIF file, so inspect the export and remove anything you do not want stored in Hamtrax before importing it.

Continue in Hamtrax​

Open Import any logbook, choose Import from file, and use Browse Files for the exported .adi file. The general import page remains the single maintained source for Hamtrax's review, organization, and finalize steps.

PoLo also places APP_HAM2K_* operation and timeline events between its contacts. Hamtrax deliberately ignores those event-only fields — including an oversized event payload — so they cannot attach to or cause the following QSO to be skipped. Actual QSO fields such as names, locations, and comments are still preserved, so the private-data warning above still applies.

Official PoLo references​

Last verified July 18, 2026. Hamtrax is independent from Ham2K Technologies and is not endorsed by or affiliated with Ham2K PoLo.