Import and export
Every register can be downloaded as Excel, CSV or a print view, with the filters and columns you choose; registers with outlines also download as GeoJSON or KML. Most records can be added or updated in bulk from a spreadsheet, and boundaries from a map file.
Export
Needs data.export and the register’s view permission
- Open the register. Set the filters and sort you want, and tick rows if you only want some.
- Click Export (beside the count). The export dialog opens with the list’s filters already filled in.
- Rows: everything matching the filters, only the ticked rows, or only the rows on this page.
- Filters: change them here without leaving the dialog. The count beside the heading follows every change, so you see how many rows you will get before downloading.
- Columns: untick what you don’t need (All / None to start over). Your choice is remembered for that register.
- Format: Excel (.xlsx), CSV, GeoJSON or KML (registers with outlines: properties and projects), or Print view (A4).
- Click Download N rows, or Open print view.
- Saved settings: type a name under the columns and click Save settings. Next time, pick it from Saved settings to get the same filters, columns and format back. Saved settings belong to you and to this browser.
- At most 50,000 rows per file and 2,000 rows per print view. The Download button stays off until the count is under the limit.
- Ticked rows are exported as ticked, even if they no longer match the filters.
- An Excel export has a second sheet, About this export: the register, the number of rows, the filters, who exported it and when.
- Account numbers, BVNs, NINs and ID numbers are masked. Roles with
claimants.revealcan tick Include full numbers; each exported claimant’s minute sheet records it. - Every export is recorded on the exporting person’s own minute sheet, with its filters.
What can be exported
| Where | Export |
|---|---|
| Registers | Projects, properties, claimants, surveys, compensation cases, conflicts, spatial flags, background jobs, staff, messages and message deliveries: Export beside the count. Fill the gaps exports the incomplete records it lists. |
| Properties page header | Export items: every item on the properties matching the filters (ref no, project, dictionary, code, item, quantity, unit, rate, value). The same layout imports back. |
| Compensation cases page header | Case lines: what each listed case pays for, line by line. Payment schedule: the cash cases approved or with a cheque issued, with the claimants’ bank details. |
| Any record’s Minutes tab | Export: its minute sheet (when, action, from → to, note, by). |
| Any record’s Evidence tab | List: the documents attached (kind, description, file name, size, who uploaded it and when). |
| Map page header | Export projects: every project, with its boundary in GeoJSON or KML. |
| A project’s Map tab | GeoJSON / KML: the project boundary with all its properties. |
| Dictionaries page header | Export rates: the current rate of every priced item in every dictionary, in one sheet. Each dictionary also exports its own items. |
| Administration › Tags | Export: the tag list (name, group, colour, applies to, rules, records using it). |
| Locations | Export: every LGA, ward and area. |
Source columns say how a record was captured: Office, Field, Import or Map scan draft. Missing lists what the record still lacks, in the words of its completeness checklist.
Import
Needs data.import and the permission to change those records
- Click the import button in the page header (see the table below).
- Download the template (Excel or CSV) and fill it in, one record per row. The Excel template has dropdowns for fixed lists. An export of the same register can be edited and imported back instead.
- If the import has a choice of how rows are applied (property items: add and update or replace), choose it.
- Choose the file and click Check file. Nothing is saved yet.
- If the file’s headings don’t say which column is which, the dialog asks: for each column of your file, choose what it holds (or “not imported”), then click Check file again. A file with unused columns offers Choose the columns too.
- Read the result: how many rows would be New, Update, Remove or No change, and every problem by row and column.
- If there are problems, fix them in the file and click Choose another file. Otherwise click Import.
- All or nothing: if any row has a problem, nothing is imported.
- Safe to repeat: importing the same file again changes nothing; rows that match what is recorded show as No change.
- Up to 5,000 rows and 5 MB per file,
.xlsxor.csv. - Column headings are matched ignoring case and punctuation, and common other names are understood (for example Qty for Quantity).
- When a row updates an existing record, blank cells keep the stored value.
- Masked numbers (
••••6789) in an exported file are ignored. - Imported records are marked with the source Import and their data completeness is worked out straight away. Fill in what is missing on Fill the gaps.
What can be imported, and how rows match
| Import (where) | Matched by | Required columns | Other columns |
|---|---|---|---|
| Projects (Projects › Import) | Project code | Project code, Name | LGA (name), Status, Start date (YYYY-MM-DD), Description, Tags |
| Properties (Properties › Import) | Ref no | Ref no, Project code, Property type, LGA | Ward, Area, Address, Land area (m²), Latitude, Longitude, Claimant ID (e.g. CL-0012), Notes, Boundary, Tags |
| Property items (Properties › Import items) | Property + dictionary code (or custom item name) | Property ref no, Quantity | Dictionary code, or Custom item with Custom details and Custom value per unit (NGN); Notes |
| Claimants (Claimants › Import) | Claimant ID (CL-0012); blank = new claimant | Full name | Gender, Phone, NIN, Email, Address, ID type, ID number, Bank, Account name, Account number, BVN, Notes, Property ref no (links the claimant), Tags |
| Payments (Compensation cases › Import payments) | Case number | Case number | Cheque number, Cheque bank, Cheque date, Amount (NGN) (checked, not saved), Collected on, Note |
| Survey assignments (Field surveys › Import assignments) | Property ref no | Property ref no, Surveyor | — |
| Staff invitations (Staff › Import invitations) | Name, Email, Staff ID, Role | Phone | |
| Tags (Administration › Tags › Import) | Group + name | Name | Group, Colour, Applies to, Field app, One per record, Description, Active |
| Rates (Dictionaries › Import rates) | Dictionary + code | Dictionary, Code, Rate (NGN) | Note |
| Dictionary items (inside a dictionary) | Code | Code, Label | Parent code, Unit, Rate (NGN), Active, Order |
| Locations (Locations › Import) | LGA + ward (+ area) names | LGA, Ward | Area |
- Properties name their project by code and their LGA, ward and area by name. Wards and areas must already exist, so import them on Locations first.
- Property types: Land (undeveloped), Building, Land & Building, Farmland — or as edited under Dictionaries.
- A project can only be imported as Active once its boundary is set. Import it as Planning, set the boundary, then make it active.
- LGA names must be one of the 23 Kaduna LGAs:
The Tags column
Property, claimant and project exports end with a Tags column ("Priority: High; Revisit"). The same column can be imported: the tags named there are added to the record (tags already on it stay). Each name must be an existing, active tag that fits the record; an unknown name is reported on its row and nothing is imported.
The Boundary column (properties)
Optional. Give the outline in one cell, either as corners — lat lng; lat lng; …, for example 10.5231 7.4402; 10.5231 7.4410; 10.5238 7.4410; 10.5238 7.4402 — or as WKT: POLYGON((lng lat, lng lat, …)). Note that WKT puts longitude first. For many outlines, a boundary file is easier (below).
Claimants: NIN and duplicates
- NIN must be 11 digits, and one NIN belongs to one claimant. A NIN already registered to someone else is refused; put that claimant’s ID on the row to update them instead. Format the column as Text in Excel.
- A new claimant who looks like someone already registered (same phone and a similar name, same BVN or same bank account) is imported, and a Possible duplicate claimant conflict is raised for the office to decide on Records › Conflicts.
Property items
- A row names the property by Property ref no and the item by its Dictionary code (for example
mango.mature) — or, for anything not in a dictionary, leaves the code blank and gives a Custom item (with Custom details and Custom value per unit if known). - Add and update (the default): an item already on the property with the same code (or the same custom item) is updated — its quantity and notes — instead of being added twice. Anything else is added.
- Replace: as above, and every item on a property named in the file that the file does not list is removed. The check shows them as Remove before anything happens. Items in a compensation case (or in a cancelled one) are never removed.
- An item in a compensation case cannot change through an import: the row is reported as a problem.
- Quantity must be more than zero. New dictionary items are priced at the current rate. The code must be a specific, active item with nothing under it.
- Each line added, changed or removed is minuted on its property.
Payments from a bank file
Needs data.import and comp.cheque or comp.complete
- Download the Payment schedule (Compensation cases page header) and send it to the bank.
- When it comes back, fill in Cheque number, Cheque bank and Cheque date for each case paid (the schedule’s other columns can stay), and later Collected on when the claimant collects.
- On Compensation cases, click Import payments and choose the file.
- An approved case with a cheque number moves to Cheque issued. A case with a cheque and a Collected on date moves on to Paid. Each move is checked like the step on screen (your permission, the required fields) and minuted with its figures.
- When Amount (NGN) is filled in, it must equal the case’s approved amount; otherwise the row is a problem and nothing is imported.
- A case that already has a different cheque number is refused (correct it on the case). Cases already at the step in the file show as No change.
- Only cash cases are paid this way.
Survey assignments
Needs data.import and surveys.assign
One row per property: Property ref no and the Surveyor (their email, staff ID or full name — an active field surveyor). A property that already has an open or approved survey is left as it is (No change).
Staff invitations
Needs data.import and users.manage
- One row per person: Name, Email, Staff ID, Role (the role’s name) and optionally Phone. A row whose email already has an account is left alone.
- You can only give roles whose permissions you hold yourself; only an administrator can give the administrator role.
- Each person is emailed an invitation link. When email is not set up, the import says how many were not emailed: open each person’s staff file and issue the link there.
Tags
Needs data.import and tags.manage
A tag is matched by its group and name: a match is updated, anything else is created. Colour is one of the tag colours (Navy, Blue, Teal, Green, Olive, Amber, Orange, Red, Rose, Purple, Slate, Brown). Applies to is blank (any record) or a list such as Properties, Claimants. Field app, One per record and Active are Yes or No.
Rates across dictionaries
Needs data.import and dictionaries.manage
- On Dictionaries, click Export rates: every priced item of every dictionary, with its current rate.
- Change the Rate (NGN) of the items whose rate changed (add a Note saying why, if you like).
- Click Import rates and choose the file.
- A changed rate starts a new rate from now; the old one stays in the item’s rate history. Unchanged rows show as No change.
- Items with kinds under them have no rate of their own: give each kind its rate.
- Rates are a guide for valuers only: a case opened from now on shows the new rate beside its lines. Items on properties carry no rate.
Dictionary items
Needs dictionaries.manage
- Open the dictionary under Administration › Dictionaries and use Export or Import on its Items tab.
- Existing codes are updated and new codes are added. Parent code places an item under another; leave it blank for a top-level item. Parents may come anywhere in the file.
- Unit is one of
each,sqm,m,ha. A Rate different from the current one starts a new rate from today, and the old rate stays in the rate history. - Active is Yes or No: No retires the item.
Import boundaries
Needs data.import and properties.manage (properties) or projects.manage (projects)
To give many properties — or many projects — their outline at once, from a GIS or survey file:
- On Properties (or Projects), click Import boundaries.
- Choose a GeoJSON, KML or zipped shapefile (.shp, .shx, .dbf and .prj together). Each outline must carry the property’s reference number in an attribute called
refNo,reforref_no(orname) — for projects, the project code incodeorproject_code(orname); in KML, the placemark’s name. - Click Check file. Nothing is saved yet. The result shows how many outlines matched, how many will replace an existing boundary, and any problems (no match, an invalid outline).
- Click Import N boundaries to save the matched outlines, or Choose another file.
- Outlines with problems are skipped; the rest can still be imported.
- An imported outline replaces the existing boundary.
- Property boundaries: spatial checks are queued for each one; problems appear on Records › Spatial flags. A property in a live compensation case keeps its boundary unless your role can correct cases.
- Project boundaries: each project’s map scan starts, as when the boundary is drawn on the project page.
Keeping leading zeros
Excel drops leading zeros from numbers: 0123456789 becomes 123456789 and fails the 10-digit check. Use the Excel template and keep those columns formatted as Text. Opening a CSV in Excel and saving it again loses the zeros.
Common import problems
See Troubleshooting › Import and export for every message and its fix.