SimpliServDocs

Run data imports safely

Import contacts, products, categories, vehicles and fault codes and fix errors cleanly

→ Open imports in SimpliServ

The import area bundles five import types: contacts, products, product categories, vehicles and vehicle fault codes. Each tile opens its own import area below. The fields and column names per target are explained in Import & export data. Prepare data per target; a product file is not also a contact file.

Before every import

1. Define target and key

First decide whether you create new records, update existing ones or need both. Define a stable matching key: for contacts id or email, for products EAN or article number, for vehicles ID, VIN, serial number or licence plate.

2. Backup and test set

Export existing data if you change large data sets. Start with a small file containing real examples. Only when preview and result are right do you import the full data set.

3. Prepare references

Products may need categories, warehouse and supplier data. Vehicle fault codes can reference spare parts. So first check that dependent master data already exists.

Import types

TargetSuitable forCheck beforehand
Contactscustomers and contact personsunique email or id
Productscatalogue, prices, stock, suppliersEAN/article number, tax and category details
Categoriesnested product pathsparent paths and spelling
Vehiclesbikes, vehicles and fleetbrand, model, identification number
Fault codesmanufacturer codes and spare partscode format and part reference

Procedure

Choose the import type

Open Administration → Data & devices → Imports and choose the matching tile. Download a template with the correct column names via Download CSV or Download JSON.

Check file and mapping

Upload the prepared file and choose the matching CSV separator for CSV. Columns are matched by their names; check whether numbers, dates and decimal separators are recognised correctly.

Read the preview

In the Table preview faulty rows come first. Look specifically for empty required fields, truncated text, wrong categories and duplicate keys. A green import status doesn't replace a content check.

Run the import

Do a dry run first, which saves nothing and shows what would be created, updated or skipped. Then start the import with Start Import. Keep the tab open until the feedback appears and don't repeat the run blindly.

Check a sample

Open several newly imported records directly in contacts, products, vehicles or fault codes. Also check a record with optional fields.

Fix errors systematically

  • Required field missing: add the column or set the value before importing.
  • Duplicates: unify keys; don't just compare names.
  • Category not found: write the category path exactly as in the system.
  • Number wrong: unify decimal and thousands separators.
  • Reference unknown: import the parent object first or use the existing ID.

After a correction only re-import the affected rows. That keeps it traceable which run caused which changes.

A repeated import can create new records depending on target and key. Check the import logic and the preview before repeating the same data set.

Permission

The page is protected by Administration → Settings → View. Specialist write rights of the target module may also be required. If the page is missing, check role and module access.

How is this guide?

On this page