Importing & Exporting Records

Almost every implementation starts the same way: the customer has years of data sitting in spreadsheets, and it needs to end up in the system. And almost every month afterwards, somebody needs the opposite — a few hundred records pulled back out into Excel so they can be checked, corrected in bulk, and pushed back in.

Nama handles both directions with the same file. When you export records you don't get a pretty report; you get a workbook that the system knows how to read again. Export a hundred sales invoices, fix the salesman on forty of them, upload the same file, and those forty are updated. That round trip is the heart of this whole area, and it is the reason the exported sheet looks the way it does — with its odd // rows and :-record: markers.

Start with exporting, because an exported file is also the best template you will ever have for an import.

Everyday Use

📤Exporting RecordsThe four export commands, every option in the export dialog, and where the finished file lands.📥Importing RecordsUpload a workbook to add or update records, how references are matched, and how to read the errors that come back.🧩Anatomy of the Export FileWhat every marker row, suffix and detail sheet in the workbook means — the reference you need before hand-writing an import file.

Saved Definitions & Custom Sheets

🗂️Files Export / Import MenuSave an export or import as a reusable definition, and design your own Excel sheet with custom columns, formulas and totals.🛠️Advanced Record ImportMap a supplier's or a legacy system's spreadsheet — one you cannot reshape — onto Nama records, column by column.

Looking for something else?

Pulling data in automatically on a schedule, or straight from a SQL query, is the job of an entity flow rather than the manual import described here. And if you are trying to save a report as a spreadsheet, that is a different mechanism entirely — see Reports in the global configuration.