Migrate from Field Force Tracker to Nutshell

Field Force Tracker customers contain both individual contacts and company records. We split them: business name, domain, industry, and address map to a Nutshell Company; individual contact name, phone, and email map to a linked Nutshell Person. Multi-location customers create one primary Company record with address variants stored as custom fields.

Field Force Tracker Jobs are the core work records — they contain job type, status, description, scheduled time, assigned technician, parts used, and service notes. We map Jobs to Nutshell Deals with custom fields capturing job_type, status_reason, and service_category. Job stage history becomes custom date fields on the Deal. Uncompleted jobs map with their current status; completed jobs become closed Deals.

Field Force Tracker technicians map directly to Nutshell Users by email match. Nutshell's user model doesn't have a native 'skills' or 'certification' concept — we preserve technician skills, certifications, and service categories as custom fields on the User record. Scheduling availability data from Field Force Tracker becomes reference custom fields.

Nutshell has no native inventory object. We create a custom Inventory_Item__c object with fields for part_number, description, quantity_on_hand, reorder_level, cost, vendor, and location. Parts linked to Jobs in Field Force Tracker create junction records linking Inventory_Item__c to the corresponding Deal in Nutshell.

Field Force Tracker stores service locations with GPS coordinates, site name, address, and access instructions. We map the primary address to the Nutshell Company address field. GPS latitude/longitude, access codes, and site-specific notes become custom fields on the Company record. Multi-site customers create one Company with multiple address entries as custom fields.

Field Force Tracker service contracts define SLA terms, contract type, start/end dates, and covered services. We map these as custom fields on the related Company record (contract_type, contract_start, contract_end, sla_tier) and link contract value as a custom amount field. Contract renewal dates trigger custom reminder date fields for follow-up tasks.

Field Force Tracker generates invoices linked to jobs with line items, tax, and payment status. We map invoice totals and payment status as custom fields on the associated Nutshell Deal (invoice_total, invoice_status, payment_date). Full invoice line-item detail is preserved as a custom notes field or attached PDF. Nutshell does not have a native invoicing object.

Field Force Tracker tracks technician clock-in, clock-out, and break times with GPS stamps. Nutshell has no timesheet or attendance tracking model. We preserve clock-in/out timestamps as custom datetime fields on the related Deal or as Activity notes for reference. This data requires manual review post-migration — it cannot drive Nutshell scheduling.

Field Force Tracker job notes, status updates, technician comments, and photos attached to jobs map directly to Nutshell Activities (Tasks) linked to the corresponding Deal record. Each activity preserves the original creation timestamp and technician authorship attribution for audit continuity. Photos and file attachments migrate as Deal-level attachments in Nutshell, maintaining the complete job history context without requiring users to reference the legacy Field Force Tracker system for historical detail.

Field Force Tracker prospects without assigned jobs transfer directly to Nutshell Leads with all associated contact fields (name, email, phone, company, address) mapping one-to-one to Nutshell Lead fields. Lead status values (New, Contacted, Qualified, Unqualified) and lead source attribution transfer without transformation. The migration process runs an email deduplication pass against existing Nutshell leads — matching records update rather than duplicate, preventing data fragmentation across your unified CRM during the consolidation phase.