BoardPort Audit — EAGLE to KiCad DRC and migration review record
Updated 14 September 2026
https://boardport.signalandship.com/eagle-kicad-migration-check#drc-review

Free blank record. Fill it in and keep it locally; it sends no data and runs no checks.
An import log, BoardPort comparison and KiCad DRC answer different questions.
This record and a DRC exit status do not approve the whole migration, electrical
behavior or manufacturing suitability.

1. Freeze the inputs
Original EAGLE filename, revision and storage location:
First KiCad import filename and import date:
Review copy filename, revision and storage location:
KiCad version / OS:
Accompanying .kicad_pro / custom rules / external libraries:
Confirmation that the original and first import were not overwritten:

2. Check configuration (a blank remains unverified)
Reviewed copper layers and stackup:
Net classes, applicable rules and clearances (values, units and evidence):
Zone settings and refill method:
Disabled rules, exclusions and reasons:
Schematic parity: not run / run (schematic revision and report:                 )
A board-only check does not verify a missing schematic.

3. Execution and reports
Documented KiCad 10.0 example; record your own execution below.
Use a review copy and a new output filename. Quote paths that contain spaces.

kicad-cli pcb drc \
  --format json --output migration-drc.json \
  --severity-all --all-track-errors --refill-zones \
  --exit-code-violations imported.kicad_pcb

The line continuations above use POSIX shell syntax. In PowerShell or another
shell, remove the trailing backslashes and join the command onto one line.
Record the exit status immediately after running it:
POSIX shell: echo $?
PowerShell: $LASTEXITCODE
With --exit-code-violations: 0 means no reported violations; 5 means violations.
Investigate other nonzero codes as execution failures. Check that a new, readable
report was created; an old report is not evidence of the current run.
--severity-all includes errors, warnings and excluded violations.
--refill-zones does not save the refilled board unless --save-board is also used.
This example omits --save-board.

Run date, time and timezone:
Actual command and working directory:
Exit status:
New DRC report location and modification time:
Import log location:
BoardPort HTML/JSON location (only if used):

4. Per-item review (copy this block as needed)
Item ID:
Found by: import log / BoardPort DIFF / BoardPort NOT CHECKED / KiCad DRC / human review
Original finding text, severity and exclusion state:
Source location (reference / pad / net / layer / coordinates):
Destination location (reference / pad / net / layer / coordinates):
Intended design or required value and units to verify:
Evidence (source design, schematic, fabrication constraints; revision and location):
Next action and owner:
State: unverified / investigating / corrected-awaiting-recheck / intentional difference recorded / closed with evidence
Edit or decision (merely hiding a finding leaves it unresolved):
Corrected board revision:
Rerun date, new report location and remaining findings:
Evidence for closure, reviewer and date:

Triage prompts
- Unconnected items / changed nets: compare the reference, pad and intended net in both boards.
- Clearance / zones: inspect the layer, rule, net class and zone settings. Use values
  justified by the design and fabrication requirements; there is no universal migration clearance.
- Outline / layers: inspect Edge.Cuts gaps or overlaps and copper-layer assignments against the source.
- Schematic parity: check separately when the migrated schematic and PCB exist; retain the result.
- Exclusions: retain reasons and decisions. An exclusion is not a repair.

5. Outstanding review
Unresolved IDs and next actions:
Disabled-rule and exclusion review still open:
ERC / schematic parity / fabrication-output / electrical / human design review still open:
Next owner and planned date:
A BoardPort PASS only means its stated rule matched. Never count NOT CHECKED as PASS.

Reference (KiCad 10.0 CLI documentation checked 14 September 2026):
https://docs.kicad.org/10.0/en/cli/cli.html#pcb_drc
The public Pressure module's archived import log has zero zones. Its BoardPort
results are not evidence of DRC, zone, schematic or manufacturing validation.