Export a few native rows and compare them with the supplied columns.
A small export from the target software reveals its delimiter, units and required fields. Compare that template with Channel, Name, FrequencyMHz, Modulation, Type, Category, DistanceMiles, Source, SourceDate, EmissionCode and LicenceNumber before mapping the larger list.
Important: FrequencyMHz is already expressed in MHz with a full stop decimal separator. Convert to hertz only if the documented target field requires it, and verify one familiar frequency before a full import.
Map the essential fields, retain useful context and validate a small batch.
- 1
Open the target importer
Choose its conventional-channel import or editor rather than a trunked-system, talkgroup or transmitter-programming workflow.
- 2
Set the CSV structure
Use comma separation, a full stop decimal point and row one as headings. Preserve quoted text rather than splitting names or sources that contain punctuation.
- 3
Map the required fields
Map Name to the channel label, FrequencyMHz to receive frequency and Modulation to receive mode. Use Channel only when the target needs a memory number.
- 4
Map optional context
Type distinguishes Analogue, Digital, Auto and Data / other rows. Category identifies the selected group; DistanceMiles is a local distance or UK-wide; Source, SourceDate, EmissionCode and LicenceNumber preserve the Ofcom context.
- 5
Check units with one row
Compare a known FrequencyMHz value with the target preview. If the target requires hertz, multiply the working-copy value by one million and confirm the result before repeating it.
- 6
Review repeated frequencies
Do not remove rows merely because the numeric frequency matches. Separate licence holders, sites or uses can legitimately share a frequency; compare Name, Category and Source first.
- 7
Select a safe first batch
Choose five to ten rows within the target receiver's bands and free-memory capacity. Remove unsupported modes or bands from the working copy rather than forcing them into the device.
- 8
Import, inspect and then expand
Complete the small import, verify labels and tuned frequencies, and only then add the remaining wanted rows. Save the successful result in the software's native format.
Confirm one known frequency, one local row and the rollback copy.
A familiar FrequencyMHz row tunes to the expected frequency and is not shifted by decimal, comma or hertz conversion.
At least Name and Modulation are correct, and optional Category, distance, source or snapshot information remains available where the target supports notes.
The chosen batch fits the device or software limit and the untouched pre-import native backup remains ready to restore.
Restore your backup: Close the changed configuration, reopen the native backup and write or save it through the target software's own recovery workflow. Do not treat the generic CSV as the rollback file.
If fields shift, frequencies fail or the importer removes rows.
The header becomes a channel
Set data to begin on row two or enable the importer's header-row option. Row one contains field names, not a frequency.
Frequencies are rejected
Confirm a full stop decimal separator and MHz units. Remove thousands separators and do not round away the channel spacing.
Repeated frequencies disappear
The target may enforce one row per frequency. Preserve the original CSV, review the different names and choose deliberately which assignment fits the limited target.
Digital rows do not decode
Type=Digital is a source classification, not confirmed protocol programming. The generic file does not provide dependable colour code, slot, NAC, talkgroup or encryption access.
An eleven-column audit-friendly CSV with assignment context.
The generated header is Channel, Name, FrequencyMHz, Modulation, Type, Category, DistanceMiles, Source, SourceDate, EmissionCode and LicenceNumber. Local rows carry a distance; national supplemental rows are labelled UK-wide.
Separate public assignments survive even when their frequencies match. The delivered file is not capped by one generic hardware limit, so the person importing it must choose a subset when the target has fewer memories or narrower receive coverage.
Questions
Which columns are essential?
Most importers need Name, FrequencyMHz and Modulation. Channel is useful for memory position; the remaining fields preserve mode, category, distance, source, emission and Ofcom licence context.
Why is DistanceMiles sometimes UK-wide?
Local rows have a calculated distance from the ordered location. National CB, PMR446, marine, common and other selected supplemental channels are not tied to one local transmitter site.
Can I delete repeated frequencies?
Only after comparing their names, categories and sources. Matching frequencies can represent separate assignments, so the source file intentionally preserves them.
Does a Digital row contain full decoder settings?
No. It identifies a broad digital discovery row but does not promise an exact protocol, colour code, slot, talkgroup or access parameter.
Will every row fit my device?
Not necessarily. Generic output is not capped to an unknown receiver. Filter by supported bands, modes and available memories in a working copy before import.