Skip to main content
Documentation
Open Resin
On this pageIn this sectionImport a design

Documentation

Getting started

Create a project, import an existing Altium or KiCad design with its libraries, and read through a project before editing it.

In this section

Create a blank project or import a KiCad or Altium design, then find your way around it.

01

Create or import your first project

Start a blank project, or import an Altium or KiCad design through the Upload, Preview, Options, and Review steps.

15 min · Beginner
02

Review an existing project

Read through a project's schematic, parts list, outputs, and history without changing it.

10 min · Beginner

Import an existing design

Import the whole project.

Include the libraries and models the design references, then check the imported result against the source before editing.

  1. 1. Gather the files

    The project file, every schematic sheet and board, and the local symbol, footprint, and 3D model libraries they reference.

  2. 2. Run the import wizard

    On the Projects page choose Import Project, upload the files or the project folder, and step through Preview documents, Import options, and Review and create project.

  3. 3. Check the result

    Compare sheet, component, and net counts, the layer count, and the board size with the source. Check which parts came through without a footprint.

Supported import files

Altium Designer
.PrjPcb, .SchDoc, .PcbDoc, .SchLib, .PcbLib, .IntLib
Schematics, boards, and libraries. Managed content, variants, and output jobs stay in Altium.
Altium CircuitMaker
.CMPcbDoc, .SchDoc
Boards and schematics saved by CircuitMaker.
Altium CircuitStudio
.CSPcbDoc, .SchDoc
Boards and schematics saved by CircuitStudio.
KiCad 9
.kicad_pro, .kicad_sch, .kicad_pcb, .kicad_sym, .kicad_mod
Opens as-is, with project-local libraries and 3D models.
KiCad 5 to 8
.pro, .sch, .lib, .kicad_pcb, .mod
Older projects are upgraded on import. Some converted legacy boards need further repair before reopening in KiCad; compare the imported board with the original.

Moving from Altium Designer

Test one representative Altium project, including its libraries, rules, variants, and downstream outputs, before moving production work.

  • The project, schematic, and PCB files for one known revision
  • Referenced symbol, footprint, database, or integrated libraries that policy permits you to use
  • The active variant, important rules, layer notes, and output-job requirements
  • Reference PDFs, BOM, fabrication, placement, and mechanical outputs for comparison
Version and migration notes
  • Managed content, database libraries, rules, variants, scripts, and output jobs may need separate handling.
  • The public CAN bus test files have a known pad-count mismatch between the Altium source and the imported result.

Moving from KiCad

Test one complete KiCad project directory with its local libraries, rules, models, and required outputs before changing the production toolchain.

  • The project file and every schematic and PCB file in the hierarchy
  • Project symbol and footprint tables plus project-local libraries
  • 3D models, custom rules, worksheets, text variables, and environment-path notes
  • Reference PDFs, BOM, fabrication, placement, and STEP outputs for comparison
Version and migration notes
  • Version upgrades, environment variables, library tables, plugins, and external generators can change the result.
  • Custom rule expressions and third-party automation need separate review.
  • Of the two public legacy-board examples, ScopeFun v2 meets all 27 conversion checks and CIAA-NXP meets 26 of 27; KiCad 9.0.7 fails to load the converted CIAA-NXP board, so neither is a complete migration record.

Need another format? Ask about your files.