CHECKING SALES STATUS…4 of 4 product gates verified · license packet 8/8 approvals · JP business use

EAGLE → KiCad migration audit

See the defined differences—and what was not checked.

BoardPort Audit is a read-only checker that compares the EAGLE source with the imported KiCad project before you continue editing. It lists what matches, what differs, and what software cannot judge.

On-device processingRead-only analysisNo calls or custom quote

Renderer-derived sample output

Inspect the actual report shape before using a design.

Release candidate 0.1.0-rc.1 generated the report bodies from BoardPort-authored synthetic inputs. Each linked public wrapper identifies that boundary. They prove output shape and repeatability—not accuracy on another board.

boardport-report-demo.htmlRC OUTPUT

MIGRATION COMPARISON

synthetic-difference

eagle-9.6.2 → kicad-10 · rules boardport-rules-0.2

Reviewrequired
0PASS
3DIFF
0NOT CHECKED
DIFF

Pad-net mapping · U1 pad 2

The synthetic EAGLE source is VCC while the KiCad destination is GND.

DIFF

Footprint reference set

The synthetic KiCad destination contains an additional U2 reference.

DIFF

Board outline and routing layers

The normalized synthetic board outline differs between the two files.

Use the standard tools too

A complement, not a replacement.

BoardPort Audit is not an importer or a design review. Its job is narrower: compare defined native-design facts across two formats and preserve the unanswered areas.

KiCad import report + ERC / DRC

GOOD FOR

Use them first. KiCad 10 can emit an import report and check the imported project against KiCad rules.

THE REMAINING QUESTION

They do not independently compare the saved EAGLE source with the resulting KiCad board under BoardPort’s three fixed rules.

Gerber comparison

GOOD FOR

Useful for comparing rendered manufacturing output.

THE REMAINING QUESTION

It does not independently compare the source pad-to-net map, footprint references, or normalized outline.

Human design review

GOOD FOR

Can judge circuit intent, safety, DFM, and context.

THE REMAINING QUESTION

Requires expert time, file sharing, scheduling, and an individual quote.

Minimum sellable product

A fixed comparison contract.

Locked first target: EAGLE 9.6.2 XML .brd, paired with KiCad 10.0 .kicad_pcb (validated with 10.0.6). Schematic files and other versions are outside the first release and must be reported as unsupported, never silently accepted.

Check IDCompared areaOutput rule
PAD_NET_MAPPINGFootprint reference, pad, and net mapping(reference, pad) → normalized net comparison
FOOTPRINT_REFERENCE_SETPlaced footprint reference setExact missing and destination-only inventory
BOARD_OUTLINE_AND_ROUTING_LAYERSBoard outline and routed copper layersNormalized line topology and routed-segment counts
PASS

Both inputs parsed and the displayed item matched under the stated rule. It does not mean the whole migration passed.

DIFF

A defined value, identifier, or connection differs. It is a review target, not an automatic defect verdict.

NOT CHECKED

Unsupported, ambiguous, missing, or unparsed. It is never included in a pass rate and never silently treated as safe.

Scope rationale: the official KiCad 10 CLI documentation documents JSON and text import reports. The KiCad EAGLE-format documentation lists unmapped layers and unsupported or ignored source concepts. The KiCad 10.0.6 release notes also include multiple EAGLE-import fixes. These sources establish reviewable differences—not demand, accuracy, or product completion.

Deliberately limited

The report narrows review. You keep the judgment.

Not included in the first product

  • Project conversion, repair, or Gerber generation
  • Circuit correctness or electrical safety review
  • Manufacturing, regulatory, EMC, or reliability approval
  • A replacement for KiCad ERC/DRC or Gerber comparison
  • Pre-v6 binary EAGLE files or every EAGLE/KiCad version
  • Files over 16 MiB each, pairs over 32 MiB, or runs over 30 seconds
  • Environments other than macOS 26.6.2 with Google Chrome 152.0.7977.66
  • Calls, custom engineering, or individual migration work

Straight answers

Before anyone pays.

Payment will not be used to decide whether the analyzer gets built. Product accuracy, the local-processing boundary, and delivery must be verified before the paid market test begins.

Does PASS mean the migrated board is safe to manufacture?

No. PASS means only that a displayed check matched under its stated rule and tolerance. It is not an electrical, safety, DRC/ERC, Gerber, or manufacturing certification.

Will the first product convert or repair my project?

No. The planned beta is read-only. You import with KiCad, then compare the source and destination. It will not edit either project.

Why show NOT CHECKED?

EAGLE and KiCad do not express every concept one-to-one. Unsupported, ambiguous, missing, or unparsed areas must stay visible instead of being counted as a pass.

Should I buy this for a simple two-layer board?

Probably not if KiCad import, visual review, ERC/DRC, and Gerber comparison already give you enough confidence. The first product targets maintained designs, custom libraries, and projects where review traceability matters.

Will I upload design files to use the product?

No. The target product is a downloaded offline package. Supported design files must be processed on the purchaser’s device without sending their contents to BoardPort.

Product first · paid test second

Working software before checkout.

The downloadable analyzer and its design-file network boundary now have artifact-bound evidence. The customer-license approval packet is prepared and 8/8 compound approvals are complete. The sale-candidate SHA and product review are complete. Purchase includes the fixed offline version, automatic download access after verified payment, and manual email support.