Overview
Almost every implementation starts the same way: years of the customer’s data are sitting in spreadsheets and need to end up in the system. And almost every month afterwards, somebody needs the opposite — a few hundred records pulled back out into Excel to be checked, corrected in bulk, and pushed back in.
Nama ERP handles both directions with the same file. An export is not a pretty report; it is a workbook the system knows how to read again. Export a hundred sales invoices, fix the salesperson on forty of them, upload the same file, and those forty are updated.
That round trip is the point. It is also the fastest way to build an import: the best template you will ever have for loading data is an export of the same type.
Features
One workbook, both directions
Records export to a structured Excel workbook — including detail lines on their own sheets — and the same structure is what the importer expects back. Because references are matched on the way in, a corrected sheet updates the records it came from rather than creating duplicates, and errors come back identified rather than as a failed upload.
Saved definitions
An export or an import can be saved as a reusable definition, so a monthly routine is a click rather than a set of options someone has to remember correctly. You can also design your own sheet — choosing the columns, adding formulas and totals — when the standard layout is not the one your team works with.
Spreadsheets you cannot reshape
Sometimes the file comes from a supplier or a legacy system in a shape you do not control. Advanced record import maps that sheet onto Nama ERP records column by column, so the data can be loaded without anyone rekeying it or rebuilding the file by hand.
When it should not be manual at all
Scheduled loading, or pulling data straight from a SQL query, is the job of an Entity Flow rather than a person with a workbook — and a flow can import on a schedule, validate what arrives, and generate whatever documents should follow. Manual import is for the cases where a human genuinely should be in the loop.
Why it matters at implementation
Data migration is where ERP projects lose months. A system whose export format is also its import format turns migration into an iterative process — load, review in Excel, correct, reload — instead of a one-shot conversion that has to be right the first time.
Read the import and export documentation.
