Bringing data in from another programme

The Data import wizard loads an Excel or CSV file and creates the ERP records from it. If your data comes from Powergest, there is a shorter route that needs no preparation. This page tells you which one is yours.
Am I coming from Powergest or from a standalone file?
If you are moving a customer over from Powergest, use its own screen: it takes a ZIP with the Desktop ERP tables and imports them all in one go, in the right order and without preparing templates. It is the recommended route, and it is in migrate from Powergest.
If the two programmes run side by side and what you want is to take documents from here to the Desktop ERP, the route is the other way round: move documents to the Desktop ERP.
For everything else —a customer list your accountant sends you, a supplier’s catalogue, the records another system exports— the route is the import wizard, which is explained in the next section.
Can I ask to be shown how on screen?
Yes, and it is the quickest way to understand it. Press F1 on the Data import screen and choose Bring in data from an Excel or CSV file: the guide opens the tabs in order and points out what to look at on each one. It doesn’t click anything that writes to your data.
The same guide appears in the F1 of Customers, Suppliers and Items, which is where you usually remember that you already have those records in a spreadsheet. When you choose it, it takes you to the import screen by itself.
How do I import an Excel file?
The example is customers, but the steps are identical for items, suppliers, sales agents or any other target: import customers from an Excel file. That page says what the file must contain —one row per record and a first row of headers— and which formats are accepted.
A target is the type of record or document that is going to be created, and not all of them accept the same things. Before preparing the file, it is worth looking at the list of targets there are, which fields each one accepts and what is left out: what can and can’t be imported.
And what if I am going to repeat the import every month?
Then it is worth saving the work. A mapping template stores the correspondence between the columns of your file and the ERP fields: you prepare it once and reuse it every time a file with the same format arrives. It doesn’t store the file or the data, only the correspondence: prepare an import template.
With the template ready, the import can run by itself every so often without anyone logging in to the programme, reading a file or a folder: schedule a recurring import. That page also covers what you need first, which is precisely the template and a path the server can reach.
How do I know if everything has gone in?
Every import is recorded with its count and the details of the rows that didn’t go in, both the ones you ran by hand and the ones a scheduled task ran. How to read that report, what each status means and how to repeat the import fixing only what failed is in review an import.
What happens if I import the same file twice?
Not everything is duplicated blindly. Each target has an external key —for master data, the code— which is the piece of data the programme uses to recognise whether the record already exists. That is why it matters so much that the codes are right in the file: they are what makes the difference between creating a record and updating the one that was already there.
The pages on what can be imported and reviewing an import explain how each target behaves with a repeated code, including the exceptions.