EDA MIGRATION INFRASTRUCTURE
The accountable way to migrate from Altium to KiCad.
Convert, repair and validate your Altium board — without wondering what got lost.
Free analysis on one Altium .PcbDoc — the board file the migration accepts at launch, binary or ASCII text — or a .zip of the project, which is opened for the one board inside it. You sign in with your email; nothing is charged until you unlock a migration.View methodology
CROSSPAD · MIGRATIONCP-04281
ALTIUMMotorController.PcbDoc
IMPORT
COMPARE
REPAIR
VALIDATE
KICADMotorController.kicad_pcb
- ComponentsVerifiedVERIFIED
- Nets & connectivityVerifiedVERIFIED
- Copper fillsFixed and re-checkedREPAIRED_AND_REVALIDATED
- KeepoutsNeeds your callENGINEERING_DECISION_REQUIRED
REVIEW_REQUIREDevery object class reported by state
INDEPENDENT SOURCE ANALYSISSEMANTIC SOURCE → TARGET COMPARISONDETERMINISTIC VALIDATIONAUTOMATIC REPAIR
Why Crosspad exists
Import isn’t the same as migration.
KiCad can import Altium. Crosspad verifies what happens next.
01
IMPORT
Use the best available migration path for the project.
02
COMPARE
Analyze source and destination independently.
03
REPAIR
Correct known migration discrepancies.
04
VALIDATE
Verify critical engineering invariants.
Accountability
Every component. Every net. Every rule. Accounted for.
| OBJECT CLASS | WHAT IS CHECKED | REPORTED AS |
|---|---|---|
| Components & designators | Every designator present in source and target, footprint by footprint. | VerifiedVERIFIED |
| Nets & pin connectivity | Every net and every pin-to-net assignment matched against the source. | VerifiedVERIFIED |
| Copper layers & layer mapping | Each source layer mapped to a KiCad layer; the mapping is stated. | Expressed differently in KiCadTRANSLATED_EQUIVALENTLY |
| Board outline & geometry | The outline is present, closed and on Edge.Cuts. | VerifiedVERIFIED |
| Footprints & pad geometry | Pad shapes, sizes and stacks compared per footprint. | VerifiedVERIFIED |
| Tracks, arcs & vias | Geometry and net assignment compared, layer by layer. | VerifiedVERIFIED |
| Fills & zones | Net, layer and clearance restored where dropped, then the affected domains revalidated. | Fixed and re-checkedREPAIRED_AND_REVALIDATED |
| Design rules & net classes | Membership accounted for; rules mapped where a KiCad rule exists. | Fixed and re-checkedREPAIRED_AND_REVALIDATED |
| Differential pairs | Naming and membership compared; high-speed intent is named, not guessed. | Needs your callENGINEERING_DECISION_REQUIRED |
| 3D model references | Presence of each referenced model, not visual fidelity. | Needs your answerACTION_REQUIRED |
| Legacy ASCII .PcbDoc source | Converted to the binary form, then reconciled against an independent count of your board. | Expressed differently in KiCadTRANSLATED_EQUIVALENTLY |
| Pre-V6 (Protel) source | Named unsupported up front — never silently skipped. | Out of scopeUNSUPPORTED |
| Everything else in a zipped project | The one .PcbDoc inside the archive is migrated; the sheets, the .PrjPcb and the libraries beside it are listed and left alone. | Out of scopeUNSUPPORTED |
| Every validated domain, reported by evidence categoryIf we can’t verify it, we don’t mark it safe. | ||
The report structure: every object class and the state it is reported in. Scroll to see all columns
Migration report
Know exactly what changed.
Every Crosspad migration produces evidence — not just output files. A report your team can archive, review and sign off on.
Silent failure
What you don’t see is the dangerous part.
A project can look correct after import while still losing engineering intent.
SOURCE
Keepout applied
TARGET
Keepout restriction changed
detectedDETECTED
SOURCE
Differential pair defined
TARGET
Ordinary nets
review requiredREVIEW REQUIRED
SOURCE
Copper fill on a net
TARGET
Fill present, net lost
repairedREPAIRED
SOURCE
Every net in the source
TARGET
One net fewer, no error
criticalCRITICAL
Free tools
Inspect before you migrate.
MotorController.PcbDoc
PowerStage.SchDoc
scan — MotorController.PcbDoc
Migration Compatibility Scan
See what migrates cleanly and what needs review — before committing.
.PcbDoc
Open free tool1 projectA single legacy board
5 projectsA product family
10 projectsA team switching tools
Company archiveFull historical migration
ARCHIVES · ASSESS, THEN QUOTE
- 01Assessed — Every project in the archive is analyzed before a quote.
- 02Classified — Each one is named completable, guided, decision-needed or unsupported.
- 03Billed on eligible scope — You are never billed for what can’t be finished.
Scale
Built for real engineering migrations.
Crosspad works whether you’re moving one legacy board or an entire Altium archive.
From$179/project
$179 per project in a 10-project pack; $249 for a single project. Larger archives are quoted after a free assessment.
View pricingSecurity
Your PCB is your IP.
—The web application never runs the migration engine. It creates a job through the API and receives the result asynchronously.
—The container worker is designed to run without network access, as a non-root user, with a read-only runtime and resource limits. Job scratch space is removed after each run.
—Where live processing is enabled, retention follows the policy’s schedule: an analysis-only upload is deleted within 7 days after the upload, an order’s source file within 30 days after delivery or order closure, and the delivery bundle after its 90-day Download Period — a non-content hash may be retained. You can request deletion from your account email.
—No customer file is sent to an external AI or machine-learning service, and customer files are never used to train models.
PROCESSING PATH · as described in the Security policy
UPLOAD
API JOB
CONTAINER WORKER
REPORT + DELIVERY
SCRATCH REMOVED
Don’t trust a converter. Verify the migration.
01
Independent source analysis
02
Independent target analysis
03
Semantic comparison
04
Mutation testing
05
Manufacturing checks
06
False-green monitoring
Ready to move your project?
Drop an Altium .PcbDoc and see what Crosspad can verify before you pay.
Free analysis on one Altium .PcbDoc — the board file the migration accepts at launch, binary or ASCII text — or a .zip of the project, which is opened for the one board inside it. Nothing is charged until you unlock a migration.