Migrate from Zuper to Nutshell

Zuper Customers are individual contacts — service requesters, property occupants, or billing contacts. They migrate directly as Nutshell People. The Customer's name, email, phone, and address fields map to the corresponding Nutshell Person fields. Custom fields attached to the Zuper Customer record are recreated as Nutshell custom fields on the Person record.

Zuper Organizations represent the business entity — typically the property owner, service contract holder, or company receiving field service. They map to Nutshell Companies by name and address. Zuper's Organization-level custom fields migrate as Nutshell Company custom fields. The link between a Zuper Customer and their Organization is preserved by linking the Nutshell Person record to the Nutshell Company record.

Zuper allows a Customer to be associated with multiple Organizations. In Nutshell, each Person can be linked to one primary Company and additional secondary company relationships. We preserve the primary Organization as the primary Company link and surface additional Organization links as secondary relationships on the Person record.

Zuper Jobs are the core work-order entity. Completed jobs that represent billable work map to Nutshell Deals with the appropriate pipeline stage and close date reflecting the job completion date. In-progress jobs map as open Nutshell Deals. Zuper jobs with status 'Completed' and a resolved outcome can alternatively be logged as Nutshell Tasks for activity-history continuity.

Zuper job statuses are a pick-list that varies by Zuper configuration. We map each Zuper status label to a corresponding Nutshell pipeline stage by value: 'Quote' maps to the Nutshell stage representing unqualified or proposal stage, 'Scheduled' maps to a booked or scheduled stage, 'In Progress' maps to the active work stage, and 'Completed' maps to a closed-won or service-delivered stage. Cancelled jobs map to a closed-lost or cancelled stage in Nutshell.

Zuper Properties store service-location information — building address, floor/unit, access notes, property type — as a named entity with its own custom fields. Nutshell has no native property object. We migrate each Zuper Property as a set of custom fields on the associated Nutshell Company record (property address, property type, access instructions) so the service location data stays attached to the customer account without creating orphaned records.

Zuper Job Categories classify work by type — HVAC repair, plumbing, electrical, inspection. Nutshell has no native job-category field. We recreate Job Category as a custom pick-list field (Job_Category__c) on the Nutshell Deal so service-line reporting is preserved in Nutshell's pipeline views and exported reports.

Zuper Assets represent equipment or systems at a property — HVAC units, water heaters, appliances. Nutshell has no native asset registry. Asset name, make/model, serial number, and installation date migrate as custom fields on the Nutshell Deal associated with that service visit, keeping asset context linked to the work record.

Zuper Products and Services define the billable line items associated with a job. Nutshell Deals have no native product line-item table. We store the Zuper product or service name as a custom text field on the Nutshell Deal, and the quantity and unit price as separate custom fields, so the service scope of each deal is visible in the record.

Zuper Users with active CRM responsibilities (dispatchers, account managers) are resolved by email match to Nutshell Users and assigned as the OwnerId on migrated Deals. Zuper Users who only performed field work and don't need Nutshell access are migrated as Nutshell People records so their technician name is preserved in job history without creating an unused Nutshell license seat.

Zuper job notes migrate as Nutshell Deal notes attached to the corresponding Deal record. Zuper file attachments (photos, signed forms, inspection reports) are re-uploaded to Nutshell Files linked to the Deal. File size limits apply — Nutshell enforces standard upload limits per file. Large image files from Zuper's mobile app are resized as needed during the migration.

Zuper Workflow Builder automations — trigger/action sequences for inspection steps, quoting flows, and pricing logic — do not migrate. They use a node-based event model that has no Nutshell equivalent. We export your Zuper workflow definitions as a documented reference so your Nutshell admin can rebuild the logic in Nutshell Workflows or in an external automation tool.