Migrate from Fieldproxy to Zoho CRM

Fieldproxy Organizations map directly to Zoho Accounts. Organization name becomes Account Name. Parent organizations map to the Parent Account lookup. Multi-company associations in Fieldproxy collapse to one primary Account with secondary relationships stored in Account Contact Relations. During migration, we validate that each Organization's primary contact and billing address transfer correctly to the corresponding Account record, ensuring data integrity across the organizational hierarchy.

Fieldproxy Contacts map 1:1 to Zoho Contacts. First name, last name, email, phone, and address fields transfer directly. Owner assignment resolves by email match against Zoho Users list. Any custom contact fields in Fieldproxy require pre-created Zoho custom fields before migration runs. We also verify that contact-to-organization links map correctly to Zoho's Account Name lookup on Contacts.

Fieldproxy Jobs map to Zoho Deals — the closest equivalent in Zoho's data model. Job name becomes Deal Name. Job amount maps to Deal Amount. Job status (Pending, In Progress, Completed, Cancelled) maps to Zoho Deal Stage values via value mapping per pipeline. Close date maps to Expected Close Date.

Zoho Deals do not have a native scheduled start date field. Fieldproxy's scheduled_start migrates to a custom datetime field (Scheduled_Start__c) created in the Deal module before migration runs. We preserve the original timezone information in the field value and validate that date formats align with Zoho's datetime requirements. This ensures your scheduling data remains accurate and actionable within Zoho's interface.

Fieldproxy's actual_end timestamp marking job completion has no Zoho native equivalent. We create Actual_End__c as a custom datetime field on Deals during schema setup. This preserves historical job completion data for reporting continuity. The field stores the full timestamp with original timezone data, enabling accurate reporting on job duration, technician performance, and service level metrics post-migration.

Fieldproxy service route data (route name, waypoints, optimization data) stores as text in Service_Route__c. If service routes are tracked as structured records in Fieldproxy, we assess whether to create a custom Service Routes module with a lookup from Deal, or store as formatted text for reference.

Zoho CRM has no native technician assignment field on Deals. We create a custom text or multi-user field (depending on whether Fieldproxy allows multiple technicians per job) and store the assigned technician name and ID. Owner of the Deal also gets resolved by email match for Zoho native assignment.

Fieldproxy Tasks map to Zoho Tasks. Subject, description, due date, and status transfer directly. Linked record ID (job ID, contact ID) stores as a custom reference field in Zoho for traceability. Owner resolves by email match. Task status values map to Zoho Task status (Not Started, In Progress, Completed).

Fieldproxy Events map to Zoho Events. Subject, start datetime, end datetime, and location transfer directly. Event type (scheduled visit, follow-up) stores in a custom field if the values don't match Zoho's event types. Contact and Deal associations use Zoho's WhoId and WhatId lookups.

Fieldproxy Call records map to Zoho Calls with subject, duration, outcome, and notes transferring directly. Call direction (inbound/outbound) maps to Zoho's Call Direction field. Owner assignment resolves by email match against Zoho Users. Linked record ID (referencing the original Job or Contact) stores as a custom reference field for traceability. This preserves the full call history and relationship context within Zoho CRM.

Fieldproxy Notes map to Zoho Notes. Note title, body content, and created datetime transfer directly. Rich text formatting in Fieldproxy notes is preserved in Zoho Notes. Notes linked to Jobs store the Job ID in a custom field for cross-referencing.

Fieldproxy file attachments (job photos, signed forms, invoices) require re-upload to Zoho via the Attachments API. We store the original Fieldproxy file URL as a reference field on the Zoho record so teams can locate the source file during the transition period. File metadata (filename, size, type) is preserved.

Fieldproxy Users and Technicians map to Zoho Users. Owner resolution happens by email match — if a Fieldproxy user email matches an existing Zoho user email, ownership transfers automatically. Unmatched users get flagged before migration and assigned to a fallback owner or invited to Zoho first.

Fieldproxy custom fields across all modules require Zoho custom fields created before migration. Multi-select fields in Fieldproxy need special handling — Zoho multi-select picklists store comma-separated values. Lookup fields that reference other Fieldproxy records store the external ID as a text reference field.

Fieldproxy technician routing rules, customer notification triggers, and inventory replenishment automations do not have Zoho native equivalents. These must be rebuilt as Zoho Workflow Rules, Blueprint stages, or Deluge scripts post-migration. We export the Fieldproxy workflow definitions as a structured reference document.