Do we need to replace Intune or Jamf to use AssetSonar?

No. AssetSonar is designed to work alongside a mobile device management (MDM) platform, not replace it. Microsoft Intune, Jamf, and Kandji keep managing enrollment, configuration, and compliance policies, while AssetSonar uses their device data for ownership, custody, lifecycle tracking, audit history, and reporting. AssetSonar integrates natively with all three and reconciles their data with agent, network scan, and purchase records into one asset record. The practical shortlisting question is which fields each MDM controls inside that record and how often it refreshes. AssetSonar lists hourly automated syncs for hardware discovery; confirm the cadence for each integration you plan to connect.

What should we bring to an AssetSonar demo to run the Lifecycle Reconciliation Test?

Bring real data for one or two laptops instead of relying on a vendor sample. Useful inputs include an MDM export from Intune or Jamf, the matching purchase order with warranty dates, the current owner and department from your HR or identity system, and the service tickets logged for each device. Include at least one known problem record, such as a duplicate serial number or a custodian who has left the company. Then ask AssetSonar to load the data, apply your field precedence, and walk the device through transfer, repair, offboarding, recovery, and redeployment. Count the manual corrections, consoles opened, and fields maintained twice. Real records expose conflicts that a prepared demo dataset usually avoids.

What should we clean up before connecting AssetSonar to our MDM and HR systems?

Fix the rules before fixing every record. Confirm the identifier that will join records across systems, usually the serial number, and list the assets where it is missing or duplicated. Make user email addresses consistent across AssetSonar, the identity provider, and the MDM, since custodian matching depends on them. Decide which source controls each field, and standardize group and location names. The AssetSonar getting-started guide recommends resolving duplicates, missing custodians, stale records, and source conflicts before enabling Auto Checkout or lifecycle automations. Connecting integrations before precedence is defined imports existing conflicts into the new record.

How does AssetSonar track devices that are not enrolled in an MDM?

Not every device reaches an MDM. Lab machines, shared workstations, network equipment, and older hardware often sit outside Intune or Jamf. AssetSonar collects data for these devices through its agent and through agentless network discovery, then compares network discovery data with MDM enrollment records to surface devices that appear on the network but are not managed. Those devices then join the same reconciled asset record as enrolled ones. During evaluation, confirm which operating systems the agent supports in your environment and what the network scan collects for printers, switches, and other devices that cannot run an agent.

Does AssetSonar keep service tickets on the same record as the asset?

Yes. AssetSonar includes IT service management (ITSM) alongside IT asset management (ITAM), and its IT Graph connects each asset to its user, installed software, licenses, tickets, and lifecycle history. Repair and warranty work stays attached to the device record, so a technician or auditor does not have to match tickets from a separate help desk to the right laptop. Teams that already run another service desk should decide whether to move ticketing into AssetSonar or keep the existing tool connected, and check which option keeps service history on the asset record. AssetSonar uses asset-based pricing; confirm current plan inclusions with EZO.

Does offboarding in AssetSonar cover software licenses as well as hardware?

Yes. AssetSonar starts offboarding when HR records a termination and creates one ticket covering hardware recovery, license revocation, and access follow-through. Because AssetSonar combines IT asset management with software asset management (SAM), that ticket can list both the departing employee's devices and the licenses tied to that user, so IT and finance can see which laptops need recovery and which seats can be reclaimed before renewal. The same reconciliation rule applies: license and user data must match the current custodian, or recovery and reclamation start with the wrong person. Confirm that the HR and license sources you use are supported.

What happens to an asset's history when a laptop is reimaged and returns with a new hostname?

A reimaged laptop often reports a new hostname and sometimes a new MDM enrollment. If an ITAM platform matches records on hostname, it creates a second asset and splits the device's assignment, repair, and warranty history across two records. AssetSonar matches agent, MDM, and network data by serial number, UDID, or configurable rules and merges duplicates into one record, so a hostname change alone should not create a new asset. Test it anyway: reimage a device, re-enroll it, and confirm the result is one updated record. Also ask how possible duplicates that fail the matching rules are flagged and reviewed.

How do we measure whether reconciliation work actually dropped after rollout?

Set a baseline before rollout, then measure the same items 6 months later. Useful measures include the number of duplicate records, assets assigned to people who have left the company, assets whose status differs between the ITAM platform and the MDM, open reconciliation exceptions, and the time a technician needs to confirm who holds a given device. Record each measure with a date and its source system so later comparisons use the same definitions. A falling exception count while the asset count holds steady or grows is the clearest sign that the platform is absorbing the reconciliation work instead of the IT team.

Who should own reconciliation exceptions on an IT team?

Ownership should follow the field in dispute, with one named person accountable for the exception queue. The IT asset manager typically owns precedence rules and lifecycle state, because those decisions affect audits, recovery, and spend. The SysAdmin or endpoint administrator owns integration health: failed syncs, enrollment gaps, and discovery coverage. HR or identity data owners correct employee and department records at the source instead of inside the ITAM platform. The service desk reports mismatches found while working tickets. Without a named owner, exceptions age in the queue and teams drift back to spreadsheets to work around them.

How often should each data source sync with an ITAM platform?

Match the sync cadence to how quickly each field changes and how costly a stale value is. Device state from Intune or Jamf changes often and drives recovery and security decisions, so it needs the most frequent refresh the integration supports. Employee and department data matters most at the moment of change, so event-based updates from HR or identity systems are more useful than a fixed schedule. Purchase and warranty data changes rarely and can sync when a new order or contract arrives. Ask each vendor for the actual refresh frequency or trigger of every integration; AssetSonar, for example, lists hourly automated syncs for hardware discovery. Set exception alerts around those intervals.

AssetSonar Blog Stop Reconciling Asset Data

The Easiest ITAM Tool Is the One That Stops Making You Reconcile Asset Data

Published on November 11, 2026

Last updated on November 12, 2026

Farhan Ul Haq
7 minutes

Table of Contents

A laptop can exist in five systems at once. Microsoft Intune knows its enrollment and compliance state. HR knows who holds it. Procurement knows the purchase order and warranty term. The service desk holds its asset-linked tickets.

The IT asset management (ITAM) platform should tell the SysAdmin which fact is current. When records disagree, someone has to pick a winner. If the SysAdmin has to do that every week, the platform isn’t easy to use, no matter how clean its dashboard looks.

Ease in ITAM is not just fewer clicks. It is fewer contradictions.

Key Takeaways:

The easiest IT asset lifecycle management software reconciles device, user, procurement, and service data into one asset record, then automates lifecycle handoffs from it.
Judge ease by the manual record repair left 6 months after rollout.
Set source authority first: which system wins each field, which identifier joins records, and who owns exceptions.
Ask vendors to break the record in a demo, then count the manual fixes.
A connected source of truth needs clear field rules, not one tool.

SysAdmins don’t hate ITAM. They hate maintaining it.

Most SysAdmins and IT asset managers I talk to want fewer places to fix assets, not another place to view them. The daily friction looks like this:

Duplicates: a procurement import and an MDM enrollment create two records for one serial number.
Stale owners: the custodian field still shows the employee who had the laptop in March.
Wrong locations: an office move reached HR but never the asset record.
Inconsistent status: ITAM says “In Use” while Intune shows the device was wiped.
Missing warranty data: coverage dates sit in a vendor portal nobody synced.
Orphaned offboarding records: a disabled account still has 2 devices assigned.

Each manual fix takes minutes. Together, they become a standing chore no vendor demo shows, and IT leaders feel it at audit time and renewal. That chore is administrative drag, and it is the real measure of whether ITAM software is easy to use.

Why can’t a clean interface fix fragmented asset data?

The problem sits beneath the interface. Intune, Jamf, Kandji, and SCCM each legitimately own different device data, and organizations have good reasons to keep them.

The trouble starts when they describe one device differently:

Ownership: the MDM shows one primary user, the identity system shows another.
Compliance: one console reports the device as compliant, another flags a missing patch.
Device identity: a reimaged laptop returns with a new hostname and looks like a new asset.
Timestamps: Jamf recorded a check-in yesterday, while the last inventory scan ran 3 weeks ago.

A better screen only highlights these conflicts; it cannot say which version to trust. That takes asset data reconciliation: matching records for the same device across systems and deciding which source wins each field.

Which source should own each asset field?

The easiest ITAM setup starts with a decision most teams skip: source authority, meaning which system wins each field when records conflict. A typical model:

Asset field	Authoritative source	Why
Device identity (serial number, model, OS)	MDM, agent, or network discovery	Observed directly
Employee, department, manager	HR system or identity provider (Entra ID, Okta)	Employment changes start here
Purchase details (PO, cost, vendor, warranty start)	Procurement or purchasing records	Finance relies on them
Service and repair history	ITSM or ITAM ticketing	Tickets are worked there
Lifecycle state (in stock, assigned, in repair, retired)	ITAM platform	Only ITAM sees the full lifecycle

Pick the identifier that joins records across systems; serial number is usually most reliable, since hostnames change and asset tags get missed. Set a sync cadence per source. Name an exception owner for records that still disagree.

Why does ITAM automation only help when the record is right?

ITAM automation acts on whatever record it finds, so a duplicate or stale owner gets repeated, only faster.

When HR marks an employee as departed, the ITAM platform flags their hardware for recovery. If the laptop changed hands 2 months ago and the custodian field never updated, the workflow chases the wrong person while the actual device goes unrecovered.

AssetSonar documentation recommends configuring discovery and identity sources, users, groups, and locations before enabling downstream lifecycle automations. On a clean record, automation removes work; on a messy one, it creates tickets.

The first job of ITAM automation is to move the right record. Speed comes second.

Where does lifecycle friction actually appear?

Lifecycle friction appears at handoffs, where an asset changes systems and its record can split or go stale.

Handoff	What should happen	What breaks when it doesn’t
Procurement to discovery	Purchased and discovered records merge into one	Two records for one serial number
Discovery to assignment	The user-device relationship stays current	Custodian shows a former owner
Assignment to service	Repair history attaches to the same asset	Service history scattered across tickets
Employment to offboarding	Departure triggers device recovery against current custody	Recovery requests sent to the wrong person
Recovery to redeployment	Ownership changes without rebuilding the asset	Prior history lost on the new record
Redeployment to retirement	History survives through final disposition	No audit evidence for disposal

Which ITAM platforms create the least reconciliation work?

This comparison covers six platforms: AssetSonar, InvGate Asset Management, Freshservice, ManageEngine AssetExplorer, Snipe-IT, and Oomnitza. Details were checked against vendor pages on November 9, 2026.

AssetSonar

AssetSonar is EZO’s IT management product, connecting ITAM, ITSM, and SAM around one asset record. It matches agent, MDM, and network scan data by serial number, UDID, or configurable rules; merges duplicates into one record; and automates lifecycle work from it.

AssetSonar fits best when IT runs several endpoint, identity, and service tools and wants one lifecycle record for IT, the service desk, and finance. Field authority is set during configuration, so ask the demo to apply your precedence rules to your data.

InvGate Asset Management

InvGate Asset Management combines an endpoint agent with agentless network discovery over SNMP, WMI, SSH, and Nmap, and integrates natively with InvGate Service Management. Test how it handles a discovered device that conflicts with an imported record, and how identity changes flow in.

Freshservice

Freshservice is an ITSM platform with built-in asset management and a CMDB. Its basic discovery uses an agent and a probe, while Advanced ITAM routes MDM and discovery data through Device42. Test which tier you are buying and where reconciliation happens in it.

ManageEngine AssetExplorer

ManageEngine AssetExplorer covers a broad lifecycle scope, including purchase orders with approvals, contracts, software license compliance, and disposal. Test how many of those fields admins maintain by hand and how discovery and procurement conflicts resolve.

Snipe-IT

Snipe-IT, the simplicity benchmark here, is an open-source tool known for simple check-in and check-out custody tracking. It ships sync adapters for MDMs including Intune, Jamf, and Kandji, plus LDAP and SCIM user sync. Is simplicity still an advantage if conflicts between those sources stay manual? For a small, stable fleet, it may be.

Oomnitza

Oomnitza, the orchestration benchmark here, is an enterprise technology management platform that aggregates and reconciles data through agentless, API-based integrations and low-code workflows. Does deeper orchestration save enough lifecycle work to justify its configuration effort?

How do you run the lifecycle reconciliation test?

The Lifecycle Reconciliation Test is a vendor evaluation method that measures how much manual cleanup an ITAM platform leaves once its integrations are running. Instead of asking to see the dashboard, ask the vendor to break the record.

Step 1: Set up the scenario. One laptop exists in Intune, procurement, the HR or identity system, and the ITAM platform. Walk it through 7 events:

The employee changes department.
The device is repaired.
Warranty data updates.
The employee leaves.
The asset is recovered.
The asset is redeployed to someone else.
One upstream source still holds the old owner.

Then ask: Which record wins? How was the conflict detected? What does the SysAdmin fix manually?

Step 2: Check every lifecycle stage.

Stage	SysAdmin question
Discover	Do assets appear automatically from agent, MDM, or network sources?
Reconcile	What happens when two sources describe one device differently?
Identify	How are duplicates prevented or merged?
Assign	Does custodian data stay aligned with identity systems?
Change	Do location, department, and state update when upstream systems change?
Support	Do service and warranty history update the same record?
Recover	Does offboarding surface assigned hardware automatically?
Redeploy	Can a returned asset re-enter inventory on the same record?
Retire	Does retirement close out the record across systems?
Audit	Is the full history visible without merging exports?
Maintain	How much manual cleanup remains once integrations run?

The last row matters most.

Step 3: Score the result. Count:

Alerts raised for the conflict
Conflicts resolved by reconciliation logic
Manual corrections
Consoles opened to verify the answer
Fields maintained in more than one place
Lifecycle steps remembered rather than triggered

The lowest count wins, no matter what the interface looks like.

Does one source of truth mean one tool?

No. A SysAdmin may still need Intune for Windows, Jamf for Macs, an HR system, and a service desk. Ease comes from those tools feeding one trusted lifecycle record, not from pretending they all do the same job.

In ITAM, a connected source of truth is one record the team agrees to act on, built from many authoritative systems with clear rules for which field wins.

Which ITAM platform is easiest for your team?

The easiest platform depends on what you are trying not to maintain.

Platform	Easiest when
AssetSonar	Reducing reconciliation across many IT sources is the priority
InvGate Asset Management	Straightforward workflows matter more than ecosystem depth
Freshservice	ITSM is already central to how your IT team operates
ManageEngine AssetExplorer	Detailed lifecycle administration outweighs a lighter experience
Snipe-IT	Simple custody tracking matters more than automation
Oomnitza	Enterprise orchestration is worth the added setup complexity

The best ITAM UX is the record you no longer have to question

SysAdmins do not need a system that tells them more. They need one they trust enough to stop checking everything twice.

The easiest ITAM platform turns fragmented device, user, procurement, and service data into a lifecycle record your team can act on without first reconciling it.

Try this before your next audit. Take 10 devices that changed hands last quarter. Can your team say which record was used for each, why that source won, and who approved any exception?

See how AssetSonar handles the handoffs

Bring one real laptop lifecycle, from purchase and MDM enrollment through assignment, recovery, redeployment, and retirement. See how AssetSonar keeps the record aligned across each change.

Was this helpful?

Thanks for your feedback!

Farhan Ul Haq

Customer Success Team Lead

EZO

Farhan Ul Haq is Customer Success Team Lead at EZO, helping organizations strengthen IT asset management adoption, retention, and long-term value. With experience in application analysis and process optimization, he brings a practical perspective to customer success, ITAM implementation, and data-driven growth. He holds a master’s degree in IT Systems Analysis.

Frequently Asked Questions

Do we need to replace Intune or Jamf to use AssetSonar?
No. AssetSonar is designed to work alongside a mobile device management (MDM) platform, not replace it. Microsoft Intune, Jamf, and Kandji keep managing enrollment, configuration, and compliance policies, while AssetSonar uses their device data for ownership, custody, lifecycle tracking, audit history, and reporting. AssetSonar integrates natively with all three and reconciles their data with agent, network scan, and purchase records into one asset record. The practical shortlisting question is which fields each MDM controls inside that record and how often it refreshes. AssetSonar lists hourly automated syncs for hardware discovery; confirm the cadence for each integration you plan to connect.
What should we bring to an AssetSonar demo to run the Lifecycle Reconciliation Test?
Bring real data for one or two laptops instead of relying on a vendor sample. Useful inputs include an MDM export from Intune or Jamf, the matching purchase order with warranty dates, the current owner and department from your HR or identity system, and the service tickets logged for each device. Include at least one known problem record, such as a duplicate serial number or a custodian who has left the company. Then ask AssetSonar to load the data, apply your field precedence, and walk the device through transfer, repair, offboarding, recovery, and redeployment. Count the manual corrections, consoles opened, and fields maintained twice. Real records expose conflicts that a prepared demo dataset usually avoids.
What should we clean up before connecting AssetSonar to our MDM and HR systems?
Fix the rules before fixing every record. Confirm the identifier that will join records across systems, usually the serial number, and list the assets where it is missing or duplicated. Make user email addresses consistent across AssetSonar, the identity provider, and the MDM, since custodian matching depends on them. Decide which source controls each field, and standardize group and location names. The AssetSonar getting-started guide recommends resolving duplicates, missing custodians, stale records, and source conflicts before enabling Auto Checkout or lifecycle automations. Connecting integrations before precedence is defined imports existing conflicts into the new record.
How does AssetSonar track devices that are not enrolled in an MDM?
Not every device reaches an MDM. Lab machines, shared workstations, network equipment, and older hardware often sit outside Intune or Jamf. AssetSonar collects data for these devices through its agent and through agentless network discovery, then compares network discovery data with MDM enrollment records to surface devices that appear on the network but are not managed. Those devices then join the same reconciled asset record as enrolled ones. During evaluation, confirm which operating systems the agent supports in your environment and what the network scan collects for printers, switches, and other devices that cannot run an agent.
Does AssetSonar keep service tickets on the same record as the asset?
Yes. AssetSonar includes IT service management (ITSM) alongside IT asset management (ITAM), and its IT Graph connects each asset to its user, installed software, licenses, tickets, and lifecycle history. Repair and warranty work stays attached to the device record, so a technician or auditor does not have to match tickets from a separate help desk to the right laptop. Teams that already run another service desk should decide whether to move ticketing into AssetSonar or keep the existing tool connected, and check which option keeps service history on the asset record. AssetSonar uses asset-based pricing; confirm current plan inclusions with EZO.
Does offboarding in AssetSonar cover software licenses as well as hardware?
Yes. AssetSonar starts offboarding when HR records a termination and creates one ticket covering hardware recovery, license revocation, and access follow-through. Because AssetSonar combines IT asset management with software asset management (SAM), that ticket can list both the departing employee's devices and the licenses tied to that user, so IT and finance can see which laptops need recovery and which seats can be reclaimed before renewal. The same reconciliation rule applies: license and user data must match the current custodian, or recovery and reclamation start with the wrong person. Confirm that the HR and license sources you use are supported.
What happens to an asset's history when a laptop is reimaged and returns with a new hostname?
A reimaged laptop often reports a new hostname and sometimes a new MDM enrollment. If an ITAM platform matches records on hostname, it creates a second asset and splits the device's assignment, repair, and warranty history across two records. AssetSonar matches agent, MDM, and network data by serial number, UDID, or configurable rules and merges duplicates into one record, so a hostname change alone should not create a new asset. Test it anyway: reimage a device, re-enroll it, and confirm the result is one updated record. Also ask how possible duplicates that fail the matching rules are flagged and reviewed.
How do we measure whether reconciliation work actually dropped after rollout?
Set a baseline before rollout, then measure the same items 6 months later. Useful measures include the number of duplicate records, assets assigned to people who have left the company, assets whose status differs between the ITAM platform and the MDM, open reconciliation exceptions, and the time a technician needs to confirm who holds a given device. Record each measure with a date and its source system so later comparisons use the same definitions. A falling exception count while the asset count holds steady or grows is the clearest sign that the platform is absorbing the reconciliation work instead of the IT team.
Who should own reconciliation exceptions on an IT team?
Ownership should follow the field in dispute, with one named person accountable for the exception queue. The IT asset manager typically owns precedence rules and lifecycle state, because those decisions affect audits, recovery, and spend. The SysAdmin or endpoint administrator owns integration health: failed syncs, enrollment gaps, and discovery coverage. HR or identity data owners correct employee and department records at the source instead of inside the ITAM platform. The service desk reports mismatches found while working tickets. Without a named owner, exceptions age in the queue and teams drift back to spreadsheets to work around them.
How often should each data source sync with an ITAM platform?
Match the sync cadence to how quickly each field changes and how costly a stale value is. Device state from Intune or Jamf changes often and drives recovery and security decisions, so it needs the most frequent refresh the integration supports. Employee and department data matters most at the moment of change, so event-based updates from HR or identity systems are more useful than a fixed schedule. Purchase and warranty data changes rarely and can sync when a new order or contract arrives. Ask each vendor for the actual refresh frequency or trigger of every integration; AssetSonar, for example, lists hourly automated syncs for hardware discovery. Set exception alerts around those intervals.