Migrate from Agworld to Twenty CRM

Agworld Fields map to Twenty Companies — field name becomes Company name, field boundary data (acreage, location) migrates as custom address and text fields. The field's linked season context is preserved in a custom Season__c pick-list field on the Company record.

Agworld's per-field crop type (corn, wheat, permanent/tree crop) has no direct Twenty equivalent. We create a Crop custom object with name, variety, planting date, and harvest date fields. The Field Company links via a relation field. Permanent crops with rootstock or polleniser variety data map to custom text fields on the Crop record.

Agworld Jobs (spraying, seeding, fertilizing, harvesting) map to Twenty Tasks. Task type maps to a custom pick-list field (JobType__c) with Agworld job-type values. Original activity date and product applied are preserved in Task description and custom product fields. The linked Field (Company) and Crop (Custom Object) relations are established during import.

Agworld job-level notes (irrigation status, soil moisture observations, weather conditions at application) migrate as Twenty Notes attached to the Task record. Original timestamp and user who logged the observation are preserved in Note metadata. The notes retain the original author and exact time, ensuring a complete audit trail.

Agworld Recommendations from agronomists (product type, rate, timing, status) require a custom object in Twenty. Fields include: recommended product, application rate, unit, timing, status (Draft/Sent/Approved/Declined), and linked Field relation. Status transitions are preserved as a pick-list. Approved recommendations can generate a linked Opportunity in Twenty for follow-up sales actions.

Agworld's product database (fertilizers, pesticides, seeds) migrates as a Product custom object in Twenty. Fields include product name, type (chemical/biological/seed), manufacturer, unit of measure, and SDS link. Products linked to Jobs carry usage rate preserved in a text field. This lets teams build Twenty Opportunities for input sales.

Agworld Seasons (annual planning cycles) map to a Season__c custom pick-list field on Field Companies and linked Crop records. Each season carries financial targets and planned acres — those numeric fields migrate as custom number fields. Active season status is preserved for reporting continuity.

Agworld users with roles map to Twenty Workspace Members. Role (Grower/Agronomist/Contractor) migrates as a custom pick-list field on the Workspace Member record. Email is used for matching. Unmatched Agworld users are flagged before migration — your team invites them to Twenty first or assigns their records to a fallback member.

Agworld prescription files (SHP/SHX/DBF shapefiles) are not migratable via CSV. We download the files and re-upload them to the linked Company or Crop record in Twenty as attachments. Geometry data requires manual re-mapping in Twenty's map view since Twenty has no native shapefile import.

Agworld compliance documentation (application records, buffer zones, withhold periods) migrates as Notes on the Job Task record or a ComplianceRecord custom object. The compliance status and reporting body are preserved as custom pick-list fields. Reporting period and submission date are stored as date fields for audit continuity.

Agworld integrations with Xero, Figured, John Deere, and Frames do not transfer to Twenty. These connections must be rebuilt in Twenty or replaced with alternative integrations. We document the integration mapping so your admin can reconfigure connections post-migration. Post‑migration, we provide a checklist of required API credentials and endpoint URLs.

Agworld tank mix configurations (product combinations, rates, water volume) from the iPad/iPhone app are extracted as structured JSON and loaded into a TankMix custom object in Twenty. Mix ratio and unit fields map to custom number and pick-list fields. The tank mix links to the Job Task that used it.