How to Migrate Inventory from Excel

Bulk item spreadsheets break without mapping and upsert discipline

New tenants paste years of SKU masters into Excel but double-create items on second import because they used Insert mode instead of upsert keyed on OEM or item code.

Column headers like PartNo and UOM do not match Biznsbook fields until mapping is saved, producing hundreds of validation errors on execute.

Failed rows are invisible when teams do not export the error CSV and fix source data before re-running.

Items imported without product groups or tax groups force a second cleanup project before sales and purchasing can go live with correct reporting and tax calculation.

Why this happens

• Sample CSV template was not downloaded for exact column names.
• Key field for upsert does not match existing Biznsbook identifiers.
• Required fields are blank in source rows.
• Large files are uploaded without a small pilot import first.

Biznsbook addresses this through Items import target, column mapping, upsert mode when Inventory, Warehouse, and Clothing modules are licensed — stock, layout, and classification share one product master.

Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.

Step-by-step: Migrate Inventory from Excel

Built for warehouse managers, buyers, and apparel operators running bins, replenishment, fabric rolls, and migration from spreadsheets in Biznsbook.

1. License Data Import. Confirm ERPModule.DataImport is active so Import appears in the menu.
2. Prepare Excel export. Clean spreadsheet columns for item code, name, UOM, groups, and barcodes; download sample Items CSV for header alignment.
3. Start New Import. Choose target Items, set mode to Upsert, and upload .csv, .xlsx, or .xls under the 10 MB limit.
4. Map columns. On Mapping, use auto-map for scores ≥80%, assign required and key fields, and skip unused source columns.
5. Preview validation. Review parsed rows, fix file errors or remapping, and re-validate until preview is clean enough to execute.
6. Execute import job. Run import and poll status until Processing becomes Completed or Failed; read inserted, updated, and failure counts.
7. Export errors CSV. Download import_{id}_errors.csv with row, field, and message for failures; correct file and re-import failed keys.
8. Import product groups first. When restructuring categories, import ProductGroups as a separate Data Import target before Items so group references map cleanly on the item file.
9. Plan opening balances separately. Item master import establishes products; warehouse opening quantities may require opening balance capture or GRN strategy per your go-live playbook — do not assume Items import sets on-hand stock.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Sample CSV template was not downloaded for exact column names. Repeating this each month usually shows up first in capacity dashboards or ABC classification exports.
• Mistake 2: Key field for upsert does not match existing Biznsbook identifiers. Repeating this each month usually shows up first in capacity dashboards or ABC classification exports.
• Mistake 3: Required fields are blank in source rows. Repeating this each month usually shows up first in capacity dashboards or ABC classification exports.
• Mistake 4: Large files are uploaded without a small pilot import first. Repeating this each month usually shows up first in capacity dashboards or ABC classification exports.

Track recurring exceptions in month-end notes; each should map to a control above.

Best practices that hold up as you scale

• License Data Import — Confirm ERPModule.
• Prepare Excel export — Clean spreadsheet columns for item code, name, UOM, groups, and barcodes; download sample Items CSV for header alignment.
• Start New Import — Choose target Items, set mode to Upsert, and upload .
• Map columns — On Mapping, use auto-map for scores ≥80%, assign required and key fields, and skip unused source columns.
• Preview validation — Review parsed rows, fix file errors or remapping, and re-validate until preview is clean enough to execute.

Teams that map bins before high season and refresh ABC/XYZ monthly keep replenishment aligned with real velocity.

How Biznsbook supports this workflow

Items import target is documented in Biznsbook Inventory & Warehouse capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

column mapping is documented in Biznsbook Inventory & Warehouse capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

upsert mode is documented in Biznsbook Inventory & Warehouse capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.

Warehouse map, storage location, and clothing permissions gate layout edits separately from receiving clerks.

Suggested implementation timeline

1. Week 1: Document current process gaps and configure Items import target with finance owner sign-off.
2. Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
3. Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
4. Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
5. Ongoing: Monthly review using inventory migration cutover and leadership dashboard.

Related guides and help articles

Help Center: creating a GRN, stock transfers, import items.

Modules: Warehouse, Clothing, inventory guides hub.

Cutover sequencing with finance

Coordinate item import with chart of accounts and party imports if your spreadsheet migration includes customers and suppliers on the same weekend — tax groups on items require taxation configuration to already exist.

After Items upsert succeeds, run a valuation or stock card spot check on ten high-value SKUs before enabling replenishment automation that would create purchase requisitions from bad master data.

Cleaning source spreadsheets

Normalize UOM abbreviations and remove duplicate OEM rows in Excel before export — validation preview is faster when source data uses consistent casing and no merged cells.

Keep a frozen copy of the migration file with date stamp; if buyers edit the live spreadsheet after import, upsert on the next file should use the same key column to update rather than insert duplicates.

Post-import validation sample

After full import, sample ten SKUs across categories: confirm UOM, tax group, barcode, and product group in Biznsbook match the signed-off spreadsheet row.

Enable replenishment only after sample passes — bad min/max on imported rows creates automatic requisitions for wrong quantities.

Cutover weekend sequencing

Freeze physical movements during final import window — receiving and adjustments during import create drift between warehouse floor and newly loaded on-hand. Communicate freeze windows to stores and warehouses in writing.

Run import in waves: masters first, on-hand second, open POs third if supported. Validating masters before quantities prevents orphan stock rows that reference non-existent UOM or product groups.

Ownership after go-live

Name a single data steward for SKU masters post-migration — casual Excel edits by category managers after go-live recreate the multi-version spreadsheet problem inside Biznsbook exports.

Schedule a day-thirty master data review: duplicate barcodes, inactive flags left wrong, and default warehouses mis-set are the top defects found once real transactions stress the imported catalog.

Metrics to track monthly

• Bins above 90% capacity on capacity dashboard
• ABC A-class SKUs with reorder levels configured
• Fabric rolls below low-stock threshold
• Import jobs completed without row errors
• Storage locations linked on GRN lines

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheet / manual books vs integrated ERP

Compare typical manual finance work with Biznsbook Items import target and related capabilities.

Inventory migration cutover

Run a pilot upsert, reconcile item counts in Biznsbook against Excel, then execute full file on a quiet day and keep the error CSV until failure count is zero. Keep the error CSV from the final successful job in migration archives — auditors and IT support will ask which rows failed on cutover weekend.

Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.

Frequently asked questions

How this differs by industry