Migrate from Agworld to Pipedrive

Agworld Farm maps to Pipedrive Organization. Farm name becomes Organization name. Farm address, total acreage, and primary crop type migrate as standard Organization fields. Farm-level notes and management notes become Organization notes. Multi-farm Agworld accounts generate multiple Pipedrive Organizations linked by a shared tag.

Each Agworld Field becomes a separate Pipedrive Organization linked to its parent Farm Organization via Organization Hierarchy. Field boundary shapefiles are downloaded and re-uploaded as Organization attachments. Field crop type, acreage, soil type, and irrigation status migrate as Organization custom fields. This preserves field-level data while keeping Pipedrive's flat organization model intact.

Agworld grower contacts map directly to Pipedrive People. The primary Farm or Field is set as the Person's primary Organization. Grower role (operator, owner, manager) migrates as a custom picklist field on Person. Email, phone, and address fields map directly. Owner is resolved by email match against Pipedrive users.

Agworld agronomist contacts map to Pipedrive People with a custom field indicating their role as 'Agronomist.' Their associated farms are linked via Organization membership. Agronomist visit logs (field observations, soil sampling notes) migrate as Pipedrive Activities linked to the relevant Field Organization.

Agworld contractors (sprayers, harvesters, applicators) map to Pipedrive People with a 'Contractor' role custom field. Contractor licenses, service areas, and equipment types migrate as custom fields. Contractor-linked jobs in Agworld become Pipedrive Deals with the contractor as an associated Person.

Agworld Jobs (spraying, seeding, harvesting, fertilizing operations) map to Pipedrive Deals. The Job type becomes the Deal category — we create a Pipedrive pipeline named 'Field Operations' with stages reflecting job status (Scheduled, In Progress, Completed, Invoiced). Each job is linked to the relevant Field Organization. Product inputs used in the job map to Pipedrive Products attached to the Deal.

Agworld agronomic recommendations (pesticide rates, fertilizer prescriptions, seeding plans) migrate as Pipedrive Notes attached to the relevant Field Organization or Deal. Recommendation status (Pending, Approved, Applied) is preserved in the Note body. Prescription shapefiles are downloaded and attached to the Note as files.

Agworld field visit logs documenting scouting observations, soil sampling activities, and crop inspections become Pipedrive Activities with Type set to 'Field Visit'. Original timestamps, visit duration, and observer (owner) information are preserved in the migration. Each activity is linked to the relevant Field Organization and associated Job or Deal for complete traceability and context in Pipedrive's activity timeline.

Agworld product catalog entries map to Pipedrive Products. Product name, SKU, unit of measure, and standard price migrate directly. Product category (pesticide, herbicide, fertilizer, seed) maps to Pipedrive Product category. Agworld's Greenbook-linked products preserve the external ID as a custom field for reference.

Agworld users (staff, agronomists, farm managers) are matched to Pipedrive users by email address. Owner assignment on migrated records uses this resolution. Users who cannot be matched are flagged and assigned to a fallback Pipedrive user until accounts are provisioned.

Agworld Season Plans aggregate multiple jobs and recommendations for a field over a growing season. These map to a Pipedrive Deal grouping using a custom field 'Season Plan ID' linking child Deals (individual jobs) to a parent Deal representing the season. Your team defines the grouping convention during scoping.

Agworld prescription shapefiles, application maps, and soil sample PDFs are downloaded and re-uploaded as Pipedrive file attachments on the relevant Organization (Field) or Deal. File size limits per Pipedrive's storage policy apply. Maps requiring precision viewing are attached as external links.