Migrate from Field Nexus to Zoho CRM

Field Nexus client records migrate as Zoho Contacts. If the source record represents a prospect without an active work order, it lands as a Lead instead. Name, email, phone, and address fields map directly; job title migrates as a custom field on Contact.

Field Nexus company records map to Zoho Accounts. Parent-company relationships in Field Nexus preserve using Zoho's Parent Account lookup. Multi-client companies resolve to one primary Account with contacts linked via Account Name matching. Billing address, industry, and employee count migrate as standard Zoho Account fields.

The primary migration object. Field Nexus work orders map to Zoho Deals — Deal Name carries the work order title, Amount carries quoted or billed value, StageName carries the work order status via a value map (e.g., 'Scheduled' → 'Closed Won', 'Completed' → 'Closed Won'). Custom fields on the Deal capture service type, job category, and scheduling windows.

Zoho CRM has no native Service_Type field on Deals. We create a custom pick-list field (Service_Type__c) in the Deals module, populated with the distinct service-type values from Field Nexus. This field appears on the Deal layout for at-a-glance categorization. The pick-list values are created in Zoho's field settings before migration, ensuring data integrity and allowing filtering in reports and dashboards.

Field Nexus work-order statuses (e.g., 'Scheduled', 'In Progress', 'Pending Parts', 'Completed') do not map to Zoho's native Deal Stage values because stage values are sales-pipeline-oriented. We create a custom pick-list field (Job_Status__c) on the Deal to preserve the full operational status history.

Field Nexus stores scheduling windows as start/end time pairs on work orders. Zoho Deals have no native scheduling window field. We create a custom text field (Scheduling_Window__c) storing the window as 'YYYY-MM-DD HH:MM – HH:MM' for reference. Team assignment from the scheduling window resolves to the Deal Owner.

Field Nexus estimates with line items, quantities, and totals have no standard Zoho CRM equivalent. We create a Zoho custom module named Estimates, add custom fields matching your estimate line-item structure (Description, Quantity, Unit_Price, Total), and relate each Estimate to its parent Deal via a Lookup field.

Field Nexus invoices and payment records do not map to any standard Zoho CRM object. We create a custom Invoices module with fields for Invoice_Number, Amount, Payment_Date, Payment_Status, and a Lookup to the originating Deal. Payment status pick-list values (Paid, Partial, Overdue) are created in Zoho before migration.

Field Nexus locations store service-site addresses (street, city, state, postal code, country) linked to a client. These migrate as the Address fields on the associated Zoho Deal (Mailing_Street, Mailing_City, Mailing_State, Mailing_Zip, Mailing_Country). The location record itself does not become a standalone Zoho object.

Field Nexus team members and technicians resolve to Zoho CRM users by email matching. A Zoho user account must exist for each active technician before migration — unmatched Field Nexus users are flagged and assigned to a fallback owner until their Zoho accounts are created.

Field Nexus timesheet entries with technician, date, hours, and task description have no Zoho CRM native equivalent. We create a custom Timesheets module with fields for Technician (lookup to User), Work_Date, Hours_Worked, Task_Description, and a Lookup to the related Deal. Labor costs map if present in Field Nexus.

Any custom fields on Field Nexus work orders, clients, or companies — such as equipment model, site condition, or priority tier — are created as custom fields in the corresponding Zoho module before migration. Custom field data types are matched (pick-list, number, date, text) to avoid import errors.