> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildwithtrace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing from Other EDA Tools

> Import schematics and PCB layouts from Altium, Allegro, gEDA/Lepton EDA, and PADS into Trace.

## Overview

Trace can import designs from several other EDA tools, converting them into KiCad-compatible formats that Trace works with natively. This lets you migrate existing projects or collaborate with teams using different tools.

Access importers from **File → Import** in the appropriate editor (schematic or PCB).

## gEDA / Lepton EDA

Trace imports gEDA and Lepton EDA schematic files (`.sch`).

### What Gets Imported

* **Components** — Symbols with attributes, values, and reference designators
* **Nets and buses** — Electrical connections between components
* **Text and labels** — Annotations and net labels
* **Graphical elements** — Lines, arcs, paths, and Bezier curves

### Symbol Resolution

The importer uses an 11-step search chain to resolve gEDA symbols to KiCad equivalents:

1. Exact name match in KiCad libraries
2. Attribute-based matching (device, value, footprint)
3. Pin-count and pin-name matching
4. 39 built-in symbol mappings for common gEDA components (resistors, capacitors, op-amps, connectors, etc.)
5. Fallback to generic placeholder symbols with correct pin counts

### RC/Config File Parsing

The importer reads gEDA RC files and configuration to resolve library paths and component search directories, so it finds your custom symbols automatically.

<Tip>
  After importing, review the schematic for any unresolved symbols (shown as rectangles with pin stubs). Assign the correct KiCad symbol from the library browser.
</Tip>

## Cadence Allegro

Trace imports Allegro PCB binary files, including the newer v18+ format.

### What Gets Imported

* **Footprints** — Component footprints with pads and courtyard
* **Padstacks** — Complex pad definitions including thermal reliefs
* **Vias** — Standard and blind/buried vias with full padstack data
* **Traces** — Routed tracks on all layers
* **Zone fills** — Copper pours with proper net assignment
* **Teardrops** — Teardrop pad connections
* **Differential pairs** — Paired routing with spacing preservation
* **Constraint sets and net classes** — Design rule assignments
* **Text** — Silkscreen text and fabrication notes
* **Layer mapping** — Allegro layers mapped to KiCad equivalents

### v18+ Binary Format

Allegro v18 and later versions use a restructured binary format with sequential keys and reordered headers. Trace handles both the legacy and v18+ formats automatically — no user configuration needed.

<Note>
  Allegro imports are PCB-only. Schematic import from OrCAD Capture is not currently supported.
</Note>

## Mentor PADS

Trace imports PADS ASCII format files for both PCB layouts and schematics.

### What Gets Imported

* **PCB layouts** — Component placement, routing, vias, and copper pours
* **Schematics** — Component symbols, net connections, and hierarchy (where available)

### Supported Formats

The importer handles the PADS ASCII export format. To import from PADS:

1. In PADS, export your design in ASCII format
2. In Trace, use **File → Import → PADS** and select the exported file

## Altium Designer

Trace imports Altium PCB and schematic files with expanded format support.

### What Gets Imported

* **Schematics** — Components, wires, buses, net labels, power ports, text, and graphical elements
* **PCB layouts** — Component placement, routing, zones, vias, mechanical layers, and board outline
* **Project variants** — Variant definitions from `.PrjPcb` files are imported into Trace's [Design Variants](/concepts/design-variants) system
* **Libraries** — Schematic symbols and PCB footprints from Altium library files

### Accepted File Extensions

Trace accepts all standard Altium PCB file extensions, including `.PcbDoc`, `.PCBDoc`, and other case variants. You don't need to rename files before importing.

## General Import Tips

1. **Run DRC after import** — Imported designs may have rule violations due to differences in how each tool handles constraints. Run DRC to catch issues early.
2. **Check footprint assignments** — Some components may need footprint reassignment if the source tool's library doesn't map cleanly to KiCad's.
3. **Verify net connectivity** — Open the netlist inspector to confirm all connections survived the import.
4. **Save as a new project** — Import creates new files rather than modifying your original. Save the imported project to a dedicated directory.

<Tip>
  The AI works on imported designs as-is — it resolves net and pin references against your design's actual naming (including unusual names imported tools produce) and asks rather than guesses when a reference is ambiguous. Projects imported with older versions of Trace are upgraded automatically the first time the AI edits them — no re-import needed.
</Tip>

## Requesting New Importers

If you need to import from a tool not listed here, let us know:

* Open a feature request on [GitHub](https://github.com/buildwithtrace/trace/issues)
* Ask in our [Discord community](https://discord.gg/UNUvQxneCr)
* Email [hello@buildwithtrace.com](mailto:hello@buildwithtrace.com)