Skip to main content

Resources / Migration

Pilot one representative project before moving production work.

Choose the source tool, preserve the original project, import a disposable copy, compare the engineering objects that matter, and verify the downstream output path.

Source guides
2
Method
Source to inspected result

Choose a source

Use the guide that matches the project you control.

Altium Designer5 pilot steps

Altium Designer migration

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

Current fixture status: Public fixtures include a known pad-count mismatch.

Open guide Checklist
KiCad5 pilot steps

KiCad migration

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

Current fixture status: Public legacy examples include parser and target-version failures.

Open guide Checklist

Shared method

Four stages for any migration.

  1. 01

    Preserve the source

    Archive the exact revision, source-tool version, project files, libraries, dependencies, and generated baseline outputs.

  2. 02

    Import a disposable copy

    Keep every warning and error. Do not modify the source archive or edit around the first import result.

  3. 03

    Compare engineering intent

    Inspect hierarchy, connectivity, parts, board geometry, layers, routing, rules, variants, and critical mechanical features.

  4. 04

    Test editing and outputs

    Make a controlled change, save and reopen it, rerun checks, and inspect the files required by downstream tools.

Important

Keep the source tool authoritative until the pilot passes.

A successful upload is not the same as a successful migration. Preserve the original project and record any object, rule, or output that does not survive the test.
Review supported formats Inspect compatibility fixtures