Migrate from MobiWork to Nutshell

MobiWork Customers map to Nutshell Companies as the primary account record. Each customer also generates a Nutshell Person record for the primary contact, linked via Nutshell's 'maps' relationship. This dual-record approach ensures that all customer-level data — including address, phone, and account metadata — remains tied to the Company, while individual contact details live on the Person record for accurate sales outreach and communication tracking.

Named contact persons attached to a MobiWork Customer become Nutshell Person records. They are linked to the corresponding Company via Nutshell's account-person relationship. Each contact person's email, phone, and role are preserved on the Person record, while the Company record maintains the shared account context. This mapping handles multiple contacts per customer, with each contact receiving a distinct Person record that inherits the same parent Company relationship.

MobiWork Leads — prospective customers captured before conversion — map 1:1 to Nutshell Leads. Lead source, status, and notes transfer directly to preserve the full prospect context. Nutshell Lead status values are mapped from MobiWork's lead-stage values on a value-by-value basis, ensuring that the migration maintains the original progression logic and allows for accurate pipeline forecasting in the destination system.

MobiWork Quotes (estimates sent to customers) become Nutshell Opportunities. The quote total maps to Opportunity Amount. The quote description and line items are preserved as a custom text area on the Opportunity record. Quote status (Draft, Sent, Accepted, Declined) is mapped to Opportunity stage values.

Nutshell has no native work-order object. Each MobiWork Work Order is serialized as a structured text block stored on the corresponding Nutshell Company record as a custom field (e.g. Work_Order_History__c). Each entry captures work order number, date, status, assigned technician, and service description.

MobiWork work order statuses — including Scheduled, In Progress, Completed, Cancelled, and On Hold — are mapped to Nutshell custom pick-list values on the Work_Order_History__c field. The original status value is preserved in the text block alongside the pick-list mapping, maintaining full traceability to the source system's workflow states while enabling Nutshell-native filtering and reporting on custom field values.

MobiWork Invoices cannot be stored as native objects in Nutshell. Invoice reference numbers, totals, and payment status are preserved in a custom text area on the Nutshell Company record. For audit purposes, a Note activity is attached to the Company documenting the invoice summary.

MobiWork inventory items linked to a customer (e.g. equipment serviced, parts installed) are preserved as a custom text area on the Nutshell Company record. Each entry records part name, part number, quantity, and installation date. Full parts catalogs are stored as structured text.

MobiWork users (technicians, dispatchers, admins) are matched to Nutshell Users by email address. Only users who are assigned as record owners in MobiWork are created in Nutshell; field technicians without a CRM login are stored as a name reference in the work-order history block rather than as Nutshell Users.

MobiWork job schedules and appointments are stored as Nutshell Tasks linked to the associated Person or Company record. The task subject carries the job description, and the due date captures the scheduled date. Nutshell does not have a native scheduling board, so this mapping preserves the date reference only.

MobiWork payment records (total paid, payment method, date) are preserved as a structured text block on the Nutshell Company record. Nutshell's accounting happens outside the CRM, so payment data is stored for reference rather than as a native financial record.

MobiWork custom fields on any entity type are recreated as Nutshell custom fields on the equivalent object. Text fields become Nutshell text fields, number fields become Nutshell number fields, and dropdowns become Nutshell choice fields. Nutshell's field name format follows its own conventions.