Migrate from Agworld to Microsoft Dynamics 365 Sales

Agworld Farm maps directly to Dynamics 365 Account. Farm name becomes Account Name, address data maps to Address composite fields, and the primary contact on the farm resolves to the Account's primary contact role. Multi-farm operations generate multiple Account records linked by Parent Account if a hierarchy exists in Agworld.

Agworld Field records have no native equivalent in Dynamics 365 Sales. We create a custom table (agworld_Field__c) with lookup to Account. Field attributes (boundary acres, soil type, crop history) map to custom fields on this entity. Field location coordinates store as text or integrate with Dynamics Maps if available.

Agworld Crop records (wheat, corn, cotton, etc.) per field merge into the agworld_Field__c custom entity. Crop type becomes a picklist field; variety information stores as text. Multiple crops per field (rotation) captured as repeating custom fields or activity-linked records. Each crop entry includes planting date and expected yield for historical tracking.

Agworld activity types (spraying, planting, fertilizing, harvesting) map to Dynamics 365 Tasks with Type picklist values set per activity category. Original timestamps, product/product-rate data, and applicator notes preserve in custom fields on the Task record. Activity parent links to the related Field custom entity.

Agronomist recommendations in Agworld split into a Note (for the recommendation text and rationale) and a Task (for follow-up actions). Recommendation date and author map to Note creation metadata and owner lookup respectively. Completed recommendations link back to the originating agronomist Contact record.

Agworld users (Growers, Agronomists) resolve by email match to Dynamics 365 SystemUser records. Unmatched users flagged before migration. User roles in Agworld (grower vs. agronomist) preserved as custom fields on the Dynamics user record for reporting and security role assignment post-migration.

Agworld file attachments (PDF reports, controller files, images) re-upload to Dynamics 365's SharePoint integration connected to the Account or Field entity. Small files (under 10MB) may attach directly to Note records. File size limits and SharePoint storage quotas apply per Dynamics 365 licensing tier.

Soil sample results stored in Agworld map to a custom entity linked to the Field entity. Sample date, lab, and key results (pH, nutrient levels) store as custom fields. Raw lab data files attach via SharePoint or Note. Include sample location GPS coordinates for spatial analysis.

Agworld field observations (pest sightings, moisture levels, crop stress) map to Dynamics 365 Notes attached to the Field custom entity. Observation timestamp and author preserve as Note metadata. Photos associated with observations re-upload to SharePoint. Add a category tag for each observation type to enable filtered reporting in Power BI.

Agworld's connections to John Deere Operations Center, Figured, Frames by Agworld, and Greenbook label lookup do not migrate. These integrations must be rebuilt separately in Dynamics 365 or replaced with equivalent Microsoft Power Automate workflows and third-party connectors. Document each integration's endpoints and authentication methods to streamline the rebuild.

Agworld workflow constructs (plan-to-record conversion, recommendation-to-job templates) have no Dynamics 365 equivalent. We export workflow definitions as documentation for rebuild using Power Automate or Power Apps on the Microsoft platform. Include trigger conditions, data flow steps, and error handling logic to guide the implementation team.