Skip to main content

Importing Contacts

Hamtrax can import contacts from three file formats: ADIF, CSV, and Cabrillo. This lets you bring in logs from other software, contest submissions, or spreadsheet exports in just a few steps.

Getting to the import screen​

  1. Open the Logbook tab.
  2. Click the Import button in the header bar.
  3. You will see three import rows -- one for each supported format. Each row has a drop zone that accepts the matching file type and a Browse button to select a file from your device.

When you drop or select a file, Hamtrax detects its format (by extension first, then by content for .txt files) and opens the appropriate import view.

[SCREENSHOT: Import Manager showing the three format rows for ADIF, CSV, and Cabrillo]

ADIF import​

ADIF (Amateur Data Interchange Format) is the universal standard for exchanging ham radio logs. Use this for files exported from Log4OM, N1MM+, WSJT-X, or any ADIF-compatible logger.

Accepted file types: .adi, .adif, .txt

Steps​

  1. Drop your ADIF file onto the ADIF Import row, or click Browse and select it.
  2. Hamtrax parses the file and shows a preview with the number of contacts found.
  3. Choose a destination folder. Select an existing folder, or let Hamtrax create a new child folder named after your file (the suggested name is editable and creation is optional via a checkbox).
  4. Review contacts. Use the filter panel to narrow by band, mode, or date range. Toggle Skip Duplicates to exclude contacts that already match an existing log entry by callsign, date, band, and mode. You can also manually exclude or re-include individual contacts from the preview list.
  5. Click Import to save the included contacts to your log. A progress bar tracks the import.
tip

Hamtrax preserves all ADIF fields during import -- even non-standard ones. Unknown fields are stored in a rawAdifFields map, so when you export later those fields come back intact for round-trip fidelity.

CSV import​

CSV import is useful when your data comes from a spreadsheet or a logger that does not export ADIF.

Accepted file types: .csv, .txt

Steps​

  1. Drop your CSV file onto the CSV Import row, or click Browse.
  2. Hamtrax reads the headers from your file and opens a column mapping dialog. It auto-matches common header names (like callsign, band, mode) to Hamtrax fields using a built-in alias list.
  3. Adjust the mapping if any columns were not matched automatically. Your mapping is saved for future imports from the same account.
  4. Click Apply Mapping to generate the preview.
  5. Choose a destination folder, review contacts, and click Import.
info

Your CSV must include a header row. Required columns are callsign, date, and timeOn. If band is missing it defaults to blank; if mode is missing it defaults to SSB. Other columns like frequency, timeOff, rstSent, rstReceived, gridSquare, name, qth, country, state, power, and notes are optional.

Cabrillo import​

Cabrillo is the standard format for contest log submissions. Use this to import historical contest logs or logs exported in Cabrillo format.

Accepted file types: .cbr, .log, .txt

Steps​

  1. Drop your Cabrillo file onto the Cabrillo row, or click Browse.
  2. Hamtrax validates the file and extracts metadata (contest name, your callsign, operator category, grid square) from the header. This metadata is displayed in a banner.
  3. A preview shows all parsed QSO lines. Any lines that could not be parsed are listed as warnings.
  4. Choose a destination folder. Hamtrax suggests a folder name based on the contest name and your callsign (e.g., "CQ WW SSB - K1ABC").
  5. Review, filter, and click Import.
warning

Cabrillo files have a fixed-width column format. If the preview looks incorrect, the file may have been modified after export. Re-export from the original logger and try again.

Duplicate detection​

All three import formats support duplicate detection. In the preview panel, enable Skip Duplicates to automatically exclude contacts that match an existing log entry by callsign, date, band, and mode.

You can also manually exclude or re-include individual contacts from the preview list before confirming the import.

Syncing from external services​

In addition to file-based imports, Hamtrax can pull contacts from external logbook services. These integrations are available directly in the Import screen under Import from Services. You can also manage connector credentials from Settings > Connectors.

QRZ Logbook​

If you have a QRZ.com account with logbook data, Hamtrax can fetch your contacts directly -- no file download required.

  1. In the Import screen, find QRZ Logbook under the services section.
  2. If you have not set up QRZ yet, click Set Up to enter your QRZ API key. Credentials are encrypted locally using the WebCrypto API and never sent to Hamtrax servers.
  3. Unlock your vault with your passphrase, then click Import from QRZ.
  4. Hamtrax downloads your contacts and imports them into your log with duplicate detection (matching by callsign, date, band, and mode).
tip

If you already maintain a logbook on QRZ, this is the fastest way to populate your Hamtrax log -- no file export needed.

LoTW (Logbook of the World)​

Hamtrax can download your QSL confirmation status from ARRL's LoTW system. This is not a full contact import -- it updates the confirmation status of contacts you have already logged.

  1. In the Import screen, find LoTW under the services section.
  2. If you have not set up LoTW yet, click Set Up to enter your LoTW username and password. Credentials are encrypted locally.
  3. Unlock your vault and click Sync LoTW Confirmations. Hamtrax downloads your LoTW confirmation records and matches them to existing QSOs by callsign, date, band, and mode.
  4. Matched contacts are updated with LoTW confirmation status.
info

LoTW does not support uploading via API. To submit contacts to LoTW, export an ADIF file from Hamtrax and upload it through the TQSL desktop application.

Importing a past activation​

If you have an ADIF file from a previous POTA activation (or another activity program), you can import it as a complete activation record -- not just loose contacts. Hamtrax creates the activation, the activation folder, and imports all QSOs in one step.

Steps​

  1. Open the Logbook tab.
  2. In the folder tree, find the Activations category folder and click the + button next to it.
  3. In the New Activation modal, click Import Activation.
  4. Drop your ADIF file onto the drop zone, or click Browse Files to select it.
  5. Hamtrax parses the file and auto-detects activation metadata from the QSO records:
    • Activity type (e.g., POTA) -- from the MY_SIG field
    • Location reference (e.g., K-1234) -- from the MY_SIG_INFO field
    • Activator callsign -- from the STATION_CALLSIGN or OPERATOR field
    • Date range -- from the earliest and latest QSO dates
  6. Review and edit the detected fields. If the file does not contain MY_SIG / MY_SIG_INFO fields, you will need to fill in the activity type and location reference manually. The activator callsign and location reference are required.
  7. Preview the QSOs. The first 10 contacts are shown with callsign, date, band, mode, and park reference.
  8. Click Import [N] QSOs as Activation to confirm. A progress bar tracks the import.

When the import completes, Hamtrax will have:

  • Created an activation record linked to the park reference and your callsign
  • Created an activation folder in the Activations category (named in the standard callsign@reference-YYYYMMDD format)
  • Imported all QSOs into that folder with the activation ID, park reference, and MY_SIG / MY_SIG_INFO fields set
tip

This is the best way to backfill activations from before you started using Hamtrax. Export an ADIF file from POTA.app, your previous logger, or any other source, and import it here. Your activation history, folder organization, and award tracking will all reflect the imported data.

Offline importing​

You can import contacts even without an internet connection. Contacts are saved to your local database immediately and will sync to the cloud when you reconnect.

info

Large files (1,000+ contacts) may take a moment to parse and import. A progress bar shows the status during the import process.