Moving a released PCBA to another EMS provider is a transfer of manufacturing knowledge, controlled assets and responsibility. A Gerber file, BOM and a previously passing board are useful inputs, but they do not show that the receiving site can reproduce the required configuration and evidence.
This guide addresses a change of manufacturing provider or site, including a second source. For the earlier stages of developing a new product, use the EVT, DVT and PVT handoff guide. A transferred design may already be released while its receiving-site process remains unapproved.
1. Freeze the transfer boundary before comparing suppliers
Define the product variants, board revisions, firmware, assembly options, test requirements, quantities and delivery obligations included in the transfer. State whether the receiving supplier will reproduce the existing configuration or implement separately approved changes. Keep a design improvement out of the baseline unless its validation and approval are explicitly part of the plan.
Identify the transfer owner and the people authorized to approve design, quality, sourcing, test and shipment decisions. A commercial award may authorize preparation work without authorizing production shipment. Record those gates separately.
2. Inventory the assets and the rights needed to use them
On small screens, scroll the table sideways to compare columns.
| Asset or information | Transfer question | Evidence of readiness |
|---|---|---|
| Released manufacturing data | Is the receiving package complete and internally consistent? | Controlled archive, revision list and resolved discrepancies |
| Stencil, pallet and mechanical tooling | Who owns it, may it be moved, and is it compatible with the new route? | Asset identity, condition, permitted use and receiving inspection |
| Machine and inspection programs | Can they be lawfully transferred and used, or must they be recreated? | Agreed access, conversion responsibility and validation records |
| Test fixtures and reference units | Are their condition, software and limits controlled at the receiving site? | Fixture baseline and an authorized transfer-verification plan |
| Firmware and production credentials | Who controls access, provisioning and recovery? | Approved secure handoff and role allocation |
| Open issues and quality history | Which limitations and recurring problems must the new process address? | Applicable issue register, dispositions and required evidence |
Resolve ownership and permitted access before promising that a departing supplier's programs or tooling will be available. Use the appropriate contractual and security review for those arrangements. Do not put production secrets or private signing material into a general RFQ archive merely to make the package appear complete.
3. Build a receiving-site process delta
Compare what will actually change: fabrication source, stencil manufacture, soldering equipment, materials, inspection method, cleaning, programming, fixtures, operators, record systems and shipment preparation. “Same BOM” does not mean “same process.” Record what will be transferred, recreated or newly qualified.
For each difference, state the question to resolve, the responsible owner and the evidence needed. Prior results may help identify risks, but they do not automatically establish receiving-site readiness. Use the fixture handoff guide for the specific verification of transferred or restored test equipment.
Where assembly requirements invoke IPC documents, preserve the actual revision, class, addenda and customer requirements. The official IPC document table helps identify the relevant publications. Selecting a document name is not a replacement for agreeing the applicable acceptance and process requirements.
4. Compare evidence against a common configuration
Agree the receiving-site pilot configuration and verification plan before building samples. Define the characteristics to compare, required test conditions, fixture and software identities, measurement-control needs and issue-closure criteria. Reference units should have known identities and condition; a unit labeled “golden” is not automatically a suitable standard for every comparison.
Hypothetical teaching example: the outgoing site built board revision C using firmware 2.4, while the receiving-site pilot uses revision D and firmware 2.5. A different test result cannot be attributed solely to the supplier change. Either establish an appropriate matched comparison or explicitly separate the design-change validation from the site-transfer assessment.
Preserve original failed results, repairs and retests. Record what the pilot establishes and what remains open. Apply customer, product and regulatory approval requirements where relevant; this checklist does not define a universal qualification quantity or authorize a transfer for a regulated product.
5. Reconcile work in progress and material before cutover
Create a dated ledger for finished assemblies, work in progress, kitted material, loose components, held stock and outstanding purchase commitments. Identify which site is responsible for completing, transferring, returning or disposing of each item under the applicable authorization. Keep old-site and new-site identities distinct.
Hypothetical quantity example: an outgoing order for 300 boards consists of 180 completed units, 70 in work in progress and 50 not yet started. A proposed new-site order adds 200 units. The combined plan may cover 500 units of demand, but it does not mean 500 units are finished or ready to ship. Only units with the required completion and release status should be counted as shipment-ready.
Check whether components already committed to the unfinished 120 old-site units have also been counted as available to the new site. Reconcile serial allocation, label formats and shipment records so parallel production cannot create duplicate identities or obscure which site built a unit.
6. Set release and fallback gates before the last old-site shipment
- Receiving package accepted, with missing data and access issues resolved.
- Tooling and material received, identified and assessed for the new route.
- Receiving-site process and test evidence accepted against the agreed plan.
- Open issues assigned a documented disposition and effective scope.
- Required customer or product approvals completed before affected shipment.
- Inventory, serials, records and outstanding commitments reconciled.
- Fallback responsibility and decision deadlines agreed while options still exist.
A fallback plan should identify which configuration and resources could actually be used, by whom and until when. Do not assume that the old line, tooling or material will remain available after termination or redeployment. Confirm the relevant arrangements before relying on them in a delivery promise.
After release, preserve the transfer baseline and use the normal revision-control process for later changes. The first repeat order should retrieve the approved receiving-site configuration, rather than rebuilding it from the transfer team's email history.
Manufacturing-transfer questions
Is a complete Gerber and BOM package enough to transfer production?
It is part of the package. Review the applicable process knowledge, materials, tooling, programs, testing, access rights, open issues and release evidence needed by the receiving site.
Must the new site copy every outgoing process parameter?
The receiving process must meet the agreed requirements with suitable evidence. Differences in equipment and materials need explicit review; blindly copying settings does not establish equivalence.
Can both suppliers build during the transition?
Where the applicable approvals and agreements permit it, control both configurations, material commitments, serial allocation and shipment records. Parallel production requires an explicit reconciliation plan.
Source scope: the IPC reference identifies assembly publications. The transfer register, comparison example and cutover ledger are original planning tools, not a report of a completed transfer, a legal opinion or a product-specific qualification plan.