Migrate from Fieldy to Salesforce Sales Cloud

Fieldy Customer maps to Salesforce Account as the primary company record. The primary contact within that customer record migrates as a Salesforce Contact linked via AccountId. If Fieldy stores multiple contacts per customer, additional contacts create as related Contact records with the same AccountId lookup.

Fieldy Jobs map to Salesforce Cases (standard) or a custom Work_Order__c object depending on your Salesforce configuration. Job status maps to Case Status via value mapping. Original job number preserved as Source_Job_Number__c custom field. Technician assignment maps to Case OwnerId or a custom Technician__c lookup field.

Fieldy Locations tied to a Customer map as child Site__c records linked to the parent Account via AccountId. If your Salesforce org uses Field Service Lightning, the native Location object is available. Locations without a parent Customer create under a default account or as standalone Site__c records based on your configuration plan.

Fieldy Staff members who are internal employees map to Salesforce Users by email match. Technicians stored as external contacts (non-user staff) map to Contact records linked to the relevant Account or Site. Unmatched staff flagged before migration — your team creates Salesforce Users or Contacts first.

Fieldy Quotes map to Salesforce Opportunities with line items. The Opportunity Name carries the Fieldy Quote number. Quote status maps to Opportunity Stage via value mapping. Pricebook and Products require setup in Salesforce before quote line items map — we generate the setup plan.

Fieldy Invoices map to Salesforce Orders if your org uses them, or to a custom Invoice__c object. Invoice total amount maps to Order.TotalAmount or Invoice_Amount__c. Paid status and payment date migrate as custom fields on the Order or Invoice record. Payment history requires a custom Payment_History__c object.

Fieldy forms and checklists attached to jobs have no direct Salesforce equivalent. We map them as custom fields on the Case object (Checklist_Responses__c as long-text or JSON) or as a related custom Checklist__c object linked via Lookup. Your admin decides the preferred display format.

Fieldy custom objects map 1:1 to Salesforce custom objects. Custom field types (pick-list, number, date, checkbox) map to equivalent Salesforce field types. Custom pick-list values require value-by-value mapping against Salesforce pick-list constraints. We flag any pick-list that exceeds Salesforce's 500-value limit per field.

Fieldy assets or equipment records attached to locations map to Salesforce Asset objects linked to the corresponding Account or Site record. Asset serial number, installed date, and status map directly to Asset fields. If assets are tied to specific jobs, the relationship migrates as a custom Job_Asset__c junction object.

Fieldy time entries linked to jobs map as Salesforce Tasks on the associated Case or Work_Order__c record. Technician clock-in and clock-out times map as Task ActivityDate and custom Start_Time__c / End_Time__c fields. Original timestamps preserved for payroll or billing reconciliation.

Fieldy payment records against invoices map as custom Payment__c objects linked to the Invoice or Order record. Payment method, amount, date, and transaction reference migrate as custom fields. Stripe or payment gateway references stored as text fields for reconciliation. If partial payments exist, each partial amount creates a separate Payment__c record to preserve payment history.