FEDEVEL
Platform forum

Gino , 05-19-2026, 12:38 PM

We recently moved from OrCAD to Altium and are trying to migrate our existing component libraries into Altium.

We have an existing component database for the schematic libraries, and the schematic symbols are available as .OLB files. However, our PCB footprint libraries are in .DRA format.

When I try to use Altium’s Import Wizard for OrCAD libraries, the footprint library filter only accepts:

Schematic Libraries *.OLB
Footprint Libraries *.LLB

Because of this, the .DRA footprint files are not detected or accepted in this import flow.

Has anyone migrated this kind of setup before — OrCAD schematic database/libraries together with Allegro .DRA footprints — into an Altium database/library system?


Should .DRA footprints be imported through the Allegro importer instead of the OrCAD library importer?
Is there a way to convert .DRA footprints into a format Altium can use?

, 05-19-2026, 12:43 PM

🤖 In the meantime, here’s a response from the [FEDEVEL AI HW Assistant]().
It helps to find relevant resources for your question, but it may make mistakes as it’s still in early development.

This is the response from the AI Assistant:
The migration path from OrCAD/Allegro to Altium requires specific handling of .DRA footprint files. Here's the technical reality:

1. **File Format Compatibility**
Altium's OrCAD importer only accepts .LLB (layout library) files for footprints, not native Allegro .DRA files. The .DRA format requires using Altium's **Allegro importer** instead. This is a separate import path designed for Allegro board files (.BRD) and libraries.

2. **Conversion Workflow**
To migrate .DRA footprints:
- **Export from Allegro**: Use Cadence's "Export -> Libraries" to generate ASCII files (.PAD for pads, .DRA for symbols)
- **Import to Altium**:
- Use *File -> Import Wizard*
- Select "Cadence Allegro Design Files"
- Follow prompts to map Allegro layers to Altium's layer system
- Expect to manually verify critical features like padstacks and keepouts ([Example conversion process](https://www.youtube.com/watch?v=Ng4n_lN_oPc&t=1113))

3. **Critical Considerations**
- **Layer Mapping**: Allegro's layer structure differs significantly. Prepare for manual adjustment of:
- Silkscreen layers
- Solder mask/paste expansions
- 3D model associations
- **Padstack Translation**: Allegro's complex pad definitions may require recreation in Altium's pad properties
- **Script Assistance**: Consider using Altium's scripting engine (DelphiScript) to automate repetitive adjustments post-import

4.

, 05-19-2026, 12:43 PM

**Alternative Approach**
For critical footprints, manual recreation in Altium using:
- IPC-7351 land pattern calculator
- Component wizard for standard packages
- Cross-reference with original .DRA via PDF printouts

While time-consuming, this ensures proper DFM compliance with Altium's design rules ([Footprint creation example](https://www.youtube.com/watch?v=wxYbIGV9_CY&t=1889)).

5. **Database Migration**
For schematic symbols:
- Use Altium's OrCAD .OLB importer first
- Then manually relink to converted footprints
- Verify pin mappings and designator consistency

Pro Tip: Maintain a cross-reference spreadsheet during migration to track:
- Original vs new footprint names
- Layer mapping exceptions
- Component parameter translations

The process is non-trivial but manageable with careful planning. Budget time for iterative verification and be prepared to handle complex footprints on a case-by-case basis.

You can continue chatting with the AI Assistant here:
https://fedevel.com/hw-assistant