Skip to content
PhytAI
Sign in
Switching

Back up your data from 365FarmNet: boundaries, bookings, documents

Step by step: save field boundaries as a shapefile, booked work processes as CSV and your documents from 365FarmNet before it shuts down on 30 November 2026.

PhytAI editorial teamPublished Updated 9 min read

Key points

  • Deadline 30 Nov 2026, no grace period announced: back up yourself even if you move to CLAAS connect. What arrives there is decided case by case with the dealer; there is no official list.
  • Bookings in parts: one CSV export of work processes holds at most 1,000 rows. Export per harvest year and, if needed, in several periods.
  • Three kinds of data: field boundaries (geometry), bookings and records (tables), evidence and reports (documents).
  • Formats: boundaries as a shapefile in a ZIP folder, bookings as CSV, reports additionally as PDF for the archive.
  • Save per harvest year: this keeps files manageable and makes it easier to show records during an inspection.
  • Retention: in Germany, plant protection records at least three years, fertiliser records seven years – also after a software change.

Try PhytAI free for 30 days

  • No payment details needed
  • Export all your data as CSV, JSON and Shapefile at any time
  • from €59.00 a year
Try free for 30 days

365FarmNet will be switched off on 30 November 2026. Anything not backed up by then will most likely no longer be retrievable. 365FarmNet itself states: “Die Sicherung Ihrer Daten liegt in Ihrer Verantwortung” (backing up your data is your responsibility). The provider has announced no grace period, no read-only access after the shutdown and no deletion date (as of 18 Oct 2026). This article shows which data you should save, which format is most useful and how to take it into new farm record software. Background on the shutdown is in 365FarmNet shutdown: what farms should do.

Preparation: create a folder structure

Before exporting, create a folder structure, for example a folder "365FarmNet backup" with subfolders per harvest year and a folder "Field boundaries". Put the date of the backup into the folder name. Store a copy outside your work computer, for example on a USB stick or in cloud storage that you will still be able to access in a few years. Three copies in different places are a good rule. Open every file once after saving it so that you know it is complete.

Step 1: field boundaries as a shapefile

Field boundaries are the most important basis for any new software. They create the fields with their size and position, and many programs read the field identifier (FLIK) from the attributes.

This is how to download the boundaries in the web application, as described for example in the agvolution help pages:

  1. Open the Pflanzenbau (crop production) area in the top menu.
  2. On the left under Verwalten (manage), choose the Schläge (fields) tile.
  3. Select individual fields with the boxes next to their names, or select all with the top box.
  4. Choose Download above the table on the right.
  5. The boundaries arrive as a shapefile in a ZIP folder. Save the folder and do not unzip it if another program is to import it.

A shapefile consists of several files (.shp, .shx, .dbf, usually .prj). If one of them is missing, the data cannot be read. The ZIP folder keeps everything together.

Repeat the download if you maintained different boundaries for different harvest years. Background on the formats is in ISOXML, shapefile and GeoJSON.

Step 2: booked work processes as CSV

For analysing past years and for importing, structured tables matter more than reports. 365FarmNet provides booked work processes as CSV; according to the manufacturer's page, work processes can be exported in the mobile app as CSV or PDF, with the CSV containing the raw data for your own analyses.

In the web application, booked work processes are found under Pflanzenbau → Erfassen (record) → Arbeitsvorgänge (work processes), view “Verbucht” (posted). According to the 365FarmNet help, one CSV export holds at most 1,000 work processes. Filter by period, at least per harvest year, and split a year with many bookings into several exports. Check the row count of every file: if a file has exactly 1,000 rows, choose a shorter period, otherwise bookings may be missing. Export the same list as PDF as well; that is the readable backup.

Check the CSV briefly in a spreadsheet after exporting:

  • Are all fields, dates and products included?
  • Are quantities stored with units in the columns?
  • Do German umlauts display correctly? If not, choose UTF-8 or Windows-1252 encoding when opening the file.

Step 3: reports and evidence as PDF

Readable reports are helpful for the archive. In 365FarmNet the most important ones are under Pflanzenbau → Auswerten (evaluate):

  • Schlagkarte (field card): choose the harvest year and save as PDF, for every harvest year; “pro Frucht” (per crop) if you like.
  • CC-Nachweis (cross-compliance proof) for plant protection: as PDF for every harvest year.
  • Nährstoffe (nutrients): as CSV and PDF per year.
  • Ernteerträge (yields): as CSV per year.
  • Verbräuche (consumption) as PDF and, under Betrieb → Auswerten, the Lagerbericht (stock report) by printing to PDF.
  • The fertiliser requirement template (Nährstoffbedarf → Datenvorlage erstellen, Excel in a ZIP) is useful for reference; it is outdated and not accepted as proof.

A PDF shows what was documented at a given time. For the electronic plant protection records required from 2027, a PDF alone is not enough, however, because it is not machine-readable. Keep both: PDF for reading, CSV for further processing.

Step 4: do not forget other documents

A complete backup also includes documents that are often stored elsewhere:

  • subsidy application data and field lists from your federal state
  • soil analyses, for example as an Excel file or laboratory report
  • fertiliser requirement calculations and the annual summary under Annex 5 of the DüV
  • inspection reports for sprayers and certificates of competence
  • delivery notes for manure
  • soil samples, master data (machines, persons, products), documents and photos from 365FarmNet: no export is described for them. Save original reports, documents and photos yourself and keep lists of the master data.

If you use the paid module, you can also save planned orders as ISOXML (Arbeitsvorgänge → Geplant → Senden → ISO-XML); this covers planned, not posted, work processes only.

Step 5: request a complete export in writing

365FarmNet offers no programming interface for the export and no one-click full export. You can, however, ask the provider in writing before 30 Nov 2026 for a complete, machine-readable copy of your data, for example by email to support@365farmnet.com and digital-business@claas.com.

No legal advice. The following template is non-binding and has not been legally reviewed. The right to data portability under Art. 20 GDPR covers personal data only, so it suits sole traders and family farms better than a limited company or a cooperative. Whether the EU Data Act applies to farm management software is not settled. If in doubt, get advice.

Subject: Request for the complete release of my data from 365FarmNet

Dear Sir or Madam, I use 365FarmNet for the farm [farm name, customer number, email address of the account]. Because of the shutdown on 30 Nov 2026 I ask for a complete copy of all data stored for my account in a structured, commonly used and machine-readable format (for example CSV, shapefile or ISOXML), in particular: fields with boundaries, all posted and planned work processes with products and quantities, nutrient and harvest data, soil samples, master data on machines, persons and products, and uploaded documents and photos. Where personal data is concerned, I base this request on Art. 20 GDPR; where data from the use of connected products is concerned, on Regulation (EU) 2023/2854 (Data Act). Please confirm receipt and tell me a date before the shutdown by which I will receive the data. Yours faithfully, [name, address]

Step 6: take the data into the new software

How the import works depends on the new software. This order is common:

  1. Site and fields: import the field boundaries from the ZIP folder. Check names, size and identifiers in the preview.
  2. Crops of the current season: create crops and varieties per field or import them from a table.
  3. Products and stock: create plant protection products, fertilisers and seed and book stock levels as an inventory count.
  4. Open tasks: take over planned work as tasks.
  5. Past bookings: if the software offers it, read in the CSV files and check them. Otherwise they stay as an archive next to the new software.

How switching works in PhytAI

In PhytAI you import field boundaries under Data & export: shapefile as ZIP, GeoJSON or ISOXML. PhytAI suggests the columns for name and field identifier and shows a preview with the calculated area.

The CSV files of booked work processes are read in via the card “Switch from 365FarmNet”, including several files of one harvest year at once. Rows that two overlapping exports both contain arrive only once. PhytAI reads UTF-8 and Windows encoding, semicolons and commas, and German numbers and dates. Each row becomes a suggestion in the inbox, which you check and accept; fields are matched by FLIK or name, products by authorisation number or name.

To be honest: the columns of the 365FarmNet export are not publicly described, and the import has not yet been checked against real export files. PhytAI recognises the usual headings and lists the columns it cannot assign for review before the import. Not every 365FarmNet detail has a counterpart in PhytAI, and PDF reports as well as the CSV files on nutrients and yields stay an archive. If you do not see the card on your farm, support enables the import on request. The steps are in the manual under 365FarmNet: back up your data now and Data import & export.

Frequently asked questions

Is there access after 30 Nov 2026? Nothing of the kind has been announced: 365FarmNet names no grace period, no read-only access and no deletion date. Plan as if 30 Nov 2026 were the last day.

Can I import the ZIP file into CLAAS connect as well? CLAAS connect offers an import for field boundaries. Check the help pages of CLAAS connect for exactly which files are accepted.

What about machine data and yield maps? These data are closely tied to machines and terminals. Save them separately if you want to keep using them; many farm record programs do not import them.

How long do I have to keep the backup? In Germany, plant protection records for at least three years, counted from the start of the following year; fertiliser records for seven years after the end of the fertiliser year.

Sources

This article reflects the situation on the date shown, based on the sources named, and is not legal advice. Laws, approvals, official decisions and the guidance of the competent authorities prevail.

Related articles

All articles on the blog