EAGLE Gerber Export: Preserve Legacy Designs and Use Fusion

Preserve the board and schematic together

Keep the original board, schematic, libraries, design rules and CAM job settings in a read-only archive before migration or editing. Identify the last approved revision and any release notes. A board file found in a downloads folder may be a review copy rather than the source used for the previous build.

Check whether the schematic and board belong together. A design can contain a recognizable layout while its paired schematic has changed. Do not resolve a mismatch by deleting whichever file is less convenient. Establish which source is authoritative and review the differences before exporting a new package.

Collect prior manufacturing outputs as comparison evidence. They can help confirm outline size, layer count and hole relationships, but they are not automatically the current design. Keep original and newly generated archives clearly separated so a later reviewer does not unknowingly combine revisions.

Choose a supported route for the available environment

If you are maintaining an old environment, establish its actual version, access and licensing status before following a legacy procedure. The retirement notice means you should not assume the application can simply be downloaded and used as it was years ago. This page does not claim to have exercised a legacy EAGLE installation.

For a current Fusion route, consult Autodesk's version-appropriate migration and electronics documentation, then verify the imported design. The current manufacturing documentation describes CAM Preview, CAM Processor and CAM Export in Fusion Electronics. Those controls should not be confused with identically purposed but differently organized legacy screens.

Migration needs more than a successful open operation. Compare source pairing, layer definitions, device libraries, copper pours, board geometry and manufacturing settings. Record unresolved differences and give the derivative its own revision when changes are made. A format transition should not conceal a design change.

Manufacturing release manifest comparison

Prepare the design for manufacturing output

Review the intended construction and enter the applicable design constraints. Check board shape, copper layers, vias, holes and relevant mask or legend content. Recalculate design-dependent objects where required by the chosen application, then inspect the result. A stale copper pour can make the saved editor view and exported data disagree.

Run the relevant rule and consistency checks, keeping meaningful exceptions documented. A clean DRC result only covers the rules enabled and configured for that run. It does not approve component choices, electrical performance or every receiving requirement. The companion DRC guide explains how to turn errors into specific review actions.

Freeze the source state before generation. If a change is made during export, regenerate the related package coherently. Do not send a current top layer together with a drill file from an earlier run simply because both have familiar filenames.

Inspect the CAM job and selected output scope

Map each output to its physical role and the intended copper stack. Include required drill and routing information, together with the finished outline and construction notes. Paste, mask, legend and assembly drawings serve different tasks; not every available layer belongs in every manufacturing order.

In the documented Fusion workflow, CAM Preview and the CAM Processor provide opportunities to inspect the job before producing the archive. Review the actual template and generated content rather than assuming that automatic layer-count recognition handles every special feature. A blind-via design or an unusual profile needs deliberate scope confirmation.

Keep units, origins and side conventions consistent across related outputs. Do not manually mirror a bottom layer merely because an old screenshot appears reversed. Manufacturing data and human-readable underside views can use different display conventions. Resolve the intended interpretation in the receiving view.

Verify the exact files you intend to deliver

Load the generated archive in an independent viewer or receiving CAM workflow. Inspect layer order, outline, drill-to-pad alignment, mask openings and important local features. Compare known dimensions with the approved design. A ZIP opening successfully does not prove that the selected files cover the build.

Use the manifest worksheet to list actual files, assigned roles and revision labels. Its sample intentionally includes a stale revision. The tool reports missing declared roles and inconsistent labels, but it cannot inspect a file's geometry or determine whether its name is truthful. Keep the independent view as a separate check.

If you provide Gerber and another format, identify the authoritative package and confirm both came from the same source state. Alternative formats can assist review, but unlabelled duplicates create uncertainty. The ODB++ versus Gerber comparison helps decide what the recipient actually needs.

Complete the release and quotation brief

Retain the native source, chosen environment, CAM configuration and inspected archive in the engineering record. Provide the manufacturer the required release files and concise construction requirements. Add quantity, material constraints, finish, special features and any open questions that could affect the proposal.

For assembly, add the selected variant BOM, placement data and instructions rather than assuming the fabrication archive defines the populated product. The PCBA file checklist identifies that additional scope. A shared copper design can still have several different assemblies.

This guide combines official retirement and manufacturing documentation with a locally tested manifest tool. It does not claim a native EAGLE-to-Fusion migration test. Preserve that distinction when evaluating an old design: the goal is a traceable, reviewed release that the receiving engineer can interpret, not simply a new ZIP with a current date.

Keep an archive decision log

Record the original environment, source identity and the evidence supporting each interpretation. Note whether a result came from an intact native project, a migration, a fabrication archive or a drawing reconstruction. Those starting points preserve different information and should not receive the same approval label.

For each unresolved item, identify the missing evidence and the consequence of proceeding without it. A successful import can be an intermediate milestone while plane behavior, library mapping or output settings remain uncertain. Retain the original and give any repaired or migrated derivative a distinct identity. When a later reviewer opens the project, the record should explain what was changed deliberately, what was merely translated and what still needs a decision.