Migrate from The Service Program to Nutshell

Work orders have no native Nutshell equivalent and require activity-block mapping

The Service Program's work orders — the core operational record for service businesses — contain service type, technician assignment, parts used, labor hours, and scheduling. Nutshell has no Work Order or Service Ticket object. We map work orders to Activity records attached to the Person or Company, but this means work-order status cannot drive Nutshell pipeline stages the way it does in The Service Program. Teams that rely on work-order status for operational reporting will need to build Nutshell Activities-based reports or use a dedicated field-service integration post-migration.

QuickBooks data lives in two systems — de-duplication is required before import

The Service Program syncs customer records directly from QuickBooks. A single customer may therefore exist in The Service Program export AND in the original QuickBooks export. If both are imported into Nutshell without de-duplication, duplicate Person records will appear. We resolve duplicates by email match and phone number, keeping one record with a QuickBooks_ID__c custom field. Teams planning to maintain QuickBooks-Nutshell integration post-migration via Zapier must ensure the same de-duplication logic runs on an ongoing basis or duplicates will recur.

Route and dispatch data cannot be represented in Nutshell's data model

The Service Program's route planning, daily stop sequencing, and geolocation data for field technicians have no equivalent in Nutshell. These records — which define which technician visits which customer on which day in what order — cannot be mapped to any Nutshell object or custom field in a way that reproduces the operational workflow. We preserve route metadata (technician, customer, date) as Activity notes, but the routing logic itself must be handled by a dedicated field-service tool such as Jobber, Housecall Pro, or a custom routing solution after migration.

Nutshell contact-limit tiers require plan selection before migration finalizes

Nutshell pricing scales by contact limit (100 to 900,000 contacts) across its Foundation, Pro, Business, and Enterprise tiers. Custom fields, integrations, and email marketing availability also vary by plan. The Service Program migration scope — particularly the volume of customers, historical work orders, and equipment records — determines which Nutshell plan accommodates the migrated data. We provide a pre-migration data inventory that lists total Person and Company counts, custom field count, and file attachment volume so you can select the correct Nutshell plan before final import.

Technician accounts may exceed Nutshell seat count if field staff are included

The Service Program bills office users and field users separately, and technician records exist for every field employee. Nutshell's per-seat pricing applies to any user with a login. If your team includes 15 field technicians who do not need CRM access but are present as records in The Service Program, including them as Nutshell users adds to your monthly seat cost. We map technicians to Nutshell Users only for staff who will actively use the CRM; the rest are stored as references on Activity records.