Migrate from Field Nexus to Salesforce Sales Cloud

Field Nexus routing engine data has no Salesforce equivalent and must be rebuilt

Field Nexus stores route-optimization logic and technician dispatch rules in its routing_engine field and scheduling configuration. Salesforce has no native routing engine — territory-based assignment rules and Salesforce Scheduler handle scheduling at a basic level, but algorithmic route optimization requires a third-party integration (e.g., Badger Maps, Routific) or a custom Flow rebuilt post-migration. We export the routing_engine configuration as a JSON reference file for your Salesforce admin to use when selecting and setting up a replacement routing solution.

Multi-location customers require a custom Location__c child object to preserve all Field Nexus addresses

Field Nexus allows N locations per customer, each with its own address and geocoordinates. Salesforce Account holds a single set of BillingAddress and ShippingAddress fields — storing multiple addresses requires a Location__c custom object with an AccountId lookup. We create Location__c with Latitude__c, Longitude__c, and Address_Street__c custom fields. The primary location (marked is_primary = true in Field Nexus) populates Account.BillingAddress; secondary locations land in Location__c records. This mapping must be planned before data loads to ensure the AccountId foreign key resolves correctly.

Field Nexus API pagination limits bulk export speed for large datasets

Field Nexus REST API paginates using page and page_size query parameters or createTimestamp-based filtering. There is no published bulk export endpoint or documented daily rate cap. For migrations exceeding 50,000 records, API pagination adds overhead — we mitigate by using parallel API threads where Field Nexus rate responses permit, and by requesting the maximum page size per call. If Field Nexus throttles responses during extraction, the migration timeline extends to accommodate sequential pagination. We monitor API response times throughout extraction and flag any throttling to you before it affects the schedule.

Custom Field Nexus fields must be pre-created in Salesforce before the migration loads data

Field Nexus stores custom field metadata (field_type, field_label, required, searchable) in its API schema response for each custom object. Salesforce requires custom fields to exist with the __c suffix before data can be inserted — you cannot create and populate a custom field in the same API call. We extract the full custom field schema from Field Nexus first, generate a Salesforce field creation plan (with field type mapping: Text > Text, Number > Number, Date > Date, Picklist > Picklist), and deliver it to your Salesforce admin for pre-creation in the target org. Migration data loads in the second step. Any missing custom fields at load time cause the record to be rejected or the field to be left null.

Work order completion sign-off photos attach as Salesforce Files — large files require manual handling

Field Nexus sign-off photos and job completion images are stored as binary attachments linked to the work order. Salesforce Files have a 25MB per-file size limit. Field Nexus does not publish a maximum attachment size in its API documentation. We download all attachments during extraction, check file sizes, and re-upload files under 25MB as Salesforce Files linked to the Case via ContentDocumentLink. Files exceeding 25MB are flagged for manual transfer (stored to a shared location and re-linked post-migration). Inline images embedded in completion notes are downloaded, re-hosted, and the URLs are inserted as text references in the Resolution_Long_Text__c custom field.