勛圖tv 繚 ENGINEERING REFERENCE
EasyEDA to KiCad: Migration Checks for Symbols, Footprints & Nets
Plan an EasyEDA-to-KiCad migration and compare the imported design against the source circuit and library intent.
Original engineering guidance 繚 References checked September 29, 2026
Migrate the design, then prove what survived
An EasyEDA to KiCad migration is a transfer of editable engineering information, followed by a comparison against the source design. Opening an imported board is only the first checkpoint. The useful result is a maintainable KiCad project whose circuit connections, physical footprints, manufacturing rules and release outputs have been reviewed. A successful-looking screen does not establish that the imported design is ready to manufacture.
Start by identifying the source edition and export format. EasyEDA Standard and EasyEDA Pro are different formats; a ZIP extension alone does not tell you which one is inside. Record the source application, exported project revision and destination KiCad version before selecting an import route. Preserve the original archive and work in a separate destination folder so that the comparison remains reproducible.
This page owns migration and verification. For an existing KiCad circuit that needs synchronization, follow the schematic-to-PCB update workflow. For final fabrication output preparation, use the KiCad Gerber and drill export guide. Keeping conversion, circuit synchronization and manufacturing release separate makes unresolved differences easier to locate and explain.
Identify the source package before choosing an importer
The versioned documents project import routes for EasyEDA Standard backups and Pro projects. It also distinguishes complete-project import from separate schematic or board import. Check that documentation against your installed release. Instructions written for an older KiCad release may describe a different set of supported formats, and a third-party conversion script may have its own additional restrictions.
| Available source | Intended route | Evidence to keep |
|---|---|---|
| Standard project backup | Version-supported Standard project import | Original backup and list of contained design documents |
| Pro project export | Version-supported Pro project import | Export edition, archive identity and source revision |
| Individual schematic or PCB file | Matching editor import where supported | Related document and library associations still to establish |
| Gerber and drill outputs only | Manufacturing reference or reconstruction scope | Missing editable circuit and rule information |
| PDF or board photograph | Human-readable comparison reference | Information that cannot be recovered from appearance |
Do not rename a file extension to make a file picker accept it. A JSON document can represent several different objects, and an archive can contain nested archives or unrelated revision files. Inspect the package inventory before importing. If the source provides multiple boards or schematic documents, decide which source pair belongs to the destination project rather than merging everything into one undifferentiated workspace.
The installed version used for this delivery is KiCad 10.0.6. The migration workflow here is based on its versioned documentation and explicit comparison tasks. Full EasyEDA Standard and Pro project equivalence has not been established by the separate KiCad schematic and export tests. The pin-comparison tool below is not a native-file converter, and it does not make that verification claim.
Keep a source baseline you can actually compare
Archive the source project together with custom symbols, footprints, assigned manufacturer part numbers and any special design notes. Keep reference manufacturing outputs if they are available, but identify their revision. A Gerber set from an older release is not a reliable baseline for the current source board. Include an assembly drawing or readable component placement view where orientation matters.
Capture a small inventory before conversion: schematic sheets, physical component references, net names, copper layers, outline dimensions, hole classes, population variants and unusual footprints. Identify features that deserve focused review, such as board-edge connectors, castellations, copper pours, non-plated slots, thermal pads and high-speed constraints. This inventory is more useful than a screenshot showing that an application opened without an error.
Preserve source and imported projects as different revisions while the review is open. Record the import date, application versions, warnings and any manual corrections. If a correction requires changing a footprint library or reconnecting a net, describe that change explicitly. Otherwise a later reviewer cannot distinguish importer behavior from edits made during troubleshooting.
For products with several physical boards, use a product-level manifest and separate board identities. The KiCad multi-board organization guide explains how to keep revision combinations and output folders distinct. Copy count, panelization and electrical design identity are separate decisions; migration should not silently combine them.
Compare circuit meaning before polishing the drawing
Begin with symbols and connectivity. Check reference designators, values, pin numbers, pin electrical types, power symbols, hidden pins and hierarchical connections. A symbol can look correct while a pin number maps to the wrong package pad. A changed automatically generated net name may be harmless, while an unchanged familiar label can conceal an unintended connection elsewhere in the circuit.
For a connector, compare its pin table with the interface definition. For an integrated circuit, compare the symbol pin numbers with the exact package variant. For a transistor or diode, check physical pin assignment and polarity rather than trusting a familiar graphic. Datasheet pin numbering, schematic identity and footprint pad numbering must agree for the actual part to be assembled.
Use electrical rule checking to find inconsistencies, then review the intended exceptions. Imported power definitions and pin types may produce warnings different from those in the source application. Do not suppress every warning just to obtain a clean status. Keep the reason for each accepted exception with the migration record, and distinguish unresolved problems from intentionally unused pins.
Next inspect the board geometry. Compare outline dimensions, cutouts, mounting holes, pad shapes, solder-mask openings, paste apertures, copper layers and component sides. Inspect zones after any refill because their clearance behavior depends on the destination rules. A zone's apparent boundary is not evidence that its final copper connects to the intended net or preserves the required isolation.
Compare a small source and imported pin list
Create two normalized CSV lists using Reference, Pin and Net columns. Enter one physical pin per row, with an explicit net label. The worksheet reports missing source pins, additional imported pins and changed net labels. It rejects duplicate pin identities rather than silently choosing one row. Use the result to focus a review on named differences and attach the findings to the migration record.
Source-to-import pin and net comparison
This is an exact-text comparison. It does not parse EasyEDA or KiCad project files, compare graph connectivity, inspect symbol types or evaluate copper geometry. If a net has been renamed, examine its connected pins before deciding whether the difference is an error. Document an approved name mapping in the engineering record; do not make arbitrary text substitutions only to remove a warning from this worksheet.
The example intentionally changes one net label so that the result is easy to understand. Replace all example rows with your own permitted data before treating the brief as a project record. Processing takes place in the browser tool without a file-upload step. Downloaded text must be attached manually to an enquiry; opening Contact does not transfer the entered rows or approve their contents.
Re-establish constraints and component implementation
Review the destination design rules against the intended fabrication construction. Minimum clearance, copper width, via dimensions and layer definitions need actual project values. An imported default does not prove that the source rule set was reproduced. Controlled impedance requires the agreed stackup and material data; matching the width displayed in the source editor is not sufficient evidence of electrical performance.
Footprint geometry deserves particular attention when the original part came from a supplier-linked library. Preserve the exact manufacturer part number and package drawing used for the design. Review pad numbering, pin-one markers, courtyard extent and exposed-pad treatment. A library nickname can change during import without changing geometry, while a familiar nickname may refer to a different physical package in another library.
For bottom-side parts, inspect orientation and text conventions in both the board and assembly drawing. Do not apply an automatic mirror merely because the two applications display a different view. Define the reference orientation and check a few asymmetric components, including a connector, polarized device and package with a distinctive pin-one feature. Use these as deliberate comparison points rather than judging orientation from a symmetric resistor.
The PCB DFM review addresses manufacturing questions once the migrated design and its intended construction are clear. DFM feedback cannot recover missing source intent by itself. Tell the receiving engineer which features were deliberately preserved, which were changed and which still require confirmation before a quotation can become a production release.
Regenerate coherent outputs from the reviewed destination
After the migration review, generate the fabrication and assembly outputs from the same approved KiCad revision. Avoid combining new copper files with a drill file, BOM or placement table inherited from the source application without a documented comparison. Such a mixed archive can contain internally plausible files that describe different physical builds. Keep superseded files outside the active release package.
Inspect Gerber and drill data together in a suitable manufacturing viewer. Compare the overall outline and at least several known hole or pad locations. Check layer functions, units, polarity, plated versus non-plated intent and any slots. A visually aligned outline alone does not establish drill-tool assignment or netlist correctness. State the netlist comparison requirement separately when it forms part of the fabrication agreement.
Prepare BOM and position outputs for the intended population variant. The KiCad assembly export and reference checks explain how DNP state, references, coordinates and side conventions can diverge. A not-fitted component may remain physically present in the PCB source, so its treatment must be consistent across purchasing, placement and the assembly drawing.
For a quotation, describe the board dimensions, quantity, material or stackup requirement, finish, assembly scope and outstanding migration questions. Send the controlled package for PCB manufacturing review. If the circuit itself is still being recovered or corrected, identify the files as engineering references rather than implying that production can proceed from them immediately.
EasyEDA to KiCad migration questions
Can Gerber files recreate the original schematic?
Gerber data describes manufacturing geometry, not the complete editable schematic, library system or circuit intent. It can support comparison or a separately scoped reconstruction, but it is not a lossless substitute for the original project. Keep the native source whenever possible and identify missing information before requesting conversion assistance.
Does a successful import mean the board is ready to order?
No. Import success establishes that the application produced a destination document. Review symbols, pin mapping, connectivity, geometry, rules, assembly variants and manufacturing outputs before release. Each check answers a different question; no single clean-looking display proves the entire design correct.
Are Standard and Pro archives interchangeable?
Treat them as distinct source formats and select the route supported for the actual edition and destination release. A shared ZIP extension does not establish identical content. Preserve the original package and record which import route was used so that warnings or unexpected results can be reproduced.
Should I fix changed net names in the worksheet?
Use the worksheet to identify differences, then inspect the native circuit. A renamed automatically generated net may connect the same pins, or it may reflect an actual wiring change. Resolve that distinction in the design and record any approved mapping; editing comparison text alone does not repair or validate the PCB.
What should I send when the conversion is incomplete?
Send a clear description of the source files, destination version, desired manufacturing or assembly scope and unresolved differences through the enquiry route below. Identify any screenshots or exports as reference-only. You can begin a technical discussion before completing every field in the worksheet, without presenting an unfinished migration as an approved build.
Bring a coherent revision to your engineering review
Send the board revision, construction, quantity and the file or design question you need reviewed. Identify unresolved requirements so the response can address them.
Send requirements for reviewOptional: attach the downloaded worksheet manually. This guidance does not operate CAD, verify electrical equivalence or approve manufacturing.