Prepare your CSV
What it's for
A clean CSV file imports first time. This article lists every column the importer understands, the format each one expects, and a checklist to run before the dry run.
Before you start
- Download the template from Upload CSV, or export your current inventory in import format and edit that.
- Create on the project every stage, unit type / zone, ownership company and section your file mentions.
File format
- CSV, saved as UTF-8, comma-separated, with the header row first. Excel: Save As → CSV UTF-8.
- Column order does not matter; header names must match the template. Unknown columns are ignored.
- Empty cells leave the existing value unchanged on units that already exist.
- Values containing commas or quotes must be quoted the normal CSV way; spreadsheets do this when saving.
- At most 5,000 data rows and 10 MB per file. Split larger files.
Identity columns
| Column | Rules |
unit_number | Required, up to 100 characters. Must equal the label drawn on the map. Avoid & if you will map the unit. |
unique_identifier | Only when the same unit number exists more than once (for example "Tower A"). Up to 100 characters. |
external_id | Your CRM or ERP reference, unique in the project when set. Used by the API. |
Catalogue columns (names must already exist)
| Column | Rules |
stage_name | Exactly as on the project, including capitals: Available, Hold, Sold or a custom stage. Empty on a new unit means Available. |
unit_type | Lower-case value such as plot, flat, villa, shop, office, booth, warehouse, farm_land, row_house. The full list is on How it works. It must be enabled for the project. Empty uses the project default. |
zone_names | Unit types / zones, separated by |: 3 BHK|Corner |
plc_names | Preferential location charges, separated by |: Corner|Park Facing |
ownership_company_names | Separated by |: Acme JV|Partner Co |
section_path | Multi-map only. Full path from the top: Block A > Floor 1 |
Physical columns
faces_north, faces_east, faces_south, faces_west — 1/0, true/false or yes/no.
dimension_north … dimension_west — numbers in the project's area unit length, not negative.
area — the main area, a number. area_1 — secondary area as text. size — a size label such as 30x40 ft.
boundary_north … boundary_west — what lies on each side ("30 ft road", "Plot 14").
survey_numbers — for display only; separate several with | or ;.
Price and note columns
public_total_price — shown to buyers when prices are on. Numbers only, no currency symbol or thousands separators.
internal_total_price, min_price, max_price — staff only.
public_notes, internal_notes — text.
external_link (a full URL, up to 500 characters) and external_link_title.
Internal sales columns
internal_customer_name, internal_booking_amount, internal_payment_notes. Never shown on public pages. They are ignored for users without permission to view customer details, just as internal_total_price is for users without permission to view internal prices.
Checklist before the dry run
- Every stage, zone, ownership company and section in the file exists on the project, spelled the same.
- No two rows share the same
unit_number and unique_identifier.
- Numbers have no currency symbols, units or commas.
- Unit numbers match the labels on your maps; no
&.
- Multi-map: section paths were copied from the Multi map structure tab.
- The file is saved as CSV UTF-8.
Tips and common questions
- Leading zeros: spreadsheets turn
007 into 7. Format the column as text before typing.
- Copy section paths with Copy section path for CSV import rather than typing them.
- To update only prices, keep just
unit_number (and unique_identifier if used) plus the price columns — other values stay as they are.
Related: CSV import guide · Dry run and commit · Section paths · Unit types, zones & rates