Check the copy before importing it.

A file that reparses correctly can still describe the wrong contact. Use the new ADI and its manifest together, then test the result in a separate log before adding it to your working logbook.

1. Keep the two source exports. The manifest records source filenames, headers, output mappings and merged inputs, but does not contain the complete original files. Save all four files together. Your in-browser review disappears on refresh.
2. Reconcile the numbers. Input contacts minus merged pairs must equal output contacts. For the built-in sample, merging only W1AW gives 6 - 1 = 5. The manifest's outputSources tells you which source records produced each output. A retained unreviewed pair is intentional, not a failed export.
3. Check your station as well as the other station. CALL identifies the station worked. Review STATION_CALLSIGN, OPERATOR and applicable MY_* location fields separately. This bench's matching key does not include those fields. If two records came from different operators or locations, similar calls and times are not enough reason to combine them.
4. Inspect fields your logger relies on. Check contest exchange data, application fields, comments and QSL status on representative contacts. The bench preserves one-sided fields, but a receiving logger may handle them differently. N1MM Logger+ documents its own APP_N1MM_* fields and notes that a rescore may be needed after import. See its ADIF field documentation.
5. Try a separate destination log. Use your logger's documented test database or new-log workflow. Verify the record count and inspect merged and unmerged contacts. Importing into a log that already contains the source records can introduce duplicates; this tool cannot inspect your destination database.
6. Treat service submission as a separate step. QSO Merge Bench neither signs nor uploads logs. TQSL and LoTW have their own station identity and submission checks. ARRL explains multiple callsigns and locations and the required QSO fields. A successful local export does not establish award eligibility or service acceptance.

If the destination disagrees

Keep the originals, the exported copy and the manifest. Find the affected output record in outputSources, then inspect its original record numbers. Correct unsupported or inaccurate source data in the logger and compare fresh exports. Do not manually change ADI values without also recalculating their declared lengths.

This checklist is a review aid, not certification of any logger import. See the precise supported subset and the preservation policy.