Defence technology transfer in India has a long record of signed agreements. Its record of lasting industrial capability is more mixed. A Transfer of Technology (ToT) agreement can bring drawings, licences and a production line to an Indian facility. That is the start of the work, not the finish.
The real test comes years later. Can the Indian partner maintain, upgrade, qualify new suppliers for and eventually redesign the system without the original OEM in the room? If it can, ToT has become an industrial capability. If it can’t, it was assembly under licence.
This article sets out what that difference looks like, why India’s acquisition policy is moving to enforce it, and what OEMs and Indian manufacturers pursuing technology transfer and localisation should do about it.
What Is Defence Technology Transfer in India?
Defence technology transfer is the structured passing of know-how from a technology holder, usually a foreign OEM, to an Indian entity. The know-how covers design data, manufacturing processes, test methods and quality systems. It typically takes one of three forms:
Licensed production
the Indian partner builds to the OEM’s design, often from kits.
Technology absorption
the partner learns to build the full system with progressively more local content.
Co-development
both parties share design responsibility and intellectual property.
Most legacy programmes sat at the first level. India’s policy direction now pushes towards the second and third. How far a programme can go also depends on the platform, since the requirements differ across land, air, sea, space and cyber defence sectors .
Why Licensed Production Alone Falls Short
Licensed production creates jobs and a visible factory. It does not automatically create three things a country needs from its defence industry.
Sustainment independence.
If spares, software updates and overhauls still depend on the OEM, the operational risk stays offshore.
A deep supplier base.
Real capability reaches down to tier-2 and tier-3 suppliers: castings, electronics, specialty materials. Without it, “indigenous content” can be a thin layer over imported sub-assemblies.
Design competence.
Without access to design authority and source-level data, the Indian partner cannot modify the system for local operating conditions or build the next generation.
What Policy Is Now Demanding: DAP 2026
The Ministry of Defence released the draft Defence Acquisition Procedure (DAP) 2026 in February 2026 for stakeholder comments, to replace DAP 2020. Based on the draft, three shifts matter for technology transfer:
Higher indigenous content
The requirement under Buy (Indian-IDDM) rises from 50% to 60% and Buy (Global) is proposed to carry 30% indigenous content.
Design and IP ownership over assembly
The draft shifts the emphasis from where equipment is made to who owns its design, IP, and source code.
Tighter verification
Indigenous content is calculated against a defined contract base price, with tier-wise supply-chain reporting.
Note: the draft was open for comment until March 2026. Check out the Ministry of Defence’s official channels for the final notified text before making commercial decisions.
For foreign OEMs entering the Indian defence market , this means a ToT offer built on kit assembly will score progressively worse. For Indian manufacturers, it means ToT partners should be chosen on how much design access and supplier-development support they will provide, not only on price.
From ToT to Capability: Five Markers
Drawing on the experience of our leadership team in advising on defence industrial partnerships, five markers separate transfers that mature from those that stall.
Phased localisation with named milestones.
Each phase has a target for indigenous content, a date and a verification method. “Maximum feasible localisation” is not a plan.
Supplier development built into the agreement.
The OEM commits to qualifying Indian sub-tier suppliers: audits, tooling support, first-article inspection. This is where indigenous content becomes real.
Clear IP and data-rights terms.
The agreement states what design data is transferred, who owns improvements, and whether the Indian partner can export the product.
Skilled workforce transfer.
Training covers production, quality assurance, testing and engineering change management, not just assembly operators.
A route to export.
Capability sustains itself when volumes exceed the domestic order book. Export rights and market-access terms should be settled upfront, not renegotiated later.
Common Pitfalls
Treating ToT as a procurement condition rather than a business plan
Both sides then optimise for compliance, not capability.
Under-pricing the absorption phase
Building indigenous supply chains costs more than importing and assembling, and the cost must be planned for.
Ignoring the government ecosystem
Approvals, testing, DRDO and DPSU interfaces, and procurement categories shape the timeline. Early coordination avoids avoidable delay.
Weak partner due diligence
A partner’s factory size says little about its engineering depth.
How Crescendo Defence Supports the Journey
Crescendo Defence is a defence industrial consultancy working across Land, Air, Sea, Space and Cyber. We help OEMs structure ToT agreements that meet policy requirements, and we help Indian manufacturers absorb technology in phases. To discuss a technology transfer programme, get in touch with our team.
For official policy documents, procurement categories and the indigenisation agenda, refer to the Department of Defence Production, Ministry of Defence .
Conclusion
A ToT agreement is a starting line. Capability is what remains when the OEM’s engineers leave: suppliers who can deliver, engineers who can modify, and a product that can sell beyond India’s borders. As policy moves from rewarding assembly to rewarding ownership of design, the partnerships that plan for this from day one will be the ones that last.
Disclaimer: This article is for general information and is not legal or regulatory advice. Policy provisions referenced are based on the draft DAP 2026 and may change in the final text.
Build lasting industrial capability in India.
Talk to Crescendo Defence about technology transfer, localisation and industrial partnerships.
Frequently Asked Questions
What is ToT in defence?
Transfer of Technology is the formal transfer of design, manufacturing and testing know-how from a technology owner to a partner, usually under a licence or joint venture agreement.
Does ToT guarantee indigenous content?
No. Indigenous content depends on how deeply the Indian partner, and its suppliers produce the system’s components. Verification norms are tightened under the draft DAP 2026.
Is ToT the same as co-development?
No. ToT passes existing know-how to a partner. Co-development shares design work and usually IP, and it aligns more closely with the policy emphasis on indigenous design.
What is the biggest risk in a defence ToT agreement?
Vague terms on data rights, localisation milestones and export permissions. Each is easier to settle at signing than during execution.