Migrate from Field Squared to Zoho CRM

Task scheduling data splits across Zoho Tasks and Events

Field Squared stores scheduling with both ScheduledStart and ScheduledEnd datetime fields on every task record. Zoho Tasks support only a Due Date (single datetime), while Zoho Events use Start DateTime and End DateTime for calendar-style scheduling. We resolve this by mapping single-datetime Field Squared tasks to Zoho Tasks with Due Date, and tasks with both start and end times to Zoho Events. However, this means scheduling data for all-day or multi-hour tasks lives in a different Zoho module than task records — your team will need to account for this when building Zoho reports or dashboards that combine scheduling and task status.

Zoho API credit consumption limits bulk migration speed

Zoho CRM API uses a credit-based consumption model where different operations deduct different credit amounts. Get Records through COQL queries deduct 1–3 credits depending on record count per page; Get Related Records Count deducts 2 credits per related list fetch. During large migrations, API credit exhaustion causes throttling. FlitStack AI monitors X-API-CREDITS-REMAINING headers and implements backoff logic when credit usage exceeds 50% of daily limits. Zoho Enterprise tier provides 10,000 API credits per day versus 2,500 for Professional — migration speed is directly tied to your Zoho edition.

Field Squared custom fields require manual schema creation in Zoho

Field Squared's App Builder lets administrators create custom fields with 30+ data types on any object without version or edition restrictions. Zoho CRM restricts custom field creation by edition — Lookup and Formula fields require Professional+ — and field types have strict length limits that vary by data type. We create custom fields during migration setup, but any Field Squared custom field that exceeds Zoho's length limits (e.g., long text, multi-select) must be truncated or re-engineered. We surface these truncation risks in the pre-migration field mapping plan.

Owner resolution by email match fails for inactive Zoho users

Field Squared task owners are resolved by matching the external user ID to a Zoho User record via email address. Zoho deactivates users who leave the organization — inactive users do not appear in the user lookup, which means their tasks fail to write with a valid OwnerId. We flag inactive user matches before migration and surface them for your Zoho admin to either reactivate the user temporarily or reassign records to an active fallback owner. This is a Zoho data integrity requirement, not a FlitStack limitation.

Zoho bulk export caps at 200,000 records per job

Zoho's Bulk Read API limits exports to 200,000 records per job with pagination. For Field Squared migrations exceeding 200,000 task records, we run multiple sequential bulk export jobs with page offsets. Zoho's bulk export also only supports CSV and ICS formats for Events — the ICS format squashes recurring events into single entities, which means any recurring task logic in Field Squared loses its recurrence structure. We document this during discovery and preserve recurrence metadata in custom fields for manual Zoho Blueprint rebuild.