Migrate from Method:Field Services to Nutshell

Method:Field Services contacts map directly to Nutshell People. All standard contact fields (name, email, phone, address) transfer as direct field mappings. Owner assignment resolves by email match against Nutshell users — unmatched owners flagged for fallback assignment before migration commits.

Method companies map to Nutshell Companies. Company name, domain/website, industry, employee count, and annual revenue transfer directly. Parent-company relationships in Method map to Nutshell's parent Company field if the hierarchical structure exists — circular references flagged during validation. Industry pick-list values are normalized where naming differs between Method and Nutshell defaults, with mismatched values logged for admin review before the final migration run.

Work Orders map to Nutshell Deals with custom fields capturing job-specific data: work order number, job type, status, priority, scheduled date, and assigned technician. The deal name defaults to the work order number plus customer name so pipeline visibility in Nutshell reflects field service activity. Line items from work orders migrate as deal product rows or notes.

Completed work orders route to Nutshell Deals marked as Won in the default sales process. Open work orders route to the appropriate open stage based on status mapping (scheduled → Prospecting, in-progress → Proposal/Price Quote, etc.). This preserves pipeline stage context for service revenue reporting.

Method estimates migrate as Nutshell Quotes attached to the corresponding Deal. Line items transfer with quantity, unit price, and description. Original estimate date and expiry date migrate as custom fields since Nutshell Quotes carry internal timestamps rather than custom date fields by default.

Technician assignment stored as a custom field (Assigned_Technician__c) on the Nutshell Deal, resolved by email match to the Nutshell user. If the technician does not yet have a Nutshell login, the name stores as text and your team assigns the user or creates the account post-migration.

Method invoices and sales receipts have no direct Nutshell equivalent since Nutshell lacks native accounting. Invoice number, amount, date, and QuickBooks invoice ID migrate as a custom field block and attached note on the related Deal. Financial reconciliation remains in QuickBooks post-migration.

Method's QuickBooks sync log — tracking last sync timestamp, sync direction, and conflict records — has no Nutshell equivalent. We preserve the most recent sync status as a custom field and attach the sync log as a Note on the Account for audit purposes, then recommend rebuilding the accounting connection natively in QuickBooks.

Method custom tables store structured data unique to each deployment. We map each custom table to a group of Nutshell custom fields on the appropriate entity (e.g., equipment tracking → custom fields on Company; job history → custom fields on Deal). N:N table relationships require junction note records since Nutshell does not support custom junction objects.

Method activities map to Nutshell Activities tied to the relevant Person or Deal. Original activity timestamp, subject, and owner transfer directly. Email body and call notes migrate as activity details. Activity type (call, email, meeting, task) maps to Nutshell's activity type field.

Method leads or contacts marked as prospects that have not yet been converted map directly to Nutshell Leads. Lead status, source, and rating transfer as direct fields. If Method uses a separate lead queue, we map that queue to Nutshell's lead status pick-list values with value-by-value mapping.