ITAM vs SAM comes down to scope and stakes. IT asset management tracks every IT asset you own, from purchase to disposal. Software asset management is the part that proves you are licensed for what you run and stops you paying for what nobody uses. The two should share data, but they need separate owners.
Because both start from the same inventory, it is tempting to fold SAM into ITAM and give one team both jobs. This article explains why we advise against it, and what the two disciplines should share instead.
In short
- ITAM answers what you have, where it is and who owns it. SAM answers whether you are licensed for what you run, and what you are paying for that nobody uses.
- Both rely on the same discovery data and hardware record. They should not rely on the same owner, because the skills and the stakes are different.
- A SAM mistake is priced by the publisher. At Oracle’s 15 September 2026 list prices, a shortfall of 12 Database Enterprise Edition processors is US$570,000 in licenses before support.
- One platform can hold both records. What matters is that someone who knows each publisher’s rules owns the license position.
ITAM vs SAM at a glance
| IT asset management (ITAM) | Software asset management (SAM) | |
|---|---|---|
| The question | What IT assets do we have, where are they and who owns them? | Are we licensed for what we run, and what are we paying for that nobody uses? |
| What it records | Devices, software installations, warranties, maintenance contracts, users and locations | Installations, entitlements, contracts and the license metric each product is sold on |
| The rules it applies | Internal policy, warranty and maintenance terms | Each publisher’s license rules, such as Oracle’s core factor, IBM’s sub-capacity conditions and Microsoft’s product use rights |
| The cost of a mistake | A lost device, a missed warranty, a late replacement | An audit finding priced by the publisher, or support paid every year on licenses nobody uses |
| Its calendar | Every day: each request, move and disposal | The publisher’s: renewals, true-ups, audits, and IBM’s quarterly ILMT reports |
| Who runs it | IT operations, the service desk, procurement | Licensing specialists, working with procurement and legal |
ITAM, SAM and HAM
ITAM is the umbrella. Under it sit hardware asset management (HAM), which looks after devices across their life, and software asset management, which looks after licenses. HAM and the general asset register are operational work: keeping records accurate as equipment is bought, moved, repaired and retired. SAM is commercial and contractual work, and that difference is the reason to keep it apart.
Why SAM should not sit inside ITAM
The skills are different
Running an asset register well takes discipline with process and data. Running a license position takes knowledge of each publisher’s rules and contracts: how Oracle counts processors, when IBM accepts sub-capacity pricing, which Microsoft agreement and use rights apply. A good asset manager is rarely also a licensing specialist for four publishers, and the role should not assume they are.
An installation count is not a license position
An asset register counts installations. A publisher counts license requirements, and the two can be far apart. Forty installations of a database on a VMware cluster can need far more licenses than forty, or far fewer. When SAM sits inside ITAM, the installation count tends to become the answer, and the gap only appears when an auditor builds the effective license position for you.
The stakes are different
A missing laptop costs the price of a laptop. A licensing gap is priced by the publisher, at list, and on Oracle it carries annual support at 22% of the license fee. Shortfalls of that size need someone accountable for them by name, with the authority to act before a renewal or an audit sets the timetable.
The calendar is different
ITAM runs with the service desk, one request at a time. SAM runs on the publishers’ dates: renewals, true-ups, ULA certifications and audits. Folded into daily asset work, those dates arrive with no license position ready.
What ITAM and SAM should share
Keeping SAM separate does not mean keeping two inventories. The two disciplines should share one discovery process and one hardware record, because SAM cannot count licenses priced per processor or per core without the processor model and core count that ITAM already holds. Entitlements, contracts and maintenance records can sit in the same repository too.
Our own platform, Euladox, is built that way: it keeps hardware, software, contracts and entitlements in one database, from deployment to disposal. What stays separate is ownership. The license position, the reports for each publisher and the response to an audit belong to SAM.
How to set it up
- One discovery, two owners. Run discovery once and give both teams the data. Name one owner for the asset register and another for the license position.
- Give SAM the contracts. If the people building the license position cannot see the agreements, they are reconciling against memory.
- Keep the reports apart. ITAM reports what you have. SAM reports, for each publisher, what you own against what you need.
- Agree the handoff. A new server, virtual machine or cluster change should trigger a license check for every product priced per processor or per core.
Our guide to the software asset management process walks through the SAM side step by step. If you would rather not build the team, our SAM managed services run it for you, on Euladox, alongside your own ITAM.
Questions we are asked about ITAM and SAM
What is the difference between ITAM and SAM?
ITAM tracks every IT asset across its life: what you have, where it is and who owns it. SAM deals with software licenses: whether you are licensed for what you run, and what you are paying for that nobody uses. ITAM is operational work; SAM is commercial and contractual work.
Is SAM part of ITAM?
SAM sits under the ITAM umbrella and uses ITAM’s data. It should still have its own owner, because building a license position takes publisher licensing knowledge that general asset management does not need.
What is the difference between ITAM, SAM and HAM?
ITAM is the whole discipline. HAM is the hardware half: devices, warranties and maintenance across their life. SAM is the software half: installations, entitlements, contracts and compliance with each publisher’s rules.
Can one tool do both ITAM and SAM?
Yes. Euladox, for example, holds hardware, software, contracts and entitlements in one database. The tool can be shared. The responsibility for the license position should not be shared with general asset work.
Anil Nahata
Co-founder of Rythium Technologies and its designated partner since 2015. Anil co-leads Rythium’s practice, bringing deep software asset management and commercial negotiation experience across Oracle, Microsoft and the wider publisher landscape.
Before Rythium, Vice President heading the telecom towers infrastructure business at Reliance Communications, and its group Chief Procurement Officer. More than two decades across the telecom, software and financial industries.
See more of our analysis in Google: add Rythium as a preferred source