Migrate from Agworld to Nutshell

Agworld farms map directly to Nutshell Companies. The farm name becomes the Company name, address fields map to the standard address block, and total acreage from all fields is stored as a custom number field (Total_Acres__c). Owner resolution uses email matching to assign a Nutshell user as the Company owner, preserving the hierarchy for reporting. Multi-farm accounts generate one Company per farm.

Agworld fields attach to their parent Farm/Company as a structured set of custom fields — Field_Name__c, Crop_Type__c, Hectares__c, Irrigation__c, and Soil_Type__c. Boundary polygon data (geometry) has no Nutshell equivalent; we preserve it as a text note (Boundary_WKT__c) for reference only.

Agworld seasons (Spring, Summer, Fall, Winter or crop‑year based) have no native Nutshell equivalent, so we add a Season__c pick‑list custom field to Nutshell Deals. Each job, recommendation, and associated product record inherits the season label from its parent season context in Agworld, preserving the temporal planning scope within the CRM for reporting and segmentation.

Agworld jobs (spray, fertilizer, harvest, planting) map to Nutshell Deals. The Deal name reflects job type plus field name. Job status (planned, completed) maps to Nutshell Deal status (Open, Won, Lost). Job cost and product quantities become Deal amount and custom line-item notes.

Agworld job statuses (Planned, In Progress, Completed, Skipped) map to Nutshell Deal statuses. 'Completed' jobs route to Won deals; 'Planned' and 'In Progress' route to Open deals; 'Skipped' routes to Lost deals. This preserves work-flow state while fitting Nutshell's binary deal model.

Agworld products such as fertilizers, pesticides, and seed varieties are stored as custom fields on the linked Nutshell Deal—Product_Name__c, Active_Ingredient__c, Application_Rate__c, and Unit_Cost__c. If your product catalog exceeds 50 unique items, a separate Products custom object can be created in Nutshell to avoid field‑proliferation and to enable product lookups across multiple deals.

Agronomist recommendations—including pesticide rates, nutrient plans, and application timing—are migrated as Nutshell Notes attached to the appropriate Deal or Company record. The note body includes the full recommendation text, the product name, recommended application rate, and any supporting commentary. The original creation timestamp and author information are retained in the note metadata for auditability.

Agworld field observations—such as pest presence, disease pressure, soil moisture levels, and plant health indicators—are migrated as Nutshell Notes attached to the parent Company record. Each note records the observation type, the recorded date and time, and a concise description of the condition observed, preserving the full historical context for agronomists and sales teams reviewing the account.

Agworld spray records hold product, rate, weather conditions, applicator, and target pest. These map to a set of custom fields on the related Deal (Product_Sprayed__c, Rate__c, Weather_Conditions__c, Applicator__c, Target_Pest__c) plus a Note containing the full spray record text. Original application timestamp preserved as a custom datetime field.

Agworld file attachments—including prescriptions, compliance reports, application logs, and field maps—are downloaded from Agworld and re‑uploaded to the appropriate Nutshell Company or Deal record. Nutshell imposes a file‑size limit; any attachment exceeding 25 MB is flagged for manual upload to avoid processing errors, and the original file name is preserved for reference.

Agworld user accounts are matched to Nutshell users by email address. Unmatched users are flagged before migration — your team either creates a Nutshell user account or assigns records to a fallback owner. No record lands without a valid owner reference.

Agworld workflow templates and tank mix configurations are application-layer constructs that do not export as structured data. These must be rebuilt manually in Nutshell or documented from Agworld exports as reference for your team. FlitStack provides a structured export of workflow definitions for rebuild use.