BoardPort Audit — EAGLE to KiCad migration checklist
Updated: 14 September 2026
https://boardport.signalandship.com/eagle-kicad-migration-check

Free blank checklist. Fill it in and store it on your own device.
This file does not upload, convert, repair or validate a board.

BEFORE IMPORT: RECOGNIZE THE EXPECTED XML STRUCTURE
[ ] Preserve the original .brd; inspect a copy in a local text editor without saving changes.
[ ] Look for readable XML with an eagle element and a board inside drawing.
[ ] Read version on eagle. EAGLE 9.6.2 is the supported product profile; XML 1.0 is a different value.
[ ] If unreadable, missing or different: record compatibility as unconfirmed. Binary files and other versions are outside this product.
    Renaming the extension or editing version text does not convert a file.
    Recognizing tags does not validate the whole XML or guarantee KiCad import.
[ ] Preserve the source and import a copy in KiCad; save the destination as .kicad_pcb.

AFTER IMPORT: FIVE REVIEW ITEMS
1. Preserve the pair
   Source EAGLE version: ____________________
   Destination KiCad version: _______________
   Import date / local file locations: ________________________________
   Keep the first imported destination separate from later edits.

2. Check readability and scope
   Free local two-file check:
   https://boardport.signalandship.com/compatibility.html
   [ ] Record warnings and unsupported features: _______________________
   Reading success does not mean migration differences have been checked.

3. Review connections and references
   [ ] Compare changed pad-to-net mappings and added/missing references with the intended design and both files.
   Items to investigate: ______________________________________________

4. Inspect outline and routing
   [ ] Inspect the outline and routing in KiCad.
   BoardPort compares the defined normalized outline topology and routed-segment counts. Equal counts do not prove identical routes.
   Items to investigate: ______________________________________________

5. Keep unresolved checks separate
   [ ] Record each DIFF and NOT CHECKED and its next action.
   [ ] Run appropriate KiCad checks, inspect manufacturing outputs and complete human design review separately.
   Finding / next action / owner / result: _____________________________

REPORT MEANINGS
PASS: the stated rule matched; it is not approval of the whole migration.
DIFF: a difference to investigate, not an automatic defect verdict.
NOT CHECKED: a comparison could not be completed; never count it as PASS.

Free authored synthetic reports: use the guide link above.
The examples are not evidence of accuracy on customer boards.

PRODUCT SCOPE
EAGLE 9.6.2 XML .brd and KiCad 10.0 .kicad_pcb (validated with 10.0.6).
16 MiB per file / 32 MiB per pair / 30 seconds per run.
Three defined comparisons; no conversion or repair. Electrical behavior,
safety, ERC/DRC, Gerber equivalence and manufacturing suitability are not certified.
Check current OS, browser, language and purchase conditions on the site.

KICAD IMPORT AND REVIEW RECORD
[ ] Use project import when a matching .sch / .brd pair is available.
[ ] For the board alone, use Non-KiCad Board File import in PCB Editor.
[ ] Review layer mapping, stackup, rules and net classes against the source.
[ ] Refill zones; preserve DRC findings and unresolved review items.
KiCad imports EAGLE 6.x and later XML. This is broader than BoardPort support.
References:
https://docs.kicad.org/10.0/en/kicad/kicad.html
https://docs.kicad.org/10.0/en/pcbnew/pcbnew.html

DRC commands and finding triage:
https://boardport.signalandship.com/eagle-kicad-migration-check#drc-review
Free per-item review record:
https://boardport.signalandship.com/eagle-kicad-review-record.txt
Record exclusions, disabled rules and rerun evidence; never count unverified work as PASS.