Moving your asset register from Excel to asset management software

Almost every asset register starts in Excel, and many should stay there for a while. A spreadsheet is free, familiar and flexible, and for a single person with a few hundred assets it works.

This article is for the organizations that have outgrown it, and for the question that comes next: how do you move without losing what you have? The short version is that migration is mostly a cleaning exercise, with a short import at the end.

When Excel stops working

You do not need software on day one. These are the signs it is time.

• More than one person edits the file, and there are several copies of “the latest”.
• You cannot say who changed a cell, or what it was before.
• The register and the floor disagree, and checking takes days of matching lists.
• Depreciation is reproducible only by the person who built the sheet.
• You have several branches or companies, and each has its own file or tab.
• Staff in the field cannot use it, so counts are on paper and typed up later.

What software gives you that a spreadsheet does not

Task	Spreadsheet	Asset management software
Finding an asset	Search the file, hope it is the latest	Scan the tag, see the record and its history
Physical verification	Print lists, tick, match for days	Scan continuously, reconciliation is automatic
Who changed what	Unknown	Logged: who, when, before and after
Depreciation	Formulas that break when rows move	Calculated by policy, reproducible
Many branches or companies	One file each	Switch company, data kept separate
Field work	Laptops and paper	Phone app that works offline

Before you move: clean the register

This is where the time goes, and where the value is.

Make the identifiers unique

Each asset needs a unique number. Sort your sheet by asset number and look for repeats. If you have no numbers, decide on a pattern now. Check serial numbers too: the same serial on two rows is a duplicate, or a typing error.

Make locations a list

Collect every distinct location in the sheet and look at it. You will find the same place spelled several ways. Decide the correct name for each, and replace the others. If you have places inside places, write them as a path, such as Nairobi HQ > Floor 2 > Room 4.

Do the same for categories, departments and suppliers

The same logic applies. Pick the names you want, and make the sheet match.

Fix the dates and the amounts

Dates should be real dates in one format. Amounts should be numbers, with no currency symbols or text. A currency column is better than “KES” typed into each price.

Remove what is gone

If you know an asset was disposed of, mark it. If you are sure it no longer exists, do not carry it across as if it did.

Choose what to bring

Not every column deserves a place in the new system. A good set to import is: asset number, name, category, manufacturer, model, serial number, status, condition, location, department, supplier, purchase order, invoice, purchase date, in-service date, cost, currency, and warranty dates. Notes can come across too. Our register template has exactly those columns.

The import itself

In VexCloud AMS, an import has four steps.

1. Upload the Excel or CSV file. The first sheet is read.
2. Map the columns. The headers are matched for you, and you confirm each one.
3. Validate. The system runs the whole file through the real rules without saving anything, and shows what would happen: duplicate numbers, unknown locations, invalid dates, how many new locations or categories would be created.
4. Import. Rows without problems are written. Rows with problems are listed with the reason, and you can download them with their original columns, fix them in Excel and load them again.

Created records carry their normal history, marked as coming from an import, so you can always see where they started.

After the import: check it

An import is not finished until you have compared it with the original.

• Count the rows. Does the number of assets match the number you expected, after removing what you chose to leave out?
• Spot check. Open ten assets at random and compare each with the sheet.
• Check the totals. Compare total cost with the sheet.
• Check the locations. Does the tree look like your organization?

Keep the original file, unchanged, in a safe place. It is the evidence for what you brought across.

Problems you will hit

“Duplicate asset number” on rows you thought were different. Look at trailing spaces and upper and lower case. ORG/001 and ORG/001 are the same number to a person and different to a spreadsheet. Trim the column before you import.

Dates that came across as numbers. Excel stores dates as numbers behind the format. If a column shows 45123 instead of a date, the format was lost somewhere. Reformat the column as a date, or write it as YYYY-MM-DD.

Locations created in three spellings. If you chose to create missing locations, a stray capital or an extra space makes a new place. Check the list of new locations in the preview before you confirm, and fix the sheet, not the system.

Costs that do not add up. Text such as “KES 90,650” cannot be read as a number. Keep the number in the cost column and the currency in its own column.

A status the system does not know. Statuses are lists, and your sheet may use words that are not in them. Map them to the nearest status, or add the status first.

Serial numbers that are not unique. Some items have none, and some have placeholders such as “N/A” or “000000”. Leave the cell empty rather than inventing a value, and let the verification catch them.

Then verify

An imported register is still the register you had. It is more usable, but it is not more true. The step that makes it true is a physical verification: load the expected assets for an area, scan what is there, and settle the differences. Start with one department, learn what your organization’s exceptions look like, and then go wider.

If your assets are not tagged yet, or the tags are tired, tag as you verify. Vexar Solutions can tag on site and hand the register over in a form that loads straight into VexCloud AMS.

A realistic plan

Week	What happens
1	Decide the scope. Export the current register. Fix numbers, locations and categories.
2	Finish cleaning. Import a sample of rows to test the mapping.
3	Import the whole file. Resolve what validation raised. Compare with the original.
4	Verify one department. Tag what is not tagged. Go live.

The first import is rarely the last. Each correction you make in the new system is one the spreadsheet never needed to explain, and the register gets better every time somebody scans something.