Migrate from Field Nexus to Freshsales

Field Nexus contacts map directly to Freshsales Contacts. The email field is used for de-duplication during import. Any contact without an email is flagged and written as a separate record with a blank email rather than dropped. The primary company association maps to Freshsales Contact.AccountId — the company must exist as an Account first.

Field Nexus companies map to Freshsales Accounts. The Account Name, Website, Industry, Number of Employees, and Annual Revenue fields map directly. If Field Nexus stores a parent-company hierarchy, the parent maps to Freshsales Parent Account via the ParentId lookup. Accounts are migrated before Contacts to satisfy the AccountId foreign key requirement.

Field Nexus work orders map to Freshsales Deals because Freshsales has no native work-order object. The Deal Name becomes the work order name or work order number. Work order status, priority, service type, scheduled dates, assigned technician, estimated duration, and actual duration all become custom fields on the Deal (Work_Order_Status__c, Priority__c, Service_Type__c, Scheduled_Start__c, Assigned_Technician__c, Estimated_Duration__c, Actual_Duration__c). The primary contact on the work order becomes the Deal's Contact.

Field Nexus work order statuses (Open, Scheduled, In Progress, On Hold, Completed, Cancelled) do not map directly to Freshsales deal stages. Each must be mapped value-by-value to a Freshsales pipeline stage, and the mapping must be applied consistently across all work orders. FlitStack AI generates a status-to-stage lookup table before the migration run and applies it as a pre-write transformation.

Line items on a Field Nexus work order — product or service name, quantity, unit price, discount — map to Freshsales Deal Products if the Product Catalog is configured. Each line item becomes a Product record linked to the Deal. If no Product Catalog exists in Freshsales, line items are stored as a custom multi-value field on the Deal for reference.

Field Nexus estimates and proposals have no direct Freshsales equivalent. On Enterprise plans, estimates can become a Freshsales Custom Object linked to the Account or Deal. On Growth and Pro plans, FlitStack AI stores the estimate ID, status, total amount, and created date as custom fields on the associated Deal. Estimate line items are stored as a text or JSON custom field on the Deal.

Field Nexus users and field workers map to Freshsales Users by email match. The First Name, Last Name, and Email fields write to the Freshsales User record. Unmatched users — those without a corresponding Freshsales user — are flagged and assigned to a fallback owner; their records land in the system but the owner relationship requires manual resolution post-migration.

Scheduled appointments from Field Nexus — with start time, end time, assigned technician, and service address — map to Freshsales Events linked to the Deal or Contact. Original start and end timestamps are preserved. The Event subject carries the work order reference. Unserviced appointments (no scheduled time) are not written as Events.

Notes attached to Field Nexus records migrate as Freshsales Notes. The note body, created date, and owner are preserved. Notes are linked to the target record — Contact, Account, or Deal — using the appropriate association in Freshsales. Long-form notes with embedded formatting are migrated as plain text to avoid rendering issues.

Any custom fields on Field Nexus WorkOrder objects — service-category codes, regulatory flags, site IDs, customer PO numbers — require corresponding custom fields on Freshsales Deals. FlitStack AI inventories all Field Nexus custom fields during the audit phase and creates them in Freshsales with the appropriate field type before writing any Deal records.

File attachments on Field Nexus work orders and contacts are downloaded and re-uploaded to Freshsales Files, associated with the target record. Freshsales file size limits (25MB per file) are enforced; files exceeding the limit are flagged and must be stored externally with a link stored in Freshsales. Image attachments in notes are re-hosted and the URL is embedded in the note body.

Field Nexus routing rules, auto-assignment configurations, and dispatch automations are configuration settings, not data records. They do not export via API and cannot be transferred to Freshsales. FlitStack AI documents the current Field Nexus automation logic as a reference file that your team or a Freshsales admin can use to rebuild equivalent rules using Freshsales Workflows or territory management settings.