AI ITAM Platform
IT Asset Management Software: The Features That Matter
An asset register in Excel answers “what do we have?” badly and “who approved that change?” not at all. Here is what an ITAM platform must add.
Key takeaways
- Keep your original columns — map, do not redesign.
- Validate IPs, MAC addresses, dates and duplicates before import.
- Assign owners and classification during cleansing.
- Use the asset ID as the stable key for updates.
Prepare the file
- Freeze a copy as the baseline.
- Remove totals, merged cells and title rows (or let the importer skip them).
- Make sure every row has a unique asset ID.
- Standardize statuses: in use, in store, in repair, retired, disposed.
Map the columns
Good importers recognize common headings and variants — “Serial No”, “S/N”, “Computer Name”, “Hostname” — and show the proposed mapping with confidence before anything is saved. Unmapped columns should be kept as additional data rather than dropped.
Validate
| Check | Typical problem |
|---|---|
| Unique IDs | Repeated asset IDs |
| IP addresses | Invalid ranges or text |
| MAC addresses | Wrong separators or length |
| Dates | Mixed formats |
| Owners | Blank owner fields |
| Classification | Missing confidentiality / integrity / availability ratings |
Load and reconcile
- Import into a test environment and review.
- Import to production, matching on asset ID.
- Re-run the import later to update — matched rows update, new rows create.
- Start a verification audit to confirm the register against reality.
After go-live
Stop editing the spreadsheet. Every change now runs through a lifecycle request with an approver, and exports keep the original column layout for anyone who still needs Excel.
Common migration mistakes
- Redesigning the column structure before migrating
- Dropping columns that “nobody uses” — until an auditor asks
- Importing without unique asset IDs
- Keeping the spreadsheet alive in parallel
- Skipping verification after go-live
Who should be involved
| Role | Contribution |
|---|---|
| IT asset manager | Owns the register and the migration |
| Service desk | Knows allocations and locations |
| Finance | Asset codes, cost and depreciation |
| Security | Classification and disposal rules |
| Internal audit | Agrees evidence expectations |
What changes for users
After migration, staff stop editing a shared file and start raising requests: allocate a laptop, transfer a server, return a phone. Each request goes to an approver and updates the asset automatically when fulfilled. Users see their own requests in an inbox, asset managers see everything awaiting approval, and auditors see the full history of every asset.
How NAZZTEC helps
NAZZTEC AI ITAM automates this end to end — with AI assistance, segregation of duties, analytics and signed reports — and is available as SaaS, in your private cloud or on-premises. Our consultants design and run the process alongside it through our IT Asset Management services.
Next step: request a demo of NAZZTEC AI ITAM or read more on the product page.
Frequently asked questions
Will we lose any columns?
Not with a mapping importer — every inventory column can be kept.
Can we import again later?
Yes; rows are matched on asset ID and updated.
What if the data is poor?
Import anyway with validation warnings, then use data-quality reports and verification audits to fix it.
NAZZTEC Editorial TeamWritten and reviewed by NAZZTEC practitioners. This briefing is general guidance, not legal advice.
