Biologics CMC Series (14): Biologics Technology Transfer—Why Sending SOPs to a CDMO Is Not Enough

By Jason Lu | LuTra Studio
Executive Summary
Sending a manufacturing process, standard operating procedures (SOPs), and analytical methods to a contract development and manufacturing organization (CDMO) does not mean that technology transfer is complete.
Biologics Technology Transfer should establish the receiving team's ability to run the process, interpret results, and make informed decisions when something goes wrong, using its own equipment, people, facilities, and quality systems.
This article addresses five practical points:
The transfer includes product and process knowledge, operating boundaries, analytical capability, and quality responsibilities.
The same equipment name, formulation, or setpoint does not necessarily give the product the same manufacturing experience.
Process transfer and analytical method transfer need coordinated timelines. Otherwise, a batch may be manufactured before the receiving team can reliably evaluate it.
Technology transfer, comparability, process validation, and regulatory submission are connected activities with different purposes.
Transfer success should be assessed against agreed evidence and acceptance criteria, with continued review of subsequent batches.
Introduction: Why Does the Same SOP Produce Different Results at Another Site?
Imagine a company transferring an antibody process to a new CDMO.
The formulation is established. Process flow diagrams are available. Historical batch data look consistent. The receiving site has the equipment, the project schedule is in place, and both sides start discussing the date of the first batch.
Then execution begins, and differences emerge.
A transfer that took half an hour at the original site takes longer at the new one. The same agitation speed produces a different foaming pattern. Filtration pressure behaves differently. Analytical results begin to diverge between laboratories.
Each issue may seem manageable on its own. Together, they can affect product quality, batch timelines, and the strategy for assessing comparability.
In my view, one of the most underestimated parts of technology transfer is the knowledge that the original team has come to take for granted.
An operator knows that a step tends to foam and uses a particular addition position. An analyst knows that a sample does not tolerate repeated freeze–thaw cycles. The process development team knows that an operating range has worked before but has not been sufficiently studied to support routine use across that range.
Unless this information is documented, explained, and supported by evidence, the receiving team may get a procedure it can follow without the knowledge needed to recognize when that procedure is no longer appropriate.
For Readers New to the Field: What Does Biologics Technology Transfer Actually Transfer?
Think of transferring a recipe to another commercial kitchen.
The recipe specifies ingredients, temperature, and time. But changing the cookware, heat source, batch size, or operator can change the result even when everyone follows the same numbers.
Biologics add another challenge: some quality changes are invisible and cannot be fully understood through a single test.
Biologics Technology Transfer therefore needs to connect three things.
First, an understanding of the characteristics the product should have.
Second, an understanding of which process conditions can change those characteristics.
Third, the receiving team's ability to operate, measure, and respond to differences.
The receiving team does not have to be another company. A transfer can occur from research to process development, from a development laboratory to a good manufacturing practice (GMP) manufacturing group, or between manufacturing sites within the same organization.
How Do Official Guidelines Approach Technology Transfer?
The WHO's 2022 *WHO guidelines on technology transfer in pharmaceutical manufacturing* describes the transfer of products, processes, and knowledge, supported by documentation and professional expertise.[1]
ICH Q10 places technology transfer within the product lifecycle and emphasizes the flow of knowledge between development and manufacturing.[2]
These documents provide useful frameworks. The actual evidence needed still depends on the product, development stage, and regional requirements. This article primarily uses monoclonal antibodies (mAbs) as examples. Teams working on mRNA/lipid nanoparticles (LNPs), viral vectors, or cell therapies can apply the project reasoning, but should not copy the same testing or validation package.
For project discussions, I would organize the work around four questions:
Question | Supporting evidence |
What are we transferring? | Defined scope, data versions, operating conditions, and deliverables |
What is different at the receiving site? | Gap assessment covering equipment, materials, people, methods, and systems |
How will we know those differences have been addressed? | Studies with defined purposes, execution records, and acceptance criteria |
Who manages the process after handover? | Routine monitoring, change management, investigations, and escalation arrangements |
Separate the Decisions: Transfer, Comparability, Validation, and Regulatory Submission
These terms often appear in the same meeting, but they are not interchangeable.
Activity | Main question | What it does not establish on its own |
Technology transfer | Can the receiving team take over and execute the technology? | Product comparability or authorization to supply |
Comparability | Do differences after a change affect expectations of product quality, safety, or efficacy? | The receiving team's operational capability |
Process validation | Can the process consistently deliver product meeting quality requirements? | A complete product comparability or regulatory impact assessment |
Regulatory submission/approval | What notification, application, or authorization is needed for the change? | Technical evidence or effective site controls |
ICH Q5E provides principles for comparability before and after manufacturing changes. Its formal scope includes proteins, polypeptides, and related products made using cell-culture expression systems that can be highly purified and sufficiently characterized. It addresses changes by a single manufacturer, including contract manufacturers, with access to direct prechange/postchange comparison; it is not a biosimilarity assessment between different companies' products. mRNA/LNPs, viral vectors, and cell therapies should not automatically be treated as falling within that same scope: product-specific and regional guidance must be checked. The FDA's process validation guidance describes a lifecycle involving process design, process qualification, and continued process verification.[3,4]
“Transfer batches completed,” “comparability acceptable,” and “commercial supply may begin” therefore require separate conclusions. With appropriate planning, batches may support more than one activity, but their purposes, conditions, and intended data uses need to be defined in advance.

Biologics Technology Transfer Starts with Receiving-Site Suitability
Many projects begin exchanging documents before they have adequately assessed site fit.
I would first ask: Has this site handled similar products? Are its equipment and people suitable for this process? If adjustments are necessary, which quality attributes could they affect?
The gap assessment can be organized into three areas.
Process and equipment: operating principles, working volumes, flow paths, product-contact materials, temperature control, sensor positions, sampling, transfer duration, and equipment operating ranges.
Analytics and materials: analytical instruments, reference standards, critical reagents, raw-material sources, consumable specifications, and sample shipping and storage conditions.
Operations and quality systems: operator capability, contamination control, cleaning strategy, record systems, data review, deviation investigations, change notifications, and communication between companies.
The most useful column in a gap assessment is often “What happens next?”
Difference | Potential impact | Example response |
Longer tubing and additional connections | Changes in contact area, transfer duration, and hold-up volume | Assess recovery, duration, and relevant quality indicators |
Different agitation configuration in a larger preparation vessel | Changes in mixing, foaming, and local conditions | Compare equipment geometry and suitable mixing indicators |
Different filtration assembly | Changes in adsorption, flux, and pressure behavior | Evaluate suitability using representative samples |
Different critical-reagent lot for the receiving site's potency assay | Potential systematic result shift | Plan appropriate reference-standard, reagent, and method bridging |
These are examples for risk assessment, not a universal study list. The seven additional examples in this article are hypothetical teaching scenarios. Their numbers and tables are not product specifications, operating limits, or universal acceptance criteria.
Example 1: “Refrigerated storage” can mean different things at two sites.
Suppose the original site holds an intermediate under refrigeration for four hours, while the receiving site needs a 16-hour hold because of scheduling. These durations are illustrative, not recommended hold-time limits.
If the existing studies cover only the shorter duration, the same storage temperature does not automatically support the new schedule. The team should examine actual temperature, container, concentration, preceding and subsequent operations, and sampling conditions. It can then determine what representative data are needed and arrange a controlled alternative schedule while evidence is incomplete.
Site fit includes whether the operating schedule falls within supported process boundaries.
The Transfer Package: Help the Receiving Team Understand Why
I suggest reviewing a transfer package in four groups rather than measuring completeness by file count.
Product and process knowledge. Product characteristics, functions relevant to the mechanism of action, critical quality attributes (CQAs), process flow, development history, and relationships among materials and intermediates.
Operating conditions and control rationale. Critical process parameters (CPPs), operating ranges, control points, sampling, hold times, and the potential consequences of changes to parameters or materials.
Analytical and quality history. Method purposes and performance, reference standards and critical reagents, representative batch data, stability results, deviations, and investigation experience.
Execution and handover arrangements. Training, site documentation, study plans, acceptance criteria, version control, and unresolved issues.
Development failures and unusual results are particularly useful.
If an extended hold once caused an increase in particles, retaining only the final successful process can hide the reason behind the time limit. Preserving the failed conditions, investigation limitations, and subsequent improvements helps the receiving team avoid repeating the problem.
Example 2: What does “add slowly” mean in practice?
Suppose an SOP says, “Add the adjustment solution slowly while mixing until uniform.” The original team introduces it below the liquid surface and observes foam and pH stabilization. The receiving team adds it above the surface and uses a fixed waiting period to decide that mixing is complete.
Both teams may believe they followed the SOP, while executing different conditions.
The transfer should turn addition position, rate control, mixing endpoint, and measurement limitations into executable instructions supported by appropriate studies. If the original team lacks sufficient evidence, that should be recorded as an open question. An operator's habit should not automatically become a proven critical condition.
The Same Equipment Description Does Not Mean the Same Product Experience
Writing “agitation speed: 100 rpm” is straightforward. Establishing whether it is appropriate in another vessel takes more understanding.
Impeller type and diameter, vessel geometry, liquid level, viscosity, and addition position can affect mixing. Depending on the operation and risk, the team may compare mixing time, tip speed, power per unit volume, or other suitable indicators. Preserving one indicator does not mean all conditions have been preserved.
Tangential flow filtration (TFF) also requires more than membrane area, flow rate, and concentration factor.
Membrane material, flow-channel configuration, crossflow, transmembrane pressure, product concentration, processing time, and temperature should be considered in the context of the operation.
Each setpoint should have an understandable physical or biological basis. Existing knowledge may support well-understood, low-risk differences. Studies should focus on differences most likely to change the product where uncertainty remains.
Example 3: The same 100 rpm gives a threefold difference in tip speed.
Suppose two vessels have impeller diameters of 4 cm and 12 cm, both operated at 100 rpm. Using tip speed = π × impeller diameter × revolutions per second, the values are approximately 0.21 m/s and 0.63 m/s.
This simplified calculation illustrates the relationship between geometry and rotational speed. It does not establish that the larger vessel necessarily causes more shear damage or that tip speed is the only appropriate scale-up criterion. Fluid properties, vessel configuration, and the purpose of the operation still matter.
An rpm value alone is a setpoint. Equipment geometry, process understanding, and a justified comparison make it usable engineering knowledge.

Analytical Method Transfer Needs to Keep Pace with Process Transfer
If manufacturing is complete before reliable analytical capability is available, the team may struggle to distinguish product differences from sample-handling or method effects.
ICH Q14 and Q2(R2) provide scientific frameworks for analytical procedure development and validation, respectively.[5,8] Validation at the original laboratory does not automatically establish reliable execution at the receiving laboratory; a laboratory transfer still needs an appropriate plan and supporting evidence. Sections 12.24–12.36 of the WHO technology-transfer guideline provide specific considerations for analytical procedure transfer.[1] During transfer, I would examine three questions:
Can the method answer the question raised by this change?
Can the receiving laboratory execute it consistently?
Are results from the two laboratories sufficiently comparable?
For a cell-based potency assay, cell condition, incubation duration, reagent lots, sample dilution, and curve-analysis settings may all be investigation starting points.
Method transfer does not always require the same experimental design. Comparative testing, co-validation, or another approach should be justified using the method, prior knowledge, and identified gaps. Passing system suitability at both laboratories does not, by itself, establish a successful transfer.
The protocol should explain sample selection, coverage of relevant quality differences, interpretation of shifts, and investigation of unacceptable results. The comparison should not be selected after seeing which approach passes most easily.
Example 4: The same sample gives different potency results at two laboratories.
These values are hypothetical. They are not universal specifications or method-transfer acceptance criteria.
Same aliquoted sample | Original laboratory | Receiving laboratory |
Relative potency | 98% | 86% |
System suitability | Passed | Passed |
Reference standard | Same lot | Same lot |
Cell and critical-reagent condition | Record and compare | Record and compare |
The table alone cannot identify the correct result. The numerical difference does not, on its own, establish sample failure or an unsuccessful method transfer.
A reasonable next step is to examine sample handling, cells, reagents, dilution, reaction time, and data analysis under the agreed plan. Method variability and intended use should guide whether comparisons across days, analysts, or other relevant conditions are needed. Selectively reported retests should not replace an investigation into the source of the shift.
Engineering Runs, GMP Batches, and PPQ: Define What Each Batch Is Meant to Answer
“Let's run a batch and see” can begin an exploration, but it is not a complete execution plan.
Batch purpose | Questions it can prioritize |
Engineering/demonstration run | Can the workflow be executed? Are equipment settings, timing, and sampling appropriate? |
GMP batch for clinical supply | Can manufacturing and quality controls support the intended clinical use? |
Process performance qualification (PPQ) batch | Can the data support process reproducibility under appropriate commercial manufacturing conditions? |
Batches monitored after transfer | Are subsequent operations revealing trends or previously unrepresented variability? |
The label “engineering run” does not define a fixed GMP status or make its data suitable for every purpose. Representativeness, execution conditions, and record quality determine what conclusions are supported.
Three batches are not a universal answer for every transfer. Under the FDA's lifecycle approach, the number of validation batches needs a scientific rationale; completing three batches cannot replace an understanding of process variability. EU GMP Annex 15, sections 5.19–5.20, states that, for traditional process validation, a minimum of three consecutive batches manufactured under routine conditions is generally considered acceptable, while allowing a justified alternative number and potentially requiring subsequent batches to supplement the evidence. This should not be read as removing the EU's three-batch expectation in all cases or requiring exactly three batches for every technology transfer. The product, process, change, and applicable requirements determine the approach.[4,9]
Example 5: Three successful batches may cover a narrow set of conditions.
Suppose three demonstration runs use the same raw-material lot, the same operators, and equipment in favorable operating condition.
The results can support execution under that combination of conditions. If the project intends to support performance across material lots, shifts, or equipment-use conditions, the team needs to consider how much relevant variability those runs actually represent.
This does not mean deliberately changing every factor or adding the same number of batches to every project. Conclusions need to stay within the scope supported by the design and data.
Working with a CDMO: Assign Responsibilities to Specific Events
A quality agreement can clarify responsibilities, but it cannot transfer away a party's statutory CGMP responsibilities. The FDA's 2016 guidance primarily addresses commercial manufacturing; it also notes that many principles can help with development and clinical-stage arrangements.[6]
I suggest testing an agreement against actual scenarios.
If the CDMO replaces a seemingly equivalent consumable, who determines whether notification is needed? If potency is low, who leads the investigation and supplies raw data? If an external testing laboratory is needed, who reviews the subcontracting arrangement?
Material and method changes, deviations, out-of-specification (OOS) and out-of-trend (OOT) results, data access, subcontracting, document review, and closeout authority should be clearly addressed.
A project responsibility table can allocate work, but it does not replace formal quality-unit responsibilities. Notification deadlines and escalation conditions should reflect event severity rather than relying on “notify when necessary.”
Example 6: The CDMO wants to replace tubing with the “same specification.” Who acts first?
The table below is a discussion example. Actual arrangements should follow both parties' quality systems and agreement.
Activity | CDMO | Product company |
Describe the change | Provide relevant differences in material, dimensions, supplier, sterilization, and contact conditions | Identify affected products and process uses |
Assess technical risk | Supply site and component information and propose an assessment | Integrate product knowledge, quality attributes, and evidence gaps |
Study and implementation | Execute the approved plan and retain records | Review the plan, results, and implementation conditions as agreed |
Assess regulatory impact | Provide necessary technical information | Have the responsible regulatory function assess applicable reporting and implementation timing |
An agreement saying “equivalent replacements do not require notification” leaves a decision gap unless it defines who determines equivalence and what evidence supports that determination.
Hypothetical Case: Lower Recovery and More Particles After an mAb Transfer
This teaching case does not describe a particular company or actual event.
A company transfers its refrigerated mAb drug-substance process to a new CDMO. The first engineering batch shows no obvious failure in the main tests, but recovery is lower than expected and particle results exceed the original site's typical range.
I would not begin by assuming that the new operators are inexperienced or immediately recommending more agitation.
Step 1: Check measurement reliability.
Are sampling containers, sample mixing, waiting periods, and shipping conditions comparable? Are particle-method settings consistent? Does the recovery calculation account for equipment hold-up and sampling losses?
Step 2: Locate where the difference appears.
Testing only the final sample makes it difficult to identify the source. Risk-based sampling before and after relevant operations can help determine whether the change emerges during preparation, transfer, filtration, or a hold.
Step 3: Develop testable hypotheses.
Could increased contact area contribute to adsorption? Does a longer transfer change product exposure? Is a different agitation configuration producing foam? These are candidate explanations requiring controlled comparisons.
Step 4: Choose studies that distinguish among hypotheses.
Control material lots, sample history, and other conditions where possible. Focus comparisons on the most plausible factors and define interpretation in advance. The relevance of small-scale studies to actual manufacturing also needs justification.
Step 5: Update controls and the transfer conclusion.
If evidence supports changes to the flow path or processing time, update documentation, training, and related assessments through appropriate procedures. Unresolved quality differences should not be dismissed simply because the batch was completed.
The case emphasizes a planning question: if a difference appears during execution, will the team have the data needed to investigate it?

Transfer Readiness: Ten Questions to Answer Before Manufacturing
This checklist supports project discussion. It is not a universal legal checklist.
Area | Information that should be available before manufacturing |
Scope and versions | Which operations, products, and document versions are covered? |
Site suitability | Which equipment, material, and operational differences have been assessed? |
Process knowledge | Are important parameters, boundaries, and evidence limitations clear? |
Analytical capability | Can the receiving site perform the testing needed for this transfer? |
Sample strategy | How will samples, retains, and reference standards be prepared and stored? |
Batch objectives | What will each batch answer, and what uses can its data support? |
Acceptance criteria | How will process performance, product quality, and method results be assessed? |
Exception handling | Who escalates deviations, result differences, and significant risks? |
Regulatory and supply conditions | Which submissions, approvals, or supply conditions remain outstanding? |
Handover and monitoring | Who takes over routine management, and how are open actions tracked? |
I recommend adding an owner, evidence location, due date, and status to each row. Unsupported items should be recorded as gaps, with an explanation of which decision they prevent.
Risk management helps direct limited resources toward the uncertainties that matter most. ICH Q9(R1) provides principles for risk assessment and review.[7]
Example 7: “Analytical method complete” can describe very different readiness levels.
One team means that the SOP has been received and training completed. Another means that a preapproved study has been executed, differences investigated, the report approved, and reference standards and reagents are available.
A green checkmark can make these states look identical.
A useful readiness entry defines completion: which documents, execution evidence, and approvals are required? Conditional acceptance should specify limitations, responsibilities, and deadlines, while ensuring that prerequisites for the next stage are still met.

What Should Be Monitored After Transfer Closeout?
The closeout report should state whether objectives were met, whether the data support the conclusion, and which activities require continued management.
If long-term stability studies remain incomplete, the team should explain what the available data support, the ongoing commitments, and the implications for use or supply.
Subsequent batches can be monitored for recovery, processing time, important quality attributes, method failure rates, and deviations according to risk. Historical data from the original site are useful, but should not automatically become the receiving site's statistical control limits.
Early-stage transfers may have less data and different levels of documentation and study activity. Gaps that could affect patient safety, product quality, or data reliability still need explicit controls and follow-up.
Jason's Takeaway: A Good Handover Builds the Next Team's Judgment
The quality of a technology transfer becomes particularly clear when something goes wrong.
Can the receiving team explain why a parameter matters? Does it know what to check when results shift? When an event falls outside existing knowledge, can the team stop appropriately, preserve evidence, and involve the right people?
That capability requires product knowledge, operational experience, analytical methods, and quality systems working together.
This is how article 14 connects to the earlier series. Specifications define quality acceptance standards. The control strategy organizes the controls. Comparability assesses the product after change. Technology transfer brings that knowledge into the receiving team's daily work.
The deliverable is a capability another team can continue to use.
LuTra Studio: Turning Technical Information into Transfer Decisions
LuTra Studio provides biotechnology technical and development strategy consulting, helping teams organize CMC information, identify development and transfer risks, and establish a shared basis for decisions across functions.
For teams preparing for CDMO collaboration, scale-up, or site transfer, support can include:
Transfer-package review and evidence-gap assessment
Assessment of process, material, analytical, and site differences
Mapping of CQAs, process risks, and study priorities
mRNA/LNP formulation, scale-up, and comparability strategy discussions
Technical communication with CDMOs and cross-functional workshops
Clarifying an undefined question early can move a project forward more effectively than adding a manufacturing batch without a clear purpose.
References
ICH. Q10: Pharmaceutical Quality System. ICH Step 4, 2008; FDA guidance, 2009.
ICH. Q5E: Comparability of Biotechnological/Biological Products Subject to Changes in Their Manufacturing Process. ICH Step 4, 2004; FDA guidance, 2005.
FDA. Process Validation: General Principles and Practices. 2011.
FDA/ICH. Q14: Analytical Procedure Development. FDA final guidance, 2024. The page also provides information about the publication of Q2(R2) and Q14.
FDA. Contract Manufacturing Arrangements for Drugs: Quality Agreements. 2016.
FDA/ICH. Q9(R1): Quality Risk Management. FDA final guidance, 2023.
FDA/ICH. Q2(R2): Validation of Analytical Procedures. FDA final guidance, 2024.
European Commission. EU GMP Annex 15: Qualification and Validation. 2015. See particularly sections 5.19–5.20.
Sources checked November 15, 2026. Official guidance supports the underlying principles. Project tables, checklists, and hypothetical cases are the author's practical applications.





Comments