Migrate from StreetSmart to Nutshell

Field service-specific attributes have no native Nutshell equivalent

StreetSmart tracks technician assignments, service location hierarchies, and work order line items — concepts that have no direct Nutshell object or field. We handle technician assignments as custom fields on the Nutshell Person record (Technician_Role__c), service locations as Nutshell Companies with address and access notes, and work order line items as a custom text field or Note on the Deal. This approach preserves the data but requires your team to understand that Nutshell is not a field service platform — analytics built around technician utilization and job completion rates must be rebuilt outside the CRM or supplemented with a field service add-on.

StreetSmart's IgniteTech billing transition creates a hard migration deadline

All StreetSmart accounts must transition to IgniteTech billing by June 30, 2026. After that date, non-transitioned accounts may lose access to the platform. We surface this deadline prominently in the migration plan so your team can schedule discovery, field mapping, and the test migration before the cutoff. Delays in providing field mapping decisions directly compress the migration timeline — we recommend starting discovery at least 6 weeks before the deadline to allow time for custom field pre-creation in Nutshell and admin review of the value mapping tables.

Custom fields must be pre-created in Nutshell before data loads

Nutshell requires custom fields to be created in the account settings before data can be written to them via the API. For migrations with 15 or more custom fields (technician role, service category, work order priority, account type, etc.), the pre-creation step adds a planning task to the migration timeline. We deliver a custom field creation checklist as part of the migration plan, with field names, types, and pick-list options so your Nutshell admin can create them before we begin the data load. Fields not pre-created fall back to Notes, which means some structured data is less searchable after migration.

Work order stage to deal pipeline value mapping requires admin confirmation

StreetSmart work order statuses (Scheduled, In Progress, On Hold, Completed, Cancelled) do not map 1:1 to any standard Nutshell field. We build a value mapping table during the discovery phase — for example, Scheduled maps to 'Qualified', In Progress maps to 'Proposal Sent', Completed maps to 'Closed Won', and Cancelled maps to 'Closed Lost'. Your Nutshell admin must confirm this mapping before migration runs because stage values drive Nutshell pipeline reporting. If the mapping is not confirmed, we default to Nutshell's 'New' stage for all work orders, which means deal pipeline reports in Nutshell will not reflect historical work order status distribution.

Owner resolution by email match requires consistent email addresses across platforms

Nutshell resolves StreetSmart owners (technicians, account managers, dispatchers) to Nutshell users by matching the email address stored on the StreetSmart record against Nutshell user email addresses. If a StreetSmart owner has a different email in Nutshell — or does not yet have a Nutshell account — their records are assigned to a fallback owner you specify. We provide a pre-migration owner audit report listing matched owners, unmatched owners, and email discrepancies so your team can resolve gaps before migration day. Records without a resolved owner land under the fallback, which affects activity attribution in Nutshell reports.