How a migration runs, from free analysis to a sealed delivery.
Four steps, a credit spent only at unlock, and a defined path if a delivered result is not right. This page describes the flow as the product runs it today and quotes the policies that back each commitment.
Upload, results, unlock, delivery.
- 01
Upload and sign in
Drop your .PcbDoc and enter your email. An address we have never seen is signed in on the spot; any address that already has a Crosspad account is asked for a six-digit emailed code, which expires after 10 minutes and locks after five failed attempts. Creating the job needs a session, not a credit.
- 02
Free analysis and processing
The job runs through analysis, building the KiCad target, applying safe repairs and validating. You can watch its progress in the flow; the analysis is free whatever the outcome.
- 03
Results and verdict
The job ends in a completion state shown as a badge — VERIFIED, REVIEW REQUIRED, UNSUPPORTED or FAILED — with the report behind it. Failed and unsupported outcomes stop here and cost nothing.
- 04
Unlock and download
A completed job with a deliverable verdict can be unlocked with one credit (or by buying a pack at that moment). Until you unlock it, the download stays locked and nothing is spent. After unlock, the Delivery Bundle is available from your dashboard for the Download Period.
One credit equals one successful migration. A credit is spent only at unlock, never at upload or analysis.
What an Order commits us to.
Quoted from Section 2 of the Commercial Beta Terms and Scope — the commitments that govern your Order.
What the bundle contains today
You download one file, crosspad-migration.zip. It carries your board as a .kicad_pcb, the component and net inventories, the DRC and import reports, and the full migration report.
| INCLUDED | DESCRIPTION (QUOTED) |
|---|---|
| Delivery Bundle | KiCad project files for the target version, migration report, decision receipts, warnings, validation manifest with SHA-256 hashes, and a README-FIRST file with the engineering-review warning. |
| Download Period | 90 days of download access, extendable on request. |
| Independent validation | Comparison of the result with the Source File across the domains in Section 4, producing the evidence categories in Section 5. |
| Guided Decisions | Options and consequences for constructs without an exact KiCad equivalent; applied only on your confirmation. |
If an unlocked result has a material defect, we fix it first.
Quoted from the Refund and Remediation Policy. The version you accepted at checkout governs your Order.
- 01
Analysis and migration are free. A credit is spent only when you unlock a finished migration. A failed, blocked or unsupported migration never costs a credit.
- 02
You pay for a pack of credits up front. For the first 14 days you can ask us for your money back on any credit you have not used — nothing happens automatically, you have to ask. After those 14 days there is no more money back, but the credits are not lost: they stay on your account and remain usable for 24 months.
- 03
If an unlocked result has a material defect, we fix it first. Remediation within a defined period and number of cycles.
- 04
If we still cannot deliver, you get the credit back, or its purchase price if you prefer.
The terms those sentences use
| TERM | DEFINITION (QUOTED) |
|---|---|
| Initial Failure | A Migration that does not reach a deliverable verdict and therefore cannot be unlocked. It spends no Credit. |
| Remediation | The work we perform after an Initial Failure or an accepted Defect Report: alternate migration strategies, repairs, reconstruction, guided Decisions, revalidation and re-Delivery. |
| Remediation Cycle | One re-processing, revalidation and re-Delivery. |
| Remediation Period | 30 calendar days from our Initial Failure notice or our acceptance of a Defect Report, covering up to 3 Remediation Cycles. We may extend it once by 15 days with notice. It pauses while a Customer Request is open. |
| Conforming Deliverable | A Deliverable whose validation manifest reports every domain within the Supported Scope as VERIFIED, TRANSLATED_EQUIVALENTLY or REPAIRED_AND_REVALIDATED, with any remaining items disclosed as ACTION_REQUIRED, ENGINEERING_DECISION_REQUIRED or UNSUPPORTED. Items that are disclosed do not make a Deliverable non-conforming. |
Outcomes that cost nothing.
- The analysis
Free for every file, whatever the verdict.
- A Blocked project
Outside the Supported Scope; it cannot be ordered.
- A FAILED or UNSUPPORTED job
No deliverable, no credit spent.
- A completed job you do not unlock
Nothing is spent until you unlock the delivery.
How long files and records are kept.
Quoted from Section 4 of the Security, File Retention and Deletion Policy; the schedule applies where the corresponding live processing feature is enabled.
| RECORD | RETENTION (QUOTED) |
|---|---|
| Analysis-only upload | Deleted within 7 days after the upload or sooner where the deployment does not retain it |
| Source File for an Order | Deleted within 30 days after delivery or order closure, unless earlier deletion is requested after acceptance |
| Delivery Bundle | Available for the 90-day Download Period, then deleted; a non-content hash may be retained |
| Account, order, payment, consent and event records | Up to 7 years after order closure where needed for tax, accounting, fraud and dispute defense |
| Support communications | Up to 3 years |
| Server and edge logs | According to the applicable provider retention setting, ordinarily no more than 90 days |
| Expired codes and sessions | Expired sessions are invalid immediately; stale records are removed during routine cleanup |
Sign-in uses a six-digit email code. Codes are stored as keyed hashes, expire after 10 minutes and are locked after five failed attempts.
The code is what an existing account uses to prove ownership: any email that already has a Crosspad account is asked for it. An address we have never seen is signed in on the spot instead, and an open session for the same email is reused.
Frequently asked questions.
Is the analysis really free?
Yes. Creating a job needs a signed-in session, not a credit, and the analysis runs for every file whatever the outcome. A credit is spent only when you unlock the delivery of a completed migration.
When exactly is a credit spent?
At unlock, on a completed job whose badge is VERIFIED or REVIEW REQUIRED. Until then the download stays locked and nothing is spent; FAILED and UNSUPPORTED jobs never cost anything.
What happens if a migration fails, or a result I unlocked is wrong?
A migration that fails spends no credit at all — there is nothing to refund and you can retry. If you unlocked a result and it has a material defect, Remediation-First applies: we fix it within a defined period and number of cycles, and if we still cannot deliver a Conforming Deliverable the credit returns to your account, or we refund it at the Credit Price if you prefer money. The Refund and Remediation Policy defines each of those terms.
How long is my source file kept?
Per the retention schedule: an analysis-only upload is deleted within 7 days after the upload or sooner where the deployment does not retain it; the Source File for an Order is deleted within 30 days after delivery or order closure unless earlier deletion is requested after acceptance; the Delivery Bundle is available for the 90-day Download Period, then deleted.
The first step is free — and it is the informative one.
Upload a .PcbDoc, read the verdict and the report, and decide with evidence in hand.
The analysis is free.
Last updated 2026-09-05. The flow reflects the live product; commitments are quoted from the Commercial Beta Terms, the Refund and Remediation Policy and the Security, File Retention and Deletion Policy, v1.0, which govern.