Migrate from Method:Field Services to Salesforce Sales Cloud

Method Contacts map directly to Salesforce Contacts. Salesforce requires AccountId on Contacts — Method contacts without a primary company link are attached to a default 'Unassigned Account' record or flagged for manual resolution before migration. The email field serves as the unique identifier for matching existing Salesforce Contacts during delta runs. Phone and address fields transfer with direct field-to-field mapping using the standard contact object schema in Salesforce.

Method Contacts that represent prospective customers (Work Order status = 'Lead' or no closed work order) route to Salesforce Lead. Active or historical customers route to Salesforce Contact. The split logic applies the Work Order status value as the routing key. We evaluate the entire Work Order history for each Contact to determine whether the Contact has ever completed a service engagement before assigning them to the Lead object versus the Contact object.

Method Companies map to Salesforce Accounts. Method's parent/child company hierarchy maps to Salesforce Parent Account ID. Multi-company contacts collapse to one primary AccountId with the rest surfaced as Account Contact Relations. Address information from Method Companies transfers to the Account billing and shipping address fields. Industry classification, employee count, and annual revenue map to their corresponding Salesforce Account fields.

Work Orders are the core entity in Method:Field Services. Each Work Order maps to a Salesforce Case. Method's Work Order status values (e.g., 'Scheduled', 'In Progress', 'Completed') map to Salesforce Case Status pick-list values — a value-by-value mapping is required per your specific status list. Work Order priority and type fields also map to corresponding Case pick-list fields using the same value-mapping approach to ensure consistency across the migration.

Work Order appointment windows (scheduled start and end) map to Salesforce Events with the Case as the parent record. Discrete task-level items within a Work Order (e.g., checklist items) map to Salesforce Tasks linked to the Case. The Work Order number is preserved as a custom field on the Case for cross-reference between the legacy Method system and the new Salesforce environment.

Method Work Orders carry job-type fields (e.g., service category, priority, technician assignment) that do not map to standard Salesforce Case fields. These migrate as custom fields on the Case object (e.g., Service_Type__c, Technician_Assignment__c, Job_Priority__c) — created in Salesforce before migration runs. The custom field data type must match the Method source field type to avoid validation errors during record insertion.

Method Estimates carry line-item detail and totals that map to Salesforce Opportunity with Product line items. Estimate status ('Draft', 'Sent', 'Accepted') maps to Opportunity Stage values — we deliver a value-mapping plan per your estimate status configuration before migration. The Estimate total amount becomes the Opportunity Amount field, and the customer contact links to the Opportunity AccountId through a lookup relationship.

Estimate line items map to Salesforce OpportunityLineItem records linked to the parent Opportunity. Unit price, quantity, and description fields carry over. Salesforce requires the parent Opportunity to exist first — this object is migrated after Opportunity creation. The Product2 lookup on OpportunityLineItem requires matching by product name or SKU, so we create Product2 records for any unmatched products during the migration.

Method custom tables created via Tables/Fields editor map 1:1 to Salesforce custom objects. Each custom table field maps to a Salesforce custom field with __c suffix on the new object. Custom table relationships (parent/child) map to Salesforce lookup or master-detail fields. The Salesforce custom object must be created using the Metadata API or manually in Setup before we can insert any records.

Method invoices generated from Work Orders map to Salesforce Orders. Order status is derived from the Method invoice payment status. Original QuickBooks invoice reference is preserved in a custom field (QB_Invoice_Ref__c) since Salesforce has no native accounting link. Order line items correspond to the original Work Order line items, and the Order is linked to the Account that owns the original Work Order in Method.

Files attached to Work Orders, Estimates, or Contacts are re-uploaded to Salesforce Files (ContentDocument). File size limits (Salesforce default 25MB per file) apply; files exceeding the limit are flagged for manual handling. The ContentDocumentLink associates each file with its parent record (Case, Opportunity, or Contact) using the LinkedEntityId field. Original file names and content are preserved during the upload process.

Method user records resolve to Salesforce Users by email match. Dispatcher and Field Crew role assignments in Method have no direct Salesforce equivalent — your admin creates profiles or permission sets to replicate role scoping post-migration. The original Method user role is stored in a custom field (Method_Role__c) on the Salesforce User record for reference during the profile configuration phase.