Migrate from Agworld to Freshsales

Agworld's agricultural data model has no direct Freshsales equivalent — every domain concept requires custom fields or custom modules

Agworld structures all data around farm operations: fields tied to acreage and crop cycles, activities linked to chemical application rates and soil conditions, jobs tracking operational costs. Freshsales is a standard sales CRM with no native support for acreage, crop type, soil classification, irrigation method, product application rate, or growth stage. Every Agworld field in these categories creates a corresponding Freshsales custom field, and the Field entity itself becomes a Freshsales custom module. If Agworld uses custom fields extensively, the Freshsales schema setup (custom fields + custom module + field-level permissions on Pro and Enterprise plans) adds planning time before data lands. FlitStack delivers the complete custom field and module specification upfront so Freshsales admins can pre-create the schema.

Freshsales per-seat pricing means every Agworld user becomes a Freshsales license — farm teams with many users face cost scaling

Freshsales uses per-seat user licensing across all plans. Agworld farm setups often include the farm owner, multiple agronomists, contractors, and field staff — each with their own Agworld login. When migrated to Freshsales, each user needs a seat on the appropriate plan tier. The Pro plan at $39/user/month becomes expensive for large farm teams, and the Enterprise plan at $59/user/month adds field-level permissions and custom modules. Teams should audit which Agworld users actually need CRM access (sales-facing and account management roles) versus operational-only roles before migration to right-size Freshsales licensing.

Agworld workflows and job-creation triggers do not transfer — the operational automation logic must be rebuilt in Freshsales

Agworld workflows automate job creation from field activity templates, trigger notifications based on crop growth stage, and coordinate recommendations from agronomists to farm operators. Freshsales automation (workflow rules, assignment rules, and sequence enrollment) operates on a CRM logic model and cannot import Agworld workflow definitions. The specific automation triggers, conditional logic, and field-update rules built in Agworld are lost in any data-only migration. FlitStack exports the workflow definitions as a reference document so the Freshsales admin can manually rebuild the applicable automations as Freshsales workflow rules after the data is loaded.

Agworld API rate limit of 5000 requests/hour and Freshsales plan-tier limits (1000–5000/hour) require throttled multi-cycle migration passes

Large farms with thousands of fields and multi-year activity histories can accumulate tens of thousands of records in Agworld. Agworld enforces a 5000 requests/hour limit on its API. Freshsales enforces plan-tier limits: 1000 requests/hour on Growth, 2000 on Pro, 5000 on Enterprise. FlitStack reads from Agworld at up to 5000 requests/hour and writes to Freshsales at the plan-tier limit, batching records in controlled cycles. For very large datasets the migration runs over multiple days with delta pickup at the end to capture any records modified during the migration window. This throttling is disclosed upfront so teams can plan for extended migration timelines.

Agworld's offline-first field app has no Freshsales equivalent — teams relying on field connectivity will face a workflow change

Agworld is built for offline-first field operations: users record spray applications, soil samples, and observations on iPads in the field without internet connectivity, and the data syncs when the device reconnects. Freshsales is a fully cloud-based CRM with no offline mode — all data entry requires an active internet connection. This is a material workflow change for field-heavy operations where agronomists or farm staff record observations in remote areas with poor connectivity. The migration transfers all historical field data correctly, but ongoing field data entry in Freshsales requires connectivity, which should be communicated to field teams before cutover.