Migrate from Agworld to HubSpot

Agworld Farm maps directly to HubSpot Company. The farm name field becomes the HubSpot Company Name property, and the farm address maps to HubSpot's standard address properties. Farm-level metadata such as total acreage and primary crop type migrate as custom properties on the Company record, ensuring that operational context is preserved alongside the company identity in HubSpot's CRM.

Agworld Fields are not a native HubSpot object. Each Field maps to the parent Farm's Company record with field name, acreage, crop type, boundary data, and season information stored as custom properties. Complex field hierarchies (parent/child fields) use HubSpot's Company associations.

Permanent crop fields in Agworld carry rootstock, grafting date, polleniser variety, and tree-density attributes. These map to a HubSpot custom object or a set of custom fields on Company. At non-Enterprise HubSpot tiers, these attributes store as custom text or date properties and teams accept the reduced structure.

Agworld Jobs (spraying, seeding, fertilizing, harvesting, soil sampling) map to HubSpot Deals. Job name becomes Deal name. Job type (activity category) maps to a deal property. Original create date, completed date, and operator who completed the job migrate as custom fields.

Agworld job statuses (planned, in-progress, completed, cancelled) map to HubSpot Deal stage values through a defined value-by-value mapping in the migration configuration. During setup, teams choose whether to consolidate all job types into a single HubSpot pipeline or create separate pipelines per job category — the choice affects how deal filters and reports display operational data in HubSpot's CRM.

Agworld Products map to HubSpot Products and Line Items. Product name, active ingredient, and unit of measure migrate. Application rate (e.g., lbs/ac or gal/ac) and method (spray, broadcast, injection) store as custom properties on the Line Item because HubSpot's standard product model does not capture application-rate data.

Agworld agronomist Recommendations map to HubSpot Notes or Emails attached to the relevant Deal, preserving the recommendation text, date, author, and status. The recommendation-to-job conversion record in Agworld — which links a recommendation to the resulting job — is preserved as a custom property on the Deal, allowing teams to trace advisory recommendations through to completed field work in HubSpot's timeline view.

Agworld team members including farm operators, agronomists, and contractors map to HubSpot Contacts with name, email, phone, and role preserved during migration. Agworld owner assignment on Jobs resolves by matching the operator email to a HubSpot user; any unresolved owners are flagged as exceptions before the migration run executes, ensuring no record lands in HubSpot without a resolved owner assignment.

Agworld field observations, weather notes, and activity log entries map to HubSpot Engagements — Notes for observations, Calls for in-field work entries. Original timestamps and associated field reference migrate. Activity type property on the engagement record captures the Agworld activity category.

Agworld season or crop-year data is not a native HubSpot object. We create a Season__c custom pick-list or text property on the Deal object and populate it from Agworld's season assignment. This allows HubSpot reporting by season without altering the core object model.

Agworld attachments and precision data files (controller export files, soil sample PDFs) re-upload to HubSpot Files and associate to the relevant Company or Deal record. Large precision files may store reference URLs to external storage if HubSpot's 25MB file limit is a constraint.

Agworld integrations with Figured (financials), John Deere (equipment), and Frames by Agworld (IoT data) have no direct HubSpot equivalent. These connections must be rebuilt on the HubSpot side using each respective platform's HubSpot app or API integration — Figured offers a HubSpot connector, John Deere data requires a new API integration, and Frames is specific to the Agworld ecosystem.