Migrate from Field Pros to Salesforce Sales Cloud

Field Pros organizations map to Salesforce Account records. Company name becomes Account.Name. If Field Pros stores a parent-child hierarchy of customers, the hierarchy maps to Salesforce ParentId on Account. Multi-site customers require separate Account records per location unless your Salesforce setup uses the Address compound field to store multiple locations on one Account.

Field Pros contact records (site managers, dispatchers, customers) map to Salesforce Contact. The Contact requires an AccountId lookup — we resolve this by matching the contact's organization name to the Account record created from the Customer object. Unmatched contacts land as Lead records or get attached to a placeholder 'Unassigned Account' record.

Field Pros work orders do not map to any standard Salesforce object — they become a custom Work_Order__c object. The custom object stores job type, status, site address, scheduled date, completion date, and links to the Account (customer) and Contact (assigned technician or customer contact). We pre-create the Work_Order__c object and all its custom fields before migration begins.

Field Pros technicians can map to Salesforce Users if they need CRM login access, or to Contact records if they are external contractors. We match technician email addresses to Salesforce Users by email — matched technicians become User records linked to Work_Order__c via OwnerId. Unmatched technicians land as Contacts with a custom Technician__c flag for reference.

Field Pros job statuses (Scheduled, In Progress, On Hold, Completed, Cancelled) map to a custom pick-list field Status__c on Work_Order__c. Each value maps one-to-one by name. Probability and forecast-category fields on Opportunity do not apply to Work_Order__c — service status is tracked via the custom pick-list only.

Field Pros stores site address on work orders. We map this to a Site_Address__c text field on Work_Order__c for the full original address string. If Field Pros also stores a structured location record, we create a separate Site__c custom object linked to Account for multi-location customers — this preserves the N:1 relationship between sites and customers.

Field Pros file attachments on work orders download and re-upload to Salesforce Files. Files attach to the Work_Order__c record via ContentDocumentLink. Inline images in notes are rehosted in Salesforce's file storage. The 25MB per-file Salesforce limit applies — files over 25MB are flagged for manual handling before migration.

Any Field Pros custom properties that don't fit the standard Work_Order__c fields become Salesforce custom fields with the __c suffix. Type mapping: text strings become Text fields, dates become Date fields, yes/no flags become Checkbox fields, and numeric values become Number fields. Pick-list custom properties in Field Pros map to Salesforce pick-list fields with the same values.

Field Pros site visits and technician notes map to Salesforce Tasks (for discrete actions) or Events (for scheduled visits with start/end times). Original timestamps, owners, and the Work_Order__c parent link are preserved. Task WhatId points to the Work_Order__c record so activity history is visible on the work order detail page.

Field Pros user accounts map to Salesforce Users by email match. Admin users in Field Pros should be assigned Salesforce Admin profiles or permission sets before migration. We flag any Field Pros users without a matching Salesforce email so your team can decide whether to create Salesforce accounts or reassign their records to existing users.