365FarmNet Is Closing: What Happens to Your Farm Data

365FarmNet shuts down on 30 November 2026. If you're looking for a 365FarmNet alternative, the short answer for most farms is the official successor, CLAAS Connect. Your dealer moves your data across for free, and the first year of the licence costs nothing.

Whatever you decide, do these two things now:

• Export your own records. 365FarmNet says backing up is your responsibility. The migration only moves what you and your dealer agree on.
• Check what happens after year one. The free year turns into a paid contract automatically.

The rest of this guide explains what is verified, what isn’t, how to transfer your data, and when an alternative route makes a difference.

What is happening to 365FarmNet, and when?

365FarmNet will close on 30 November 2026, and support will end on the same date. CLAAS has been moving its functions into CLAAS Connect since October 2024.

What you need to know:

• New sign-ups are already closed. Existing users can keep working as normal until the shutdown.
• Invoices continue. 365FarmNet still bills the current year's licence pro rata.
• About 100,000 users have registered over the platform's lifetime, so dealers will be busy in November.
• Data after the shutdown: 365FarmNet hasn't said what happens to data left on its servers or whether exports still work on the last day. Assume they don't.

UK and Ireland: almost all the transition material, including the webinars, is written for German farms. Ask your CLAAS dealer early how they're handling the switch.

What moves to CLAAS Connect, and what doesn't?

Data can be migrated free of charge, but it is agreed with your dealer, case by case, which data will move. The main tasks of 365FarmNet, such as field records, planning, machine data, and precision farming, are included in CLAAS Connect.

How the switch works

You can't switch on your own. CLAAS sells through dealers, so a dealer is required. The process has four steps:

1. Contact your CLAAS dealer, or use the switch form on 365FarmNet's website.
2. Sign a changeover contract.
3. Give your 365FarmNet login details to your contact person. They run the migration at an agreed appointment.
4. Log in to your new CLAAS connect account.

What it costs

Put the renewal date in your diary the day you sign.

What CLAAS Connect handles

• Mixed fleets: ISOXML from ISOBUS terminals, the Data Connect link to John Deere and CNH, and trackers such as LACOS and Exatrek.
• FAKT scheme: CLAAS says farms in Baden-Württemberg's FAKT agri-environment program can meet its record requirements.
• Exports: PDF and CSV from the app, and ISOXML for completed work.

What is still unclear

• Which data migrates. There's no published list. The FAQ says your sales partner decides with you "which data makes sense to migrate in your specific case." You won't know until the appointment whether every harvest year and every boundary version comes across.
• Price and cost management. It's promised for 2026 and isn't complete yet. That matters if you used 365FarmNet for margin work.
• Add-on modules. If you booked one in 365FarmNet, you have to cancel it yourself after signing the CLAAS Connect contract.

How do you export your data from 365FarmNet?

Use 365FarmNet's built-in exports, one harvest year at a time, and finish well before 30 November 2026. Do this even if you're migrating. It's the only copy you control.

365FarmNet treats these as two separate jobs:

• Migration: Your dealer copies data into CLAAS Connect.
• Backup: You export files and keep them yourself.

The exports to run

365FarmNet's own backup guide, which has screenshots, covers the first four:

Take the ISOXML export if there's any chance you'll move to something other than CLAAS connect.

How to keep the files usable

• Export by harvest year, not one big date range. Smaller files are easier to check.
• Use the same file names every time, for example, farm-record-type-year.
• Open every PDF. Spot-check one CSV against a field you know well.
• Keep two copies, one of them off the farm computer.

Field boundaries: check before you assume

• The official guide doesn't include a boundary export.
• A field map saved as PDF is only a picture. Another system can't import it as a boundary.
• One competing vendor says boundaries can be exported as a shapefile.
• Ask 365FarmNet support how to get them out in a usable format: [email protected] or 00800 365 365 36.

The 2027 spray record rule (EU farms)

From 1 January 2027, farms in EU countries such as Germany and Austria must keep plant protection records electronically, in a machine-readable format. Paper records have to be converted within 30 days.

• Your PDF archive covers records.
• It won't cover next season's spraying.
• Whatever system you move to must produce these records.

For moving field records from one system to another, see our companion guide.

Is there a 365FarmNet alternative worth considering?

For most farms, CLAAS Connect is the sensible choice. The migration is free; your dealer helps, and year one costs nothing. You have three realistic routes:

Several German field record vendors are already targeting 365FarmNet users, some at low annual prices. Before you compare prices, ask each one:

• Does it import Shapefile and ISOXML?
• Does it handle fertiliser planning (Düngebedarfsermittlung) for your federal state?
• Can you export all your data again if you leave?

That last question is the real lesson of this closure.

When owning your own platform makes sense

A custom platform is worth looking at if "one farm, its fields, its machines" doesn't describe your business. For example:

• Contractors (Lohnunternehmer) documenting work on customers' fields across several machine brands and invoicing from that record.
• Advisers, co-ops, and farm groups managing data for many farms with their own reporting.
• Agritech businesses whose product ran on top of 365FarmNet.
• Operations with unusual integrations, such as weighbridges, sensors, accounting, or subsidy systems.

If that's you, settle the data model first, starting with fields:

• A boundary drawn on satellite imagery rarely matches the legal parcel (Flurstück) in the cadastral record.
• Leases, subsidy claims, and field records may each use a different one.
• Every later record attaches to the field, so getting this wrong is expensive to fix.

On a farm platform we built on a field model matched to the German cadastral record, this was the first decision we made. See how we approach farm and agritech software.

Owning a platform also means paying to run it:

• Hosting and security patches
• Map and cadastral data updates
• Changes when rules change, such as the 2027 spray record rule

Plan for ongoing maintenance and support from the start.

When it doesn't

Move to CLAAS Connect if any of these fit:

• You run one farm, use CLAAS machines and mainly require field, spray and fertiliser data.
• No one in business has time to invest in a software project.
• A standard Ackerschlagkartei already does what you need.

In these situations, a custom build would incur more than years of licences and burden you with software requiring maintenance. The same reasoning applies to any build-versus-buy decision for business software: custom pays off when your processes are unusual and stable.

Your checklist for October and November 2026

Moving off a closing platform? Talk to us about owning your data.

FAQs

Do I have to switch to CLAAS Connect?

No. You can use 365FarmNet until 30 November 2026 and keep the data you export. CLAAS Connect is the official successor, not a requirement.

Is CLAAS Connect free?

Partly. Machine management is free with CLAAS machines. Farm management needs a paid licence after the free first year, and the contract renews automatically.

Can I use CLAAS Connect with a mixed fleet?

Yes, through ISOXML, the Data Connect link to John Deere and CNH, and some third-party trackers. CLAAS says support for non-CLAAS machines is still being expanded.

Will my field boundaries come across?

The official manual doesn't say that. Neither does the FAQ. Ask your dealer before the migration appointment and request 365FarmNet support on how to export them yourself.