Migrate your Agworld data

Farms are the top-level container in Agworld's data model. They hold a name, location, and aggregation of all Fields within them. We migrate Farms 1:1, preserving the farm name and any metadata fields attached to the farm record.

Fields belong to a Farm and carry crop type, acreage, crop year, and optional permanent-crop attributes like rootstock and polleniser variety introduced in 2024. Standard field attributes migrate cleanly. We flag any custom field attributes for manual review.

Jobs exist in multiple states: planned, recommended, or actual (completed). The plan-to-actual conversion is a core Agworld workflow. We preserve job state, linked field, activity type, product inputs, dates, and costs. Multi-state jobs require mapping to the destination's equivalent status model.

Observations are free-text or structured field notes captured at the field level — soil moisture, pest pressure, irrigation notes. We migrate observations with their timestamp and linked field, preserving them as notes or comments in the destination.

Agronomist recommendations (fertilizer rates, pesticide applications) flow into the grower's account and can be converted to Jobs. We migrate recommendations with their linked field, product details, and recommended rates. The conversion-to-job relationship is preserved by mapping the recommendation ID as a reference property in the destination.

Agworld distinguishes role types: Grower (primary account holder), Agronomist, Contractor, and Viewer. We migrate user records with their assigned role and contact details. Team permission structures and sharing settings may require manual reconstruction in the destination.

Soil sampling records include lab reference, collection date, field location, and test results. Agworld integrates with sampling labs via the Frames by Agworld API. We migrate sample records with all result fields intact.

Agworld generates regulatory compliance reports from structured field activity data. We migrate the underlying activity records (application dates, product rates, weather conditions) that feed compliance reports so the destination can reconstruct audit documentation.

Precision data — machine controller files exported from the iPad app to equipment — is tied to specific hardware configurations and job-linked machine logs. This data does not have a portable schema and is excluded from standard migrations. We advise customers to retain precision file archives independently.

Crop templates standardize job structures (application rates, product sequences) for common crop types. We migrate template definitions with their activity steps and product assignments. Template-to-job inheritance logic may require reconstruction in the destination platform.

Agworld integrations sync financial planning data (Figured), machine data (John Deere), third-party contextual data (Frames), and reporting (Power BI). Integration connections require manual reconfiguration in the destination — we document current integration mappings for re-setup.

Agworld organises data by season or crop year. We preserve the season structure so historical comparisons of planned versus actual product usage and cost of production carry over to the destination intact.