Migrate to VIA ERP
Your data is in spreadsheets. You upload them, VIA ERP checks every row, and you see what will be written before anything is.
What you can import
Thirteen kinds of data, each with its own template and validation rules.
Customers and prospects
- Contacts
- Leads
Catalogue
- Products
- Variants
- Categories
- Suppliers
- Price lists
Stock
- Units of measure
- Warehouses
- Opening stock
- Stock adjustments
- Reorder rules
Accounting
- Exchange rates
How an import runs
-
You upload the file
One spreadsheet, one kind of data. An XLSX template is downloadable for each of the thirteen, generated by the server in your language, carrying the expected columns and their format.
-
You map your columns
Your headings are not ours. You match them once and the mapping stays with the session.
-
VIA ERP checks the whole file
Not a sample: every row is re-read and validated on the server. You get the count of valid rows, failed rows and duplicates before anything is written.
-
You write
The file is re-read and re-validated at write time, never taken from memory. A large file is queued with a progress counter, and you can cancel it while it runs.
-
You collect the rejects
Failed rows are listed with their row number and the reason. You fix the spreadsheet and re-upload those rows.
Three ways to write
The mode is chosen at write time, not at upload.
Create only
Anything that already exists is skipped. Nothing you already hold is overwritten.
Create or update
What exists is updated, the rest is created.
Update only
What exists is updated, what is missing is skipped. Nothing is created.
Duplicates are handled twice
First inside the file: two rows carrying the same key, and the first one wins while the rest follow the mode you chose — a spreadsheet that repeats a row cannot quietly create a twin. Then against your own data: the lookup is scoped to your organisation, and the match is exact, on the key that kind of record declares.
Contacts and leads add a likeness check: the same scoring the duplicate-scan screen runs, applied to the rows the exact match did not claim. It warns, it does not decide — no row is ever blocked or merged on a confidence score. It stops past 500 rows and tells you so on the first row rather than pass for complete.
Your imports stay on the record
Every import is listed with its kind, who ran it, when, and what it produced. You see your own; an administrator sees the whole organisation’s. The failed-row report stays attached to the import that rejected them.
Your country is set up before your first import
When your organisation is created, VIA ERP installs your jurisdiction’s reference data: taxes with their official legal code, tax groups, fiscal positions, currency, banks, payment terms and numbering series. For Tunisia that is six active taxes, five tax groups, three fiscal positions, eight banks and five payment terms already in place.
Seven jurisdictions are covered: Tunisia, France, Morocco, Algeria, Senegal, Côte d’Ivoire and Cameroon.
Worth knowing before you start
An import cannot be undone afterwards
Once rows are written, they are written. That is why the check covers the whole file before the write, and why a dry run is available.
Matching is exact
Reconciliation against your data runs on a declared key, not on a resemblance. The likeness check exists for contacts and leads, and it only warns.
Each kind of import has its roles
Importing contacts, products or stock is not the same person’s job. The user’s role decides which kinds they can upload.
One file, one kind of data
Products before variants, warehouses before opening stock. The order follows the dependencies.
Available on every plan
Import is not held back for a higher plan. It works from the moment your organisation is created, across all thirteen kinds of data, with the same checks.
See the migration on your own data
Bring an extract of your spreadsheets and we will go through the columns, the duplicates and the order to follow.
Book a demo