Import from HAMRS
HAMRS supports ADIF in and ADIF out, but does not publish a supported third-party logbook-read API for Hamtrax. The supported migration path is to export your HAMRS logbook as an ADIF file.
Export the logbook from HAMRS
- Open HAMRS and select the logbook containing the contacts you want to move.
- Open the Logbook Actions menu on the logbook page.
- Select Export ADIF.
- Save or share the resulting
.adifile somewhere accessible to Hamtrax.
HAMRS ships on web, mobile, and desktop, so the save or share sheet after export follows the platform you are using. The current HAMRS release consolidates its logbook-page actions in the Logbook Actions menu.
What to expect from a POTA-typed HAMRS log
HAMRS logs are typed — you pick POTA, and it writes MY_SIG=POTA onto every record in that logbook, including the hunts you made from home where no park of your own was involved. That bare code names no park, so it identifies no activation, and Hamtrax drops it: your hunts file into their monthly Hunting folders the way they should, and nothing is collapsed into one custom folder for want of a park reference that was never there.
Rows that do carry a park in MY_SIG_INFO are untouched and still file as activations. See how contacts are sorted for the full rule.
Continue in Hamtrax
Open Import any logbook, choose Import from file, and use Browse Files for the exported .adi file. That page is the maintained source for every later Hamtrax-side step and avoids duplicating instructions here.
Official HAMRS references
Last checked against HAMRS's public 2.52 product and release information on July 18, 2026. Hamtrax is independent from Cabin Interactive, LLC and is not endorsed by or affiliated with HAMRS.