
Autodesk 在 2023 年宣布 EAGLE 停服,最终日期定在 2026 年 6 月 7 日。新许可证停售、订阅停续,整个客户群被推向绑在 Fusion 360 里的付费 Fusion Electronics。很多团队对这套新捆绑不买账。EAGLE 项目最自然的归宿是 KiCad — 开源、永久免费、活跃开发,从 KiCad 6 起内置原生 EAGLE 导入器,开箱就能处理 .brd 板文件、.sch 原理图、.lbr 库。这篇讲清楚真正的迁移是什么样、哪里会翻车、结果怎么在信任它之前先验一遍。
EAGLE 文件是 XML — 板是 .brd,原理图是 .sch,库是 .lbr。KiCad 文件是 S-expression — .kicad_pcb、.kicad_sch、.kicad_sym、.kicad_mod。KiCad 导入器直接读 EAGLE XML 并输出对应的 S-expression。能搬过来的:板外框、铜层、走线、过孔、焊盘、铺铜、丝印、元件摆放、飞线、网络名、设计规则。需要二次处理的:封装库引用(EAGLE 封装 vs KiCad 封装)、3D 模型(EAGLE 不带,KiCad 要 .step 或 .wrl)、用 EAGLE ULP 脚本写的自定义 DRC。原理图符号能搬过来,但在你把它们重映射到真实符号库之前,会挂在 KiCad 的通用占位符上。
在信任转换结果前,把原 .brd 和新 .kicad_pcb 一起拖到 MakerSuite 3D — 30 秒视觉 diff 就能抓住导入器的静默回归。
免费试用 MakerSuite 3D2026 年 6 月 7 日停服不是营销话术 — 那天之后 EAGLE 不再激活新安装,老安装也失去对云端元件库的访问。离线 .exe 能继续跑,但新同事装不了、许可证没法转移、任何依赖云端库同步的团队工作流都崩。拖过截止日的团队会花时间维护死掉的工具链,而不是出板。正确做法是现在就转换活跃项目,留一台机器装个离线 EAGLE 当只读存档,新板从第一天起就在 KiCad 里做。
PCB 源文件装着你完整的设计 IP。把 .brd 或 .kicad_pcb 传到云端查看器在 NDA 项目里是风险。MakerSuite 3D 用 JavaScript 在浏览器里直接解析 EAGLE 和 KiCad 文件 — 不走服务器、不上传、不留缓存。一个标签页打开原 EAGLE .brd,另一个标签页打开转出来的 .kicad_pcb,并排对比。跟导入器作者内部用的是同一套解析逻辑,只是挪到客户端跑,板子不出你的机器。
Yes. Autodesk officially announced EAGLE's discontinuation in 2023 and set the final sunset for June 7, 2026. New license sales stopped earlier, subscription renewals are ending, and cloud library services shut down on the sunset date. Existing installs continue to run offline indefinitely, but without updates or cloud sync. Autodesk directs the customer base toward Fusion Electronics (formerly Fusion 360 Electronics), which is a paid subscription bundled into Fusion 360 rather than a standalone EAGLE successor.
Yes — it has been built into KiCad since version 6 (released 2022) and matured significantly in KiCad 7 and 8. The importer reads .brd, .sch, and .lbr XML files directly and produces native .kicad_pcb and .kicad_sch output. Nets, layers, component placements, zones, and design rules transfer reliably. The parts that need manual attention are footprint library remapping (EAGLE package names don't match KiCad footprint library paths) and 3D models (EAGLE doesn't ship models, you'll need to find KiCad-compatible .step or .wrl files). For a typical hobbyist or small-team board, expect to spend an afternoon on remapping after a clean import.
KiCad 8 can import .lbr files through File > Import > Non-KiCad Library. The importer splits the EAGLE library into KiCad's separated structure — .kicad_sym for schematic symbols and .pretty folders for footprints. This is useful if you've maintained custom EAGLE libraries for years. For parts covered by KiCad's official libraries (which are extensive), it's usually faster to remap to the official names than to maintain converted custom libraries. For truly custom packages (odd mechanicals, proprietary modules), converting the .lbr keeps your existing work intact.
No — EAGLE's ULP (User Language Program) scripting is specific to EAGLE's C-like embedded interpreter and has no direct equivalent in KiCad. KiCad uses Python for scripting (via the pcbnew Python API). If you have ULP scripts for BOM generation, panelization, or custom DRC, you'll need to rewrite them in Python. The good news is KiCad's Python API is more powerful and has broader community support, so most ULP use cases have established Python equivalents or open-source plugins.
Yes — MakerSuite 3D opens both EAGLE .brd and KiCad .kicad_pcb files directly in the browser. Drop the original .brd in one tab and the converted .kicad_pcb in another, and visually compare layer by layer. Any silent regression from the importer (missing zones, flipped layers, rotated parts) shows up immediately in the 3D view. No KiCad install required for the verification step, which is useful if you're auditing converted boards on a machine that doesn't have CAD software installed.
把 EAGLE .brd 或 KiCad .kicad_pcb 拖进来 — 视觉验证迁移结果
打开 PCB 查看器