← All posts

Moving from Excel to Warehouse Management Software: Turn Your Existing Spreadsheet into a Working NocoBase System

by BAMFLOW • • 5 min read • Updated 9 Nov 2026

Moving from Excel to warehouse management software with NocoBase: fix five spreadsheet defects, import once, clean duplicates and negative stock, and run goods-in / goods-out / stock pages the same day — free template included.

cover-final

Moving from Excel to Warehouse Management Software: Turn Your Spreadsheet into a Working NocoBase System

Quick summary: Moving from Excel to warehouse management software does not mean retyping thousands of SKUs. Clean up your spreadsheet, import it into NocoBase — the open-source, self-hosted no-code platform — and get goods-in, goods-out and stock pages working the same day.

Every warehouse knows this scene. The stock spreadsheet has 4,000 rows and has survived three warehouse keepers. Stock is added and subtracted by hand; at month-end the physical count is off by dozens of units, and nobody can say when it went wrong, because a spreadsheet never remembers who edited which cell. Excel is a superb calculation tool, but it was not built for several people posting stock movements in real time, for documents with approvals, or for warning you before an item runs out. Past a few thousand SKUs, the spreadsheet becomes the bottleneck.

Five spreadsheet defects that break imports

Ninety percent of failed first imports are caused by the source file, not the software. Fix these five classics first.

Two facts in one cell. "Copper wire 2.5mm – 100m roll" mixes name and specification. Split them into separate columns, or you can never set reorder levels per variant.

Inconsistent item codes. "CW-25", "CW 25" and "cw25" are three different items to a computer. Codes become your primary key: unique, uniformly formatted, no exceptions.

Stock stored as text. "Out", "low", "~50" cannot land in a numeric field. Replace with a real counted quantity — which is why migration day should follow a physical stock count.

Merged cells and mid-table headers. Rows like "WAREHOUSE A – OCTOBER" inside the data break the one-row-one-record rule. Flatten everything: first row is column names, every row after is a record.

Mixed units of measure. Receipts in cartons, issues in pieces. Pick one base unit per item (piece, kg, metre) and note conversions in a remarks column.

Save the cleaned copy under a new name and never edit the live original.

Import, then clean what the import reveals

In NocoBase, create an Items collection — code, name, specification, base unit, opening stock, reference cost, category — and import the prepared file. The verification pass usually surfaces three issues.

Item catalogue right after importing the Excel warehouse file into NocoBase
Item catalogue right after importing the Excel warehouse file into NocoBase

Duplicate codes: two rows, one code, slightly different names. Merge the balance into the canonical code and keep the old code in a notes field so old paperwork stays traceable. Negative stock: usually goods issued on paper before the receipt was recorded — post a signed stock adjustment to counted reality, and from go-live the system itself blocks issues that would drive stock negative. Unit chaos: one base unit per item, enforced in the catalogue.

Do not import years of movement history. Opening balances, the item catalogue and the supplier list are enough; keep old history in the archived spreadsheet.

The first three pages: catalogue, goods-in, goods-out

Item catalogue — a searchable list with current stock at a glance, answering sales' eternal question: "How many of item X do we have?" Goods-in document — every delivery becomes a numbered document with supplier, lines and prices; on confirmation, stock increases automatically, with creator and timestamp recorded. Goods-out document — issues go through a document too; the system checks available stock before deducting, so sales promises delivery dates against real numbers and accounting reconciles cleanly.

All three pages are views over one data model. Define the data once, and each role gets its interface — the director can add an inventory-value chart without rebuilding anything.

Stock levels and inventory value dashboard in NocoBase after moving off Excel
Stock levels and inventory value dashboard in NocoBase after moving off Excel

Let AI draft your data model

Ask an AI assistant to propose the structure first: "Here is the Excel warehouse file of a [your trade] business, with these columns: [list them]. Propose a data model for warehouse management software: an Items table, Goods-in and Goods-out tables, and their relationships. Mark the primary key, required fields and fixed choice lists, and flag suspicious rows: duplicate codes, negative stock, inconsistent units." Treat the output as a draft — only you know which items need batch or expiry tracking — and never send real cost prices or customer data to public AI tools.

What 30 minutes gets you — and what comes next

In one focused session you can have a clean catalogue, correct opening balances, three working pages and basic permissions — roughly 70% of a small warehouse system's value. The rest is a deliberate next step: QR code scanning for goods-in and goods-out (see QR code warehouse management in NocoBase), automatic low-stock alerts at the minimum level (định mức tồn tối thiểu), and multi-warehouse operation with FIFO valuation. Clean data first, a few stable weeks, then the extras. New to the platform? Start with What is NocoBase.

Free template: BAMFLOW gives readers the import-ready warehouse template (Items – Goods-in – Goods-out – Stock) plus the AI prompt set from this article.


About BAMFLOW — BAMFLOW is the official NocoBase partner in Vietnam, implementing and teaching AppSheet, NocoBase and AI for businesses (300+ applications built, 150+ business clients, 1,000+ students trained).

Đọc bản tiếng Việt RSS