Moving an existing PCBA build to a new EMS provider involves more than sending a BOM, Gerber files, and a new purchase order.
For OEM teams switching PCB assembly suppliers, the main risk is not the change of factory address. It is losing control of the approved build during the handoff.
The new manufacturing partner needs to know which revision set is released, which materials and tools belong to the customer, which factory-specific programs and process controls must be rebuilt, and what evidence is required before the product can be released to repeat production.
A controlled PCB assembly supplier transfer preserves the approved product, rebuilds the manufacturing process where necessary, and proves that the transferred build meets the buyer's current requirements.
Most Transfer Problems Start with Version Drift
The most dangerous transfer package is often not an empty folder.
It is a full folder in which the BOM, assembly drawing, firmware, component placement data, and reference unit describe different builds.
The BOM may show Revision C, while the assembly drawing still reflects Revision B. The approved reference unit may contain an alternate component that was accepted by email but never added to the released BOM. The test fixture may be running a later firmware configuration than the file stored in the project folder.
Each item may appear valid on its own. Together, they create an uncertain product baseline.
Before asking the new EMS provider to quote tooling or schedule a build, the buyer should establish one released revision set covering:
- PCB fabrication data;
- BOM revision;
- component placement list;
- assembly drawing;
- approved manufacturer part numbers;
- approved alternatives;
- do not populate (DNP) positions;
- firmware and programming configuration;
- test requirements;
- labeling and traceability rules;
- packaging requirements;
- approved engineering changes or deviations.
The purpose is not to create the largest possible transfer package. It is to make sure every file points to the same approved product.
An approved reference unit, sometimes called a golden sample, can support the review. It should not silently override the documentation.
A physical board may contain a temporary deviation, a repair, an old revision, or a component approved for only one production lot.
A golden sample is useful evidence. It is not a substitute for revision control.
In practice, supplier transfers often expose a problem that existed long before the move began: procurement, engineering, and quality are not working from the same product baseline.
Procurement may be tracking open component orders against one BOM. Engineering may have released a later change. Quality may still be inspecting against an older reference unit.
Closing that gap is usually more urgent than agreeing on the first production date.
Separate the Product from the Factory Process
A supplier transfer becomes easier to control once the project team separates three categories:
- What must be transferred under revision control?
- What must be rebuilt for the new production line?
- What must be revalidated before production release?
This distinction prevents the product definition from being confused with the previous factory's machine settings and local work instructions.
What Must Be Transferred Under Revision Control?
The product definition must be transferred as a controlled set of information.
Depending on the project, the transfer package may include:
- Gerber, ODB++, IPC-2581, or other PCB manufacturing data;
- drill files and fabrication notes;
- stackup and impedance requirements where applicable;
- BOM with manufacturer part numbers and sourcing rules;
- component placement list (CPL), also called a pick-and-place or centroid file;
- assembly drawing;
- polarity and orientation notes;
- firmware and programming instructions;
- test procedure and pass/fail criteria;
- label artwork;
- serialization and traceability requirements;
- packaging specifications.
The file format matters less than consistency.
An intelligent manufacturing-data format may reduce manual alignment between PCB and assembly files, but it cannot correct an outdated BOM or an uncontrolled firmware version. A conventional Gerber, drill, BOM, CPL, and drawing package can also support a transfer when the files are complete, aligned, and approved.
The real question is not how many files are in the folder.
It is whether they all describe the same board.
What Must Be Rebuilt for the New Production Line?
Factory-specific programs and process controls usually need to be rebuilt or re-established for the new production environment.
These may include:
- stencil design;
- placement-machine programs;
- feeder setup;
- work instructions;
- AOI programs;
- reflow settings;
- wave or selective-soldering programs;
- test-station configuration;
- packaging workflow.
The outgoing supplier's files may provide useful reference information, but they are not automatically portable.
An old reflow profile is evidence of how the product was previously built. It is not a machine recipe that can simply be pasted into another oven.
The new factory may use different equipment, solder paste, board support, conveyor settings, inspection software, fixture interfaces, and production loading conditions.
What transfers is the released product requirement and its acceptance criteria-not the previous factory's machine settings.
What Must Be Revalidated Before Production Release?
The transferred process must demonstrate that it produces an acceptable assembly.
The required evidence depends on the product, application risk, customer requirements, and agreed manufacturing scope. It may include:
- first-piece or first-article verification;
- component identity and orientation checks;
- solder-joint inspection;
- X-ray inspection for relevant hidden joints;
- programming confirmation;
- electrical or functional testing;
- test correlation with an approved reference;
- mechanical fit;
- traceability review;
- labeling and packaging approval.
Not every transfer needs the same sample quantity, report format, or qualification sequence.
A mature, relatively straightforward industrial controller may require a focused transfer build and functional comparison. A high-reliability or customer-regulated product may require a more formal approval package.
The acceptance method should be agreed before the transfer build begins.
Build One Controlled Transfer Dossier
A standard RFQ package is often enough to start a quotation. It is rarely enough to transfer a product that has already been manufactured elsewhere.
The transfer dossier should bring together the product definition, material position, customer-owned assets, and acceptance requirements.
Product Definition and Approval Rules
The dossier should identify:
- the current released revision set;
- exact manufacturer part numbers where required;
- approved alternatives;
- customer-supplied or customer-controlled components;
- special assembly requirements;
- firmware and programming version;
- test scope;
- marking and packaging rules.
A BOM should not restrict every ordinary passive component to a single manufacturer without a technical or commercial reason.
At the same time, a generic entry such as "10 kΩ resistor" may be insufficient when voltage rating, tolerance, temperature coefficient, qualification, lifecycle status, or an approved source matters.
The BOM should communicate the real engineering and sourcing boundary for each relevant line.
Materials and Open Purchase Commitments
Material handover should be reviewed separately from the design files.
Create a material and purchase-order ledger covering:
- stock held by the outgoing supplier;
- customer warehouse stock;
- work in progress (WIP);
- finished goods;
- components in transit;
- open purchase orders;
- customer-supplied parts;
- consigned materials;
- non-cancellable and non-returnable (NCNR) stock;
- long-lead, sole-source, or obsolete parts;
- approved disposition for unused material.
This review should happen before duplicate orders are placed.
A quantity report alone does not show whether the material supports the current revision, whether the source is approved, whether the packaging remains suitable, or whether the buyer has the right to release it.
One unresolved customer-controlled component can hold up the entire transfer, even when every EMS-sourced item is already available.
Material ownership, material condition, and sourcing approval are three separate questions.
Customer-Owned Tooling and Fixtures
Tooling and fixture ownership should be confirmed before the outgoing supplier relationship becomes difficult.
For each asset, record:
- owner;
- current location;
- supported product revision;
- physical condition;
- available drawings or software;
- release restrictions;
- compatibility with the new factory;
- transfer, rebuild, or retirement decision.
Typical assets include:
- stencils;
- soldering pallets;
- programming adapters;
- mechanical jigs;
- test fixtures;
- custom trays;
- packaging tools;
- approved reference units.
An NRE charge does not automatically establish ownership or transfer rights for every physical tool, program, or source file. Those rights depend on the original commercial agreement.
A customer may own the physical fixture but not the outgoing supplier's proprietary test software. In another project, the buyer may own the fixture drawings and source files but decide that rebuilding the hardware is more practical than shipping the existing unit.
Ownership and technical usefulness must be reviewed separately.
A Test Fixture Is Not a Test Method
Test transfer is often underestimated because the physical fixture appears to be the main asset.
The fixture is only one part of the system.
A usable handoff may also require:
- fixture drawing;
- wiring diagram;
- probe or connector map;
- fixture revision;
- test software;
- configuration files;
- test limits;
- pass/fail logic;
- calibration requirements;
- firmware files;
- programming utility;
- checksum or verification method;
- known-good reference results;
- debug instructions;
- retest rules.
A fixture without its program, limits, configuration, and reference results is only hardware.
Even when the physical fixture transfers successfully, its results may still need to be correlated with the previous setup. Different instruments, cable losses, load conditions, software versions, and calibration states can affect measurements.
Just as important is confirming what the existing test actually covered.
A board that passes a power-on test at the new supplier is not necessarily equivalent to a board that previously underwent:
- communication-port testing;
- relay or I/O checks;
- current-consumption limits;
- firmware verification;
- load testing;
- sensor simulation;
- customer-specific functional sequences.
Compare the test coverage, limits, configuration, and recorded results-not just the final word "PASS."
Use the Transfer Build as a Correlation Exercise
The first build at the new supplier should not be treated as an ordinary repeat order.
Its purpose is to correlate the new manufacturing and test process with the approved product baseline.
| Review area | What to verify |
|---|---|
| Product revision | PCB, BOM, assembly drawing, firmware, labeling, and packaging files describe the same approved build |
| Materials | Components follow the approved part-number, source, and substitution rules |
| Assembly | Placement, polarity, soldering, workmanship, and special processes meet the agreed requirements |
| Programming | The correct firmware, configuration, and verification method are used |
| Testing | Coverage, limits, fixture setup, and result records match the approved test intent |
| Identification | Serial number, traceability, labeling, and packaging are correct |
| Open issues | Deviations and corrective actions have owners before wider production release |
The review should not be reduced to:
The boards powered on, so the transfer passed.
Power-on success can be useful, but it does not validate functions that were never tested.
Likewise, an approved first article can confirm that the build starts correctly. It does not automatically prove material continuity, stable test execution, or readiness for repeat production.
The transfer build should answer one practical question:
Can the new supplier reproduce the approved product using a controlled and repeatable process?
Do Not Turn Historical Workarounds into New Requirements
Mature products often accumulate local corrections over time.
Examples include:
- a manually adjusted test limit;
- extra solder applied at one location;
- a feeder rotation correction;
- a modified stencil aperture;
- an operator inspection note;
- a temporary alternate component;
- a special rework instruction.
Some of these changes contain valuable manufacturing knowledge. Others are temporary workarounds that should never become part of the permanent baseline.
During transfer, each item should be classified as:
- an approved product requirement;
- a validated permanent process;
- an approved temporary deviation;
- a troubleshooting measure;
- an obsolete instruction.
The new supplier should not ignore known production history. It should also not inherit every workaround without understanding why it existed.
A correction that was necessary on one line may no longer be needed on different equipment. Conversely, a change that addressed a real design, material, or test issue may need to be added to the released documentation.
Preserve the reason behind the change, not merely the old instruction.
Plan the Cutover Around Exposure, Not a Generic Timeline
There is no standard number of weeks, units, or production batches that makes every PCB assembly supplier transfer safe.
The cutover plan depends on available finished goods, committed deliveries, component and fixture readiness, outgoing-supplier cooperation, product risk, approval requirements, and whether both suppliers can operate in parallel.
Parallel production can reduce continuity risk, but it is not always practical. A project may have only one functional test fixture, critical components that cannot be divided, or customer-owned inventory that is already being relocated. The outgoing supplier may no longer accept orders, or the product may not permit two manufacturing sources to operate at the same time.
Low annual volume creates another boundary. Maintaining two qualified supply paths may cost more and create more revision-control work than the continuity benefit justifies.
Where parallel production is not feasible, the transfer plan can use a combination of finished-goods buffer stock, a limited transfer build, staged purchase-order release, additional inspection on early batches, and customer approval before wider production.
Selected material may also remain at the outgoing supplier until the transfer build is accepted, provided ownership, condition, and release terms are clear.
The right control depends on the consequence of interruption, not on a universal calendar.
Boundary Conditions That Need Extra Attention
The Outgoing Supplier Does Not Cooperate
Customer-owned product information should first be separated from proprietary manufacturing knowledge held by the outgoing supplier.
A transfer may still proceed using:
- buyer-owned design data;
- released product specifications;
- approved reference units;
- customer-owned fixtures and materials;
- customer test requirements;
- relevant quality records.
Factory-specific tooling and process controls may then need to be recreated.
The objective is not to obtain another manufacturer's proprietary process. It is to recover enough controlled product information to establish and validate a replacement process.
01
The Reference Unit Does Not Match the Files
Do not ask the new supplier to decide which one is correct.
The difference may represent:
- an approved alternate;
- a temporary deviation;
- an old revision;
- a repair;
- an undocumented change;
- a build error.
Engineering should identify the intended product state before the transfer build proceeds.
02
An Engineering Change Is Still Open
A supplier transfer can continue while an engineering change is being evaluated, but the change must be managed separately.
The project team needs to know:
- which revision is being quoted;
- which revision will be used for tooling;
- whether existing material remains usable;
- who approves the change;
- when the new revision becomes effective.
Allowing the supplier transfer and product change to blend together makes it difficult to determine whether a failure came from the new manufacturing process or the new design.
03
The Existing Test Depends on Operator Judgment
A test that works only because one experienced technician knows how to interpret it is not fully transferable.
The buyer may need to define:
- connection sequence;
- load condition;
- measurable limits;
- firmware configuration;
- failure categories;
- retest rules;
- result-recording requirements.
Supplier transfer often exposes weaknesses in a test method that already existed.
04
PCB Assembly Supplier Transfer Checklist
| Review area | Questions to close | Control record |
|---|---|---|
| Product baseline | Do the PCB, BOM, CPL, assembly drawing, firmware, labeling, and packaging files describe the same revision? | Controlled release index |
| BOM and sourcing | Are approved parts, alternatives, customer-supplied items, and source restrictions clear? | Approved BOM and sourcing rules |
| Material position | Where are stock, WIP, open POs, consigned parts, and NCNR materials? | Material and purchase-order ledger |
| Customer assets | Who owns the stencil, fixtures, adapters, pallets, programs, and custom tools? | Asset register and disposition plan |
| Manufacturing review | What must be regenerated for the new line, and which product requirements must remain unchanged? | Manufacturing review and action list |
| Programming and test | Are firmware, software, fixture data, limits, and reference results controlled? | Programming and test package |
| Transfer build | What must the transferred build prove before approval? | Inspection, test, and issue report |
| Release to repeat production | Are open actions, materials, and change-control responsibilities closed? | Documented release decision |
Before production release, pause the transfer if the approved BOM cannot be identified, the reference board does not match the released files, firmware ownership is unclear, tooling ownership is disputed, or the test fixture has no controlled software and limits.
The same applies when approved alternatives exist only in email threads, customer-owned inventory cannot be located, or the buyer has not defined what the transfer build must prove.
A new EMS provider can help identify these gaps. It cannot invent the buyer's product requirements.
How STHL Reviews Supplier Transfer Projects
Shenzhen STHL Technology Co., Ltd. can review the available transfer package and identify gaps that may affect BOM readiness, material handover, assembly planning, programming, testing, and release to repeat production.
The review can begin with the files and records currently available. The exact support scope is confirmed after the product revision, material status, tooling, test method, and open transfer issues have been reviewed.
For an initial discussion, buyers can prepare:
- BOM and PCB fabrication data;
- component placement list and assembly drawing;
- current released revision set;
- approved-alternative information;
- material, inventory, and open-PO status;
- tooling and fixture summary;
- firmware and programming requirements;
- test method and pass/fail criteria;
- relevant quality or failure information;
- planned transfer-build quantity and target production stage.
The first review does not require a perfect dossier.
It should make clear what is available, what remains at the outgoing supplier, what must be recreated, and what requires approval before the transfer build.
Review STHL's PCB Assembly capabilities, submit the available package through Request a Quote, or send the project information to info@pcba-china.com.
Conclusion
A PCB assembly supplier transfer is not finished when the new supplier receives the files or cuts a new stencil.
It is finished when:
- the approved product definition is controlled;
- materials and customer-owned assets are accounted for;
- factory-specific manufacturing controls have been rebuilt where needed;
- programming and testing are repeatable;
- the transfer build meets predefined acceptance requirements;
- repeat production no longer depends on undocumented assumptions.
The safest supplier transfer preserves the product, rebuilds the process, and proves the result before full production release.
