Migrate from Agworld to Zoho CRM

Agworld has no Leads or Opportunities — Zoho CRM will receive a new commercial model

Agworld stores commercial relationships implicitly — agronomist recommendations and activity history carry business value but are not tracked as CRM opportunities. When migrating to Zoho CRM, you are creating a commercial layer that did not exist in Agworld. We set up the Leads and Deals modules as part of the migration plan: agronomist recommendations become Tasks with a recommendation flag, and your sales team must create Deals from those recommendations manually in Zoho CRM after migration or by importing a deals list alongside the activity data. This is not data loss — it is surfacing a commercial model that was not present in the source.

Agworld API rate limit of 200 requests per minute forces migration batching

Agworld enforces a 200 requests per minute cap with a maximum of 4 concurrent connections. For migrations with tens of thousands of activity records, we cannot pull all records at full speed. We batch Agworld API reads at 100 records per page and introduce a 300ms throttle between requests, keeping well under the 200/minute ceiling. The migration run time scales linearly with record volume — a dataset of 50,000 activities takes approximately 8–10 hours of API read time alone, plus transformation and Zoho write time. We surface this pacing constraint in the migration plan so you can schedule the migration run during off-peak hours if needed.

Field boundary GeoJSON serializes as text — no native Zoho CRM spatial display

Agworld stores field boundaries as GeoJSON polygons, linestrings, or points with coordinates in WGS84. Zoho CRM has no spatial field type, no native map widget in the standard CRM module, and no built-in GeoJSON rendering. We store boundary GeoJSON as a custom text field (Boundary_JSON__c) on the Field sub-form. This preserves the geometry for export to a GIS tool or a Zoho Creator custom map widget, but standard Zoho CRM list views and reports will not display field shapes. We recommend planning a Zoho Creator map page post-migration if spatial visualization is business-critical — we document the boundary JSON structure in the field mapping plan to support that build.

Agworld offline-sync timestamps do not reflect device-entry time

Agworld supports offline activity recording — field staff create activities on their iPad with no connectivity, and the app syncs when back in range. The modified_at timestamp on synced records reflects the server-apply time, not the original device-entry time. The actual time the activity was performed in the field is lost in the API. We preserve modified_at as Original_Modified_Date__c, but your team should be aware that Zoho reports will show the sync timestamp rather than the field timestamp for offline-recorded activities. If exact field-entry timestamps are regulatory-required (some spray records require real-time timestamps for compliance), this should be flagged during planning and the Agworld mobile audit log may need to be referenced separately.

Zoho CRM API credit model limits concurrent write throughput on higher-tier migrations

Zoho CRM's API credit model allocates credits per edition: Professional tier provides 50,000 base + 500 per user per day. The Bulk Write API consumes 500 credits per initialize call, and Insert/Update consumes 1 credit per 10 records. For migrations with large field sub-form data (where each field requires multiple sub-form row inserts per Account), the Zoho credit budget can constrain write throughput. We monitor X-API-CREDITS-REMAINING headers during migration runs and pause Zoho writes when credits fall below 20% of the daily budget, resuming once the rolling 24-hour window refreshes. We document the expected credit consumption in the migration plan so Zoho admins can purchase a credit add-on if the migration is expected to exhaust the daily budget.