Skip to main content

Migration guide / KiCad

Pilot an existing KiCad project in Resin.

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

Pilot steps
5
Source
KiCad
Current public fixture
Public legacy examples include parser and target-version failures
Download checklist All migration guides

Prepare the source

Collect one complete, reopenable project copy.

Use a representative project whose important design intent and required outputs are understood before import.

Bring these source materials

  • 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

Pilot sequence

Run these 5 steps in order.

Keep the original project untouched while you inspect and edit a working copy.
  1. 01

    Preserve the directory

    Archive the complete project and confirm it opens in the KiCad version that last saved it without an upgrade.

  2. 02

    Import a working copy

    Keep the directory structure intact and record unresolved libraries, paths, warnings, substitutions, and skipped objects.

  3. 03

    Compare the design

    Check hierarchy, power intent, connectivity, parts, board stack, pads, routing, zones, keepouts, rules, and models.

  4. 04

    Test editing and checks

    Make a representative schematic and PCB change, save, reopen, and compare ERC and DRC behavior.

  5. 05

    Inspect the outputs

    Generate the files your team needs and verify dimensions, layers, drills, placement, BOM, and mechanical content downstream.

Evidence and exercise files

Inspect the available KiCad fixture files.

Each repository-backed file is labeled with its contents, provenance, license or publication boundary, and current limitations.
Repository-backed file

KiCad import starter set

ZIP · 7 native inputs · 57 KB / GPL-2.0-only, GPL-3.0-only, and MPL-2.0

Provenance: Valid native KiCad files generated by Resin's Altium importers from pinned open-source source projects.

Current limit: Starter inputs are provided for a pilot; no separate portable Resin persistence result or broad KiCad-version compatibility claim is included.

Download file

Known limits

What this guide does not assume.

  • Version upgrades, environment variables, library tables, plugins, and external generators can change the result.
  • Custom rule expressions and third-party automation need separate review.
  • The public legacy-board examples include known target-version and footprint-value failures and should not be treated as passing migrations.

Next step

Keep the source tool available until the pilot works for your team.

A successful upload is only the beginning. Confirm the design, normal edits, checks, and downstream files before moving active work.
Inspect compatibility fixtures Add to the evaluation