Can I import my customers from Excel?

Yes. Upload a CSV or Excel file, map your headers to BizOS fields, review the validation summary, and import. Duplicates are matched on phone number and you choose whether to skip or update them.

Can I bring in what customers already owe me?

Yes. Import opening dues in BizOS. Those balances are chased like any other invoice but flagged so they are excluded from revenue totals, since the money was earned before BizOS.

What happens to rows with mistakes?

They don't block the import. The good rows are written and the problem rows come back as a downloadable error file listing the row, the field and the reason, so you fix that file and re-upload just it.

How big a file can I import?

Up to 20,000 rows per file. For a larger catalogue, split it — each run reports its own counts.

Will importing create duplicate customers?

No. Customers are matched on phone number and items on SKU or barcode, and you decide up front whether matches are skipped or updated. The count of duplicates handled is reported at the end.

Data import

Nobody starts from zero. The import wizard brings your existing customers, item list, open enquiries and — crucially — the money people already owe you, so BizOS is useful on day one rather than after a month of typing.

What you can import

Type	Brings in	Why it matters
Customers	Name, phone, company, email, address, city, GSTIN, tags and notes	The spine everything else attaches to
Items	Name, SKU, barcode, category, brand, model, unit, HSN/SAC, GST %, sale and purchase price, opening stock and cost, low-stock level, goods or service, measurement profile	Scan-to-bill works from day one
Leads	Open enquiries with source, priority, estimated value, tags and notes, landing on a pipeline and stage you choose	Your existing pipeline doesn’t reset
Opening dues	Outstanding bills from before BizOS: customer, bill number and date, due date, total and amount already paid	Payment chasing starts immediately

Import opening dues — this is the one people skip

Without it, BizOS only knows about money owed on invoices you raised in BizOS, and the receivables report understates reality for months. Opening dues are flagged so they’re chased like any other invoice but excluded from revenue totals — the money was earned before BizOS, and counting it again would overstate your year.

The four steps

1
Choose and upload
Pick what you are importing and upload a CSV or Excel file. BizOS reads the header row and the first few rows so the next step has something to show you.
2
Map the columns
Match your spreadsheet’s headers to BizOS fields — "Mobile" to phone, "Party Name" to name. Required fields are marked, and the preview shows real values from your file so you can see you mapped the right column.
3
Review
BizOS validates every row and reports how many are ready, how many are duplicates and how many have errors, with the first errors listed inline. Choose whether duplicates should be skipped or updated.
4
Import
Good rows are written. When it finishes you get counts and a link into the list you just populated, plus an error file if any rows need fixing.

Duplicates

Customers are matched on phone number, items on SKU or barcode. When a match is found you choose:

Skip them — keep what’s already in BizOS and ignore the incoming row. Safest for a top-up import.
Update them — let the file overwrite. Right when your spreadsheet is more current than BizOS.

Either way the count is reported, so you always know how many rows were affected.

Errors

A row with a bad phone number, a missing required field or an invalid value doesn’t stop the import — the good rows go in and the bad ones are collected. You get the first errors inline (row number, field, and what’s wrong) and the full set as a downloadable error file. Fix that file and re-upload only it.

Import is not a validation bypass

Imported rows run through exactly the same rules as rows typed into the app: phone numbers are stored in one international format (+91… for an Indian mobile), and required fields are enforced. An import can’t create data the app itself would refuse.

Tips for a clean first import

Start with customers, then items, then dues — dues reference customers, so the order matters.
One header row, no merged cells, no totals row at the bottom.
Phone numbers can be 9876543210, +919876543210 or 98765 43210 — BizOS normalises them. What it can’t fix is a missing digit.
Opening stock on items creates opening-balance stock movements, so your stock ledger starts from a real position.
Import leads onto the right stage, not just the first one — a lead that’s already been quoted shouldn’t land in New.

Where it lives

Settings → Connections & AI → Import from Excel (Owner and Admins). The Customers, Items & stock and Leads pages link straight to it, and Invoices has Import opening dues. Imports are recorded in the Activity log, and each run keeps its counts and error file so you can look back at what happened. If your business uses Branches, imported records land at the head office.

Common questions

Can I import my customers from Excel?: Yes. Upload a CSV or Excel file, map your headers to BizOS fields, review the validation summary, and import. Duplicates are matched on phone number and you choose whether to skip or update them.
Can I bring in what customers already owe me?: Yes. Import opening dues in BizOS. Those balances are chased like any other invoice but flagged so they are excluded from revenue totals, since the money was earned before BizOS.
What happens to rows with mistakes?: They don't block the import. The good rows are written and the problem rows come back as a downloadable error file listing the row, the field and the reason, so you fix that file and re-upload just it.
How big a file can I import?: Up to 20,000 rows per file. For a larger catalogue, split it — each run reports its own counts.
Will importing create duplicate customers?: No. Customers are matched on phone number and items on SKU or barcode, and you decide up front whether matches are skipped or updated. The count of duplicates handled is reported at the end.