Migrate from Fieldy to Nutshell

Fieldy customer records with name, email, phone, and address map directly to Nutshell People. Nutshell People support custom fields and are the primary contact entity. Email is the unique identifier used for deduplication. Records without an email are migrated using name as the primary key with a source-system flag.

Fieldy company records (business name, address, phone, industry) map 1:1 to Nutshell Companies. Nutshell Companies can hold multiple associated People records. If Fieldy stores multiple contacts per company, the primary contact links to the Company record and additional contacts are associated via Nutshell's contact-role relationship.

Fieldy jobs contain work description, service type, total cost, status, scheduled date, and assigned technician. These fields map to a Nutshell Deal record: job name becomes Deal name, job total cost maps to Amount, and scheduled date maps to Close Date. Job status (Scheduled, In Progress, Completed) maps to a Nutshell pipeline stage via a value-mapping table — Completed maps to Closed Won, Cancelled to Closed Lost, and open statuses map to the pipeline's active stages.

Fieldy job completion logs, technician notes, customer sign-off entries, and GPS timestamps migrate as Nutshell Notes attached to the corresponding Deal or Person. Original timestamps and the technician's name (as note author) are preserved. This gives Nutshell users visibility into the full service history without relying on a separate FSM tool.

Fieldy tasks linked to a job or customer migrate as Nutshell Activities of type 'Task'. The task description becomes the activity subject, the due date becomes the activity due date, and the assigned team member resolves to a Nutshell user by email match. Completed task status maps to Nutshell's completed-activity flag.

Fieldy team members (technicians, dispatchers) resolve to Nutshell users by email address. A team member's name and role in Fieldy are stored as a custom field on the migrated Deals and Activities so the technician assignment is preserved even if no matching Nutshell user exists. Unmatched team members are flagged and assigned to a fallback Nutshell user during migration.

Fieldy custom fields on customers (e.g., service tier, customer rating, account manager) are reproduced as Nutshell custom fields on the Person object. Nutshell's field type system (text, number, date, currency, pick-list) maps to the Fieldy field type. For pick-list fields, the exact option labels are reproduced as Nutshell pick-list values. This requires pre-creating each field in Nutshell before the migration run.

Fieldy custom fields on jobs (e.g., service type code, equipment model, warranty status) map to Nutshell custom fields on the Deal object. Each custom field must be created in Nutshell under Settings → Customize → Deals → Add Field before the migration runs. Fields are recreated with matching types and pick-list values where applicable.

Fieldy custom fields on companies (e.g., contract value tier, service region, SLA tier) migrate as Nutshell custom fields on the Company object. Each custom field is recreated with its original field type and any pick-list values preserved. The migration plan includes a field-creation checklist so Nutshell admins can pre-build the schema before data lands, ensuring all required fields exist in the destination account.

Fieldy service agreements and SLA timers have no direct Nutshell equivalent. SLA tier and contract terms migrate as text fields on the Nutshell Company record; agreement documents are stored as Note attachments. Renewal reminders must be rebuilt using Nutshell tasks or external tools.

Fieldy job attachments (photos, signed forms, equipment images) are re-uploaded as Nutshell Notes with file attachments. Large files are preserved as-is; Nutshell's file storage limits apply. The attachment is linked to the corresponding Deal or Person record so field technicians' documentation is accessible in the CRM.

If Fieldy tracks lead-level records (prospective customers without an active job), those migrate directly to Nutshell Leads. The lead name, email, phone, and source are mapped field-by-field. Nutshell Leads can be converted to People and associated with a Company or Deal, mirroring Fieldy's workflow of converting a prospect to an active customer.