Skip to main content

Migration guide / Altium Designer

Pilot an existing Altium Designer project in Resin.

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

Pilot steps
5
Source
Altium Designer
Current public fixture
Public fixtures include a known pad-count mismatch
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, 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

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 source

    Archive a copy that still opens in the Altium version that last saved it. Keep the original untouched.

  2. 02

    Import once without edits

    Upload a working copy and review every missing file, substitution, warning, and skipped object before changing the result.

  3. 03

    Compare the design

    Check hierarchy, connectivity, component fields, variants, board geometry, layers, pads, routing, zones, and mechanical features.

  4. 04

    Test a normal edit

    Make a representative schematic and PCB change, save, reopen, and rerun the checks your team requires.

  5. 05

    Inspect the outputs

    Generate the required BOM, fabrication, assembly, and mechanical files and open them in the receiving tools.

Evidence and exercise files

Inspect the available Altium Designer fixture files.

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

Altium pilot source set

ZIP · 7 source files · 3.0 MB / GPL-2.0-only, GPL-3.0-only, and MPL-2.0

Provenance: Sanitized sources retained from three open-source projects at pinned upstream commits; full license texts are included in the fixture library.

Current limit: Use only as controlled importer fixtures. The set is not representative of every Altium version, object type, library system, or production design.

Download file
Repository-backed file

Altium conversion results

ZIP · 14 results and reports · 62 KB / GPL-2.0-only, GPL-3.0-only, and MPL-2.0

Provenance: Converter-produced KiCad-format results and machine-readable reports generated by Resin's committed Altium importers from the paired sources.

Current limit: Reports check counts rather than complete fidelity. One CAN-shield PCB report scores 88% because source pad count is 32 and output pad count is 5.

Download file

Known limits

What this guide does not assume.

  • Managed content, database libraries, rules, variants, scripts, and output jobs may need separate handling.
  • A visually similar result does not prove identical connectivity, pad geometry, or constraints.
  • The public CAN fixture currently has a disclosed source-to-result pad-count mismatch and should not be treated as a passing migration.

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