Starting your equipment management in Excel or Google Sheets is the right call. But spreadsheets eventually hit five limits: simultaneous editing, search, bookings, reminders, and updates from a phone. This guide covers how to stretch a spreadsheet further, the five steps to move to a dedicated system, and the data-migration traps to avoid.
You couldn’t save the equipment sheet because someone else had it open. A projector that was supposed to be checked out is somehow back on the shelf. The quantity column quietly stopped matching what’s actually on hand. Moments this small are usually what make people wonder whether their equipment spreadsheet is reaching its limit. In most organizations, tracking equipment in Excel or Google Sheets started without anyone deciding on it. And because nobody remembers starting, it’s just as hard to tell when to stop.
This article gives spreadsheets full credit for what they do well, then walks through the warning signs, the workarounds that can keep a sheet going, and the concrete steps and pitfalls of moving to a dedicated system. To be clear up front: we don’t think every organization should switch. The goal is that by the end, you have what you need to decide which camp you’re in.
For most organizations, starting equipment management in Excel or Google Sheets is the most sensible choice available. As a first move, nothing is easier.
There are three reasons. First, it costs next to nothing. The tool is already in the building, so there’s no purchase approval and no contract. Second, it’s extremely flexible. “Add a warranty-expiry column just for this item” or “split the sheet by department” can be handled on the spot. Where a dedicated system might mean changing settings or asking for a new feature, a spreadsheet just needs one more column. Third, anyone can use it. New team members need almost no training, because hardly anyone has never touched a spreadsheet.
In fact, if your organization fits the following, there’s no need to force a move to a dedicated system.
If that’s how things run, keep going. Changing tools always costs something: people have to relearn how to do things, and the migration itself takes work. There’s no reason to pay that price up front for a process that isn’t causing problems. The rest of this article is about the other case, where a process that used to work has, at some point, stopped working.
The limit arrives after small frustrations pile up. Then one day it clicks: this isn’t about being more careful; it’s a problem with the system. These are the five that come up most often.
Two people have the shared file open at once, and one person’s changes get overwritten. Or you get “This file is in use by another user” and can only open it read-only. If your Excel file lives on a file server or in cloud storage, this is hard to avoid. It’s always when you need to fix something quickly that the file won’t open, and that wears people down.
Moving to Google Sheets solves simultaneous editing itself, but a different problem shows up. When two people change the same cell for different reasons, whoever edits last wins. Version history will tell you who changed what and when, but almost nobody checks it in day-to-day work. By the time anyone notices, the quantity column no longer matches reality.
Once you pass about 100 items, searching gets much harder. The same model is entered as “EOS R6”, “EOS-R6”, and “Canon EOS R6”, so a search doesn’t find it on the first try. Filtering by category doesn’t help much either, because people categorize things differently. The list exists, but it takes minutes to reach the one row you need.
The bigger problem is that the physical item carries no information. Pick up a camera from the shelf, and nothing tells you which row of the sheet it belongs to. You can go from the data to the item, but not from the item to the data. During a stocktake, you end up doing that reverse lookup once for every item you own.
Try tracking “I need the projector next Tuesday” in a spreadsheet and things suddenly get difficult. You can add date columns, but checking whether two bookings for the same equipment overlap still comes down to someone eyeballing it. That’s even harder for items you have more than one of. Reading at a glance how many of your three units are free on a given day is not realistic.
So “Is it okay if I use this?” goes back to being a conversation, in person or in chat. The sheet exists, but the actual coordination happens outside it. At that point the sheet only holds an after-the-fact record, and that record usually gets put off too.
A spreadsheet tells you nothing unless you go and look. You can add a due-date column, but nothing alerts anyone when the date arrives. Conditional formatting can turn the cell red, but only people who open the file will see it.
In organizations where equipment is lent out routinely, this leads straight to missing items. Reminding people over and over doesn’t fix it; without something that actually prompts them, it keeps happening. The borrowers aren’t acting in bad faith. They just forget.
When people take equipment out, they’re rarely at a desk. They’re in the storeroom, on site, at a shoot. Opening a spreadsheet on your phone there, scrolling sideways across a wide table to find the right row, then tapping a tiny cell to type into it: try it once and you’ll see it doesn’t work in practice.
That’s when “I’ll enter it all later” starts. Information entered later, in one batch, is rarely accurate. And looking at the sheet, you can’t tell whether a row is up to date or has been left alone. Once “you can’t trust that sheet” becomes the shared view on the team, the process has already failed.
Even if a few of those signs sound familiar, you don’t need to decide on a switch right away. Changing how you use the sheet can fix a good share of the problems. Here are the three most common workarounds, with what each one gets you and where it stops helping.
The first is data validation. Turn the status column into a dropdown so only three values can be chosen: Available, Checked out, In repair. Make the storage-location column pick from a list of existing locations too. That alone stops most inconsistent entries. It takes a few minutes to set up and costs nothing. If you’re going to change anything, start here.
It has limits, though. Validation only protects cells when someone types into them directly. New items added as whole rows, or data copied and pasted in from another sheet, can end up outside the rule. And if someone removes the rule, nothing will tell you. In the end, the only way to know whether it’s being followed is for someone to go and look.
The second is tightening sharing and permissions. Limit who can edit, and give everyone who only needs to look view-only access. Use sheet protection to lock formula columns and header rows. Editing collisions and accidental deletions drop noticeably. In Google Sheets, version history and cell comments also leave a record of who changed what, and why.
But the fewer people who can edit, the slower updates get. If the people on site can’t fix the sheet themselves, every change waits on whoever owns it. Tighter control means staler information; fresher information means looser control. No amount of clever settings resolves that tug-of-war.
The third is building a template and a definitions sheet. Write a one-page reference that defines what each column means, and spell out required fields, naming rules, and the list of categories. Document the steps for registering a new item as well. That way, registrations stay consistent even when the person in charge changes. This work also isn’t wasted if you migrate later: it’s exactly Step 1 of the migration process described below.
The limit is that a template assumes people will read it. Whether the rules are followed is left to each person, and there’s no way to catch it when they aren’t. And the more rules you add, the more there is to remember.
| Workaround | What you get | What it can’t fix |
|---|---|---|
| Data validation and dropdowns | Far fewer inconsistent entries and typos. Takes minutes to set up | Added rows and pasted data can bypass it. Nobody notices if it’s removed |
| Sharing settings and sheet protection | Prevents editing collisions and accidental deletions. Keeps a history | The fewer editors, the slower the updates and the staler the data |
| Templates and a definitions sheet | Less reliance on one person; items can still be registered after a handover | No way to tell whether it’s followed. More rules to remember |
All three assume people will run the process correctly. While the group is small and stable, that assumption holds. It starts to break down when more people get involved, or simply when things get busy.
Item count alone doesn’t decide whether to switch. Count how many of these seven statements apply to you.
If three or more apply, it’s time to start looking at dedicated systems. If zero to two apply, the workarounds in the previous section still have plenty of room to help. If five or more apply, your sheet has probably already lost a lot of accuracy. In that case, you’ll get there faster by first figuring out how to clean up your current data, before choosing a tool.
Migration sounds like a big project, but for equipment management the work is fairly well defined. Do it in the right order and you’ll have something working in anywhere from a few days to about two weeks.
Don’t export straight away. Clean up the sheet you have first. Delete rows for equipment you no longer use. Standardize category names. Make model numbers consistent. Check that the core columns (name, model number, quantity, storage location) are filled in on every row. It’s unglamorous work, but it pays off more than any other part of the migration.
Skip this step and you just move messy data into a new container. Fixing things after the migration always takes more work than fixing them before. Once this is done, most of what’s left is routine.
Once the list is clean, export it in CSV format. In Excel, use Save As and choose CSV UTF-8. In Google Sheets, go to File > Download > Comma-separated values (.csv). Export a single sheet only. If your data is split across several sheets by department or year, combining them into one beforehand is the safer approach.
This is also the time to remove merged cells, subtotal rows, and any notes or memo rows inside the sheet. A CSV can only express “one row = one record”, so anything added for looks becomes noise. Row 1 holds the headers and nothing else; every row after that is data. Get it into that shape and the odds of the import going wrong drop sharply.
After importing the CSV, always reconcile the counts. Does the number of imported records match the number of rows in the original? Does the total quantity match? Checking just those two things will catch any major gaps. If you record the numbers once, right after the migration, you’ll later be able to trace when things started drifting.
If some rows fail to import, look into why right away rather than leaving them. The cause is usually simple: text in the quantity column, or a required column left blank. With a tool that makes you redo the entire import, every faulty row sends you back to the beginning. It’s worth checking in advance whether you can fix just the failed rows and import them separately.
Putting QR labels (or similar) on the physical items is the most time-consuming part of the migration. Try to label everything in one go and you’ll usually stall partway, leaving a half-finished mix of labeled and unlabeled items.
The better approach is to start with the items that get checked out most often. The more an item moves, the more likely its records drift, and the more a label helps. Label the top 20% first and you’ll cover most of your day-to-day activity. Items on shelves that never move can be labeled a few at a time during your next stocktake.
Only print as many labels as you can stick on that day. Once a printed label sits unused, nobody remembers where it was meant to go, and it ends up lost in a drawer.
Finally, invite the people who actually handle the equipment. The key here is to make the old sheet reference-only and have a single place where updates happen. If you keep updating both, nobody knows which one is right, and eventually nobody trusts either. Rather than deleting the old file, switch it to view-only and keep it around for a while. That’s the safe option.
To make it stick, start by teaching just one action. Make “scan the code with your phone when you borrow something” the one habit everyone follows. Once that’s running smoothly, you can introduce bookings and stocktakes. Explain every feature on day one and, more often than not, nothing sticks.
Even when you follow the steps, the sticking points tend to be the same. Know them in advance and you can head off most of them.
This is the most common one. “Tripod”, “Tripods”, and “Camera tripod” get registered as separate items. Storage locations split into “1F Storage”, “First-floor storeroom”, and “Storage (1F)”. When category totals don’t add up after a migration, this is usually why. And if you fix it after migrating, you also have to sort out the history and bookings that are already attached to those records.
The fix is simple: before exporting, count the unique values in each affected column. A pivot table or Remove Duplicates will show you in a few minutes. If there are more distinct values than you expected, the difference is exactly how much inconsistency you have.
To check for inconsistent naming, counting the unique values in each column is enough. If you only have five locations but twelve different values show up, you have seven candidates to fix.
This is when the same item is spread across several rows. In a sheet where rows were copied every time another unit was bought, it’s almost guaranteed. The tricky part is that it isn’t necessarily wrong. Having three cameras of the same model is correct; whether you show that as three rows or as one row with a quantity of 3 is just a design choice.
If the system you’re moving to handles items and individual units separately, consolidating into one row with a quantity will make things easier later. On the other hand, if each unit has its own serial number, purchase date, or condition, keeping separate rows means you won’t lose that information. Decide which way you’re going before you import. Changing your mind after the import is the pattern that creates the most rework.
The columns in your sheet will almost never map one-to-one to the fields in the new system. A “Notes” column holding warranty dates, rental suppliers, and the name of the person responsible is common. The longer a sheet has been in use, the more likely this is.
Try to move everything over cleanly and the migration itself grinds to a halt. The realistic approach is to reliably move the four essential fields first (name, model number, quantity, storage location) and tidy up the rest gradually afterwards. A plan to move every field perfectly usually never gets started.
There are plenty of equipment management tools, but if you narrow the question to moving off a spreadsheet, what you need to check comes down to five things.
The first is surprisingly easy to miss. If CSV import is reserved for higher-tier plans, you have to pay before you can try it, which means you can’t really evaluate the tool at all. Since it’s the entry point to the whole migration, check for plan restrictions first. While you’re at it, see whether it shows a preview before importing and whether it can skip only the rows with errors.
The third, phone support, directly affects adoption. If a dedicated app has to be installed, the people who only borrow equipment occasionally are the least likely to install it. Whether everything works with just a browser and a camera makes a real difference to how easily you’ll get cooperation on the ground.
The fifth, how pricing scales, matters too. Is it priced per user, per item, or per location? Equipment management tends to expand in scope once you start using it, so estimating costs based on your expected headcount and item count a year from now, not today’s, will save you regret later.
The most reliable way to see how pricing scales is to plug your own team size into an actual pricing table.See pricing plansHere’s how Werp™ measures up against each of those criteria. Werp™ is a SaaS tool for managing equipment, bookings, and members by workspace, and it was designed with migration from spreadsheets in mind.
CSV import is available on every plan. Upload a template CSV with name, model number, quantity, and storage location, and you’ll see a row-by-row preview before anything is imported. Rows with errors can be skipped so only the clean rows go in, which means one bad row never forces you to redo the whole import. Rows that match an existing item are added as new units of that item, and new rows are registered as new items. The duplicate-row problem described earlier is handled at import time.
The Free plan requires no credit card, never expires, and covers up to 3 people and 50 items. Import a single category by CSV and check that it works on your team’s phones on site. Because you can test it that way, you never have to sign up first and evaluate later.
Starting your equipment management in Excel or Google Sheets is the right call. It’s free, flexible, and anyone can use it. If you have few items, only a handful of people touch them, and hardly anything gets checked out, staying put is the most sensible choice. Workarounds like data validation, sharing settings, and a proper template can make it last even longer.
But five things can’t be fully fixed with workarounds: editing conflicts, search, double-booking checks, reminders, and updates from a phone. If three or more items on the checklist above apply to you, a dedicated system is worth trying at least once.
Even if you decide to switch, you don’t have to move everything at once. Clean up the list, export it as a CSV, and import part of it to check. You can try that much in a few hours. If you’re still unsure, moving just 50 items from your own data will get you an answer faster than continuing to compare tools on paper.
Set up in 5 minutes. Free forever — no credit card required.