Import vineyards

Instead of creating every vineyard individually, you can import your vineyard data from external agricultural management systems. The import brings across both master data (name, grape variety, vine area) and area geometries, provided these are included in the source file.

Supported import sources

Vinitor supports import from the following systems:

Import source	Region
eAMA	Austria
FIONA	Baden-Württemberg, Germany
LAFIS	South Tyrol, Italy
LEA	Rhineland-Palatinate, Germany
LAWIS+	Switzerland

Tip

Depending on the import source, different file formats are expected (usually ZIP files containing shapefiles). In the import wizard, first select the appropriate import source, then upload your export file — Vinitor automatically maps the included fields to the correct structure.

Don’t see your system?

We can usually connect new import sources within a few days. Just send us a sample file by email to support@vinitor.app — we’ll take care of the implementation.

Export guides

For each supported system there is a detailed step-by-step guide to exporting your data:

eAMA / INVEKOS-GIS Shapefile export from the eAMA portal for Austrian businesses.

FIONA GIS export from FIONA for businesses in Baden-Württemberg.

LEA Shape export from LEA for businesses in Rhineland-Palatinate.

LAFIS (South Tyrol) Shape export from LAFIS for businesses in South Tyrol (Italy).

LAWIS plus Geometry data export from the new LAWIS plus system (Switzerland).

Import wizard

The import runs through a three-step wizard:

Step 1: Upload file

1. Navigate to Field record book in the sidebar.

2. Click Import in the top right.

3. Under Import source, select the system your data comes from (e.g. eAMA, FIONA).

4. Upload your file by dragging and dropping it into the upload area, or by clicking to select a file.

5. Configure the import settings (see below).

6. Click Import.

Import settings

Before importing, you can configure two options:

Option	Description
Overwrite attributes	If enabled, master data (name, grape variety, Ried, parcel number, vineyard number) of existing vineyards is overwritten with the values from the import file.
Remove vineyards not included	If enabled, vineyards not included in the import file are set to Inactive status (not deleted).

Caution

Check the import settings carefully before starting the import. The Overwrite attributes option irreversibly replaces existing master data. If you’re not sure, leave this option disabled — this way, only new vineyards are created and existing ones remain unchanged.

Step 2: Resolve conflicts

If the import detects overlaps with existing vineyards — e.g. matching numbers or overlapping areas — the wizard displays a conflict list.

For each conflict, you can decide how it should be handled. Some conflicts are resolved automatically, others require your manual decision. You can only continue once all manual conflicts have been resolved.

Note

Conflicts often occur when you repeat an import (e.g. after an update in eAMA). In most cases, you can accept the automatic suggestions.

Step 3: Complete

Once processing is complete, the wizard displays a summary. Your imported vineyards now appear in the field record book — including map geometries, provided these were included in the source file.

After the import

After a successful import, we recommend:

• Check master data — Spot-check that the name, grape variety and area were transferred correctly.
• Check map geometries — Open a few vineyards in the detail view and check that the drawn areas are displayed correctly.
• Add leaf wall height and row spacing — Most import sources don’t supply these fields, but they’re required for the plant protection calculation. Use bulk editing in the field record book to enter these values efficiently for all vineyards.
• Assign groups — Organise your imported vineyards into groups to structure them logically.