Migrate from Method:Field Services to Freshsales

Method contacts map directly to Freshsales Contacts using 1:1 field mapping. Address fields, email address, phone number, and owner assignment transfer directly without transformation. QuickBooks-linked customer IDs migrate as a custom field called QB_Customer_ID__c on the Contact record for reference and audit continuity. Created dates are preserved via the Original_Create_Date__c custom field since Freshsales sets its own created timestamp at migration time.

Method property records — which store customer site address, service location, and property-type metadata — map to Freshsales Accounts. These Account records capture the physical service location, property classification, and associated site details. Multiple contacts per property supported in Method collapse to one primary Account with additional contacts linked via Freshsales Account-Contact relationships. We identify the primary contact based on most recent activity or modification date.

Method Work Orders have no direct Freshsales equivalent and must be transformed into Deals. They map to Freshsales Deals with a Work_Order_ID__c custom field for traceability, Work_Order_Status__c (value-mapping from Method status to Freshsales deal stage), and Service_Type__c custom fields capturing field-service specifics like repair, installation, or maintenance. The original Work Order description, priority level, and scheduled date transfer as additional custom fields on the Deal.

Method Work Order statuses (Scheduled, In Progress, Completed, Cancelled) map value-by-value to Freshsales Deal Stage pick-list values. Each status gets assigned to a corresponding pipeline stage during migration setup. We apply your target pipeline stage order and probability percentages at migration time. Any unmapped or non-standard Method statuses route to a default stage that you designate, ensuring no Work Orders are lost during the transition.

Method Estimates transform into Freshsales Deals with Estimate_Reference__c custom field storing the original estimate identifier and a custom field capturing the original estimate amount. Estimate line items map to Deal Products, linking each service line to the Product Catalog when matching products exist. If the Estimate status shows as Accepted in Method at migration time, the corresponding Deal stage is set to Closed Won automatically.

Method Work Order line items including service description, quantity, and rate per unit map directly to Freshsales Deal Products. Each line item attaches to the parent Deal representing the Work Order. Product lookup in Freshsales ties the line item to the Product Catalog if a matching product record exists, otherwise the line item stores the service description without catalog linkage.

Method's product and service item records map to Freshsales Products using direct field mapping. Unit price, SKU code, and product description transfer directly without transformation. QB_Product_ID__c custom field preserves the QuickBooks item reference on each Product record for audit continuity and future QuickBooks reconciliation if needed. Inventory tracking fields map to Freshsales stock quantity where applicable.

Freshsales has no native invoicing object, so Method Invoices synced from QuickBooks migrate as a Freshsales Custom Module called Invoice_Reference. This module includes fields for invoice number, invoice amount, payment status, and QB_Invoice_ID__c linking back to QuickBooks. The module preserves invoice history for audit purposes but does not enable invoice generation within Freshsales. Ongoing invoicing must continue in QuickBooks or be managed through Freshsales Product Catalog with manual billing processes post-migration.

Method technicians who are active CRM users map to Freshsales Users by email address matching. Non-user technicians who work primarily in the mobile Field Crew app map to Contacts with a Technician__c checkbox custom field set to true, distinguishing them from regular business contacts. Owner_Phone__c custom field preserves field crew mobile contact details on the Contact record for dispatch reference.

Method's custom tables and extensible data capture structures map to Freshsales Custom Modules on Pro and Enterprise plans. Each Method custom table becomes one Custom Module with fields created to match Method's original schema field-for-field. N:N relationships between custom tables require Freshsales lookup fields and junction objects to preserve the many-to-many connections. Your admin reviews the relationship mapping before migration to confirm the structure meets your data integrity requirements.

Files attached to Work Orders, Estimates, or Contacts migrate as Freshsales attachments on the corresponding Deal or Contact record. All file metadata including filename, file type, and upload date transfer with the attachment. File size limits apply per Freshsales constraints — files exceeding 25MB are flagged during migration for manual re-upload after migration completes using Freshsales file upload tools.

Any QuickBooks IDs stored as custom fields in Method including QB_Customer_ID, QB_Invoice_ID, and QB_Product_ID migrate as text custom fields on the target Freshsales object with the same __c naming convention. These reference fields serve audit and reconciliation purposes only — they preserve the link between migrated records and their QuickBooks source but do not create live QuickBooks API connections or synchronization within Freshsales.