The import is the part people dread and it is genuinely the easy part, because nothing is written until you approve the preview. Here is how to get a clean result on the first attempt.
Prepare the file
Export what you have as CSV or Excel. Do not spend a day tidying it first, because the mapping step handles most of the mess. There are only three things worth fixing in advance.
Make sure the first row is a header row, that one row equals one asset, and that serial numbers are stored as text rather than numbers. That third one matters: spreadsheets silently convert long serial numbers into scientific notation, and once that has happened the original value is gone.
- One header row at the top, one asset per row below it
- Serial numbers and asset tags formatted as text, not numbers
- Merged cells removed, since they cannot be read reliably
- Dates in a single consistent format across the whole column
Map your columns
Upload the file and Eze IT lists your columns next to the fields it can map them to, guessing where the names are obvious. Confirm each one, point anything unusual at a custom field, and skip the columns you no longer need rather than importing clutter.
Where a column is missing entirely, set a default instead. If every row in the file is a laptop from the Denver office, set category and site as defaults and leave those columns out of the spreadsheet.
Save the mapping when you are done. Next quarter, the same export maps itself.
Read the preview properly
The preview is the whole point of the import step. It shows exactly how many records will be created, how many are duplicates of assets you already have, and how many rows will not validate.
Duplicates are matched on serial number, asset tag and MAC address. Decide whether to skip them or update the existing record with the newer values. Rows that fail validation are listed individually with the reason, usually a date that cannot be read or a required field left empty. Fix them in the preview rather than going back to the file.
Commit, then verify
Commit the import and Eze IT writes the records, usually in well under a minute for a few thousand rows. Then spend five minutes checking the result rather than assuming it worked.
Open three assets you know well and confirm the values are on the right fields. Filter by site and check the counts look plausible. Sort by purchase date and look at both ends, because bad date parsing shows up immediately at the extremes.
- Spot check three records you know the details of by heart
- Compare asset counts per site against your own expectation
- Sort by purchase date and inspect the oldest and newest rows
- Confirm owners resolved to directory accounts rather than plain text
If something went wrong
Every import can be reversed in a single action for thirty days. Open the import in the history view and choose to roll it back. Records created by that import are removed and nothing else in your workspace is touched, so you can correct the file and run it again without consequence.
Next
Label and scan with QR