An EAGLE 6 project should be treated as a legacy design release. Before migrating it, preserve the schematic, board, libraries and manufacturing outputs that belong together. The practical question is whether the migrated project represents the same circuit and build configuration, not whether a historical feature list sounds current.
Check the applicable software and license status
Autodesk states that EAGLE sales and support ended June 7, 2026. Its announcement distinguishes earlier perpetual licenses from subscription entitlements and says pre-acquisition perpetual versions continue to function on their current machine. Check the terms applicable to the particular installation; do not assume every EAGLE user has the same access. See the official EAGLE status and migration FAQ, reviewed October 2, 2026.
This guide does not recommend unofficial installers or promise compatibility with every operating system. Work from legitimately available project files and the supported import instructions for the destination tool. Keep a read-only copy of the original release before saving a converted version.
Build an archive manifest
| Artifact | What to record |
|---|---|
| Schematic and board | File names, revision and known matching pair |
| Libraries | Used symbols, footprints and device mappings |
| Design rules | Clearance, width and via settings used for release |
| CAM configuration | Layer mapping, drill export and output conventions |
| Manufacturing package | Released Gerbers, drills, drawings and BOM |
| Exceptions | Approved rule waivers and unresolved issues |
Review libraries separately from board geometry
Autodesk documents separate paths for importing EAGLE libraries and local .lbr files into Fusion. Follow the appropriate route in its library import documentation. A successful import is a starting point for review, not evidence that every package assignment matches the intended purchased part.
Check pin-to-pad mappings, package variants, polarity and reference designators against the approved BOM and component drawings. Flag any automatic library update that changes the design. Give the converted project a distinct revision until those changes are accepted.
Compare the manufacturing result
- Confirm the board outline, units and origin.
- Compare copper-layer count and assignment.
- Check drill sizes, plated versus nonplated holes and slots.
- Review solder mask, paste and legend layers.
- Reconcile net connectivity and remaining unrouted connections.
- Compare BOM population and placement exports.
- Review any differences in exported fabrication data before release.
For example, a migrated board may look correct on screen while its CAM job exports a different layer selection. Comparing the released fabrication package can reveal that difference before it reaches manufacturing. Keep the discrepancy, its owner and its resolution in the release record rather than silently replacing the original outputs.
Can old manufacturing files be used directly?
A complete previously released package may support a repeat order if it still represents the approved product, but a design change requires a new controlled release. Confirm component availability and the supplier’s acceptance of the construction. A file opening successfully does not establish electrical correctness or current manufacturing readiness.
See PCB layout handoff requirements and DFM review. Request a manufacturing review with the released outputs, design revision and a list of migration differences.