Migrate from SortScape to Nutshell

SortScape has no API — migration runs from CSV exports only

SortScape does not expose a REST or GraphQL API for programmatic data extraction. All migration data comes from CSV exports pulled from three separate screens: the Clients list, the Schedule export, and the Staff export. These exports are not normalized — the same contact may appear in multiple CSV files with slightly different column sets. FlitStack AI parses all three exports, deduplicates by email and name, and merges columns into a unified record set before writing to Nutshell. If a client has no email address, deduplication falls back to name-and-address matching, which requires manual review for ambiguous records. Teams should export all three CSVs before migration scoping to capture the full data picture.

Nutshell has no scheduling or job-tracking object — service context must live in custom fields

Nutshell is a sales CRM with no native scheduling, job-run, or visit-tracking capability. SortScape's job runs, visit schedules, crew assignments, and route optimization data have no direct Nutshell equivalent. FlitStack AI stores service type, visit frequency, crew size, site address, time-in, and time-out as custom fields on the Nutshell Deal and Activity records. Recurring visit patterns are stored as formatted text. Scheduling logic — including recurring visit automation — must be rebuilt using Nutshell's automation rules (Pro and Business plans) or a third-party scheduling connector. Teams relying on SortScape's drag-and-drop scheduler will need to evaluate Nutshell's calendar view or a companion scheduling tool post-migration.

Xero and QuickBooks sync records do not transfer — accounting connections must be rebuilt

SortScape's native Xero and QuickBooks Online sync links jobs and visits to invoices, payments, and expense records in those accounting platforms. Nutshell has no native accounting integration — no Xero sync, no QuickBooks connector, no invoice-tracking object. Invoice numbers and accounting references from SortScape are preserved as read-only custom fields on the Nutshell Deal, but the live sync connection breaks at migration. Teams using Xero or QuickBooks for billing must rebuild the integration using Zapier, Make, or a dedicated Xero-Nutshell connector after go-live. Failure to rebuild the sync before the next billing cycle will create gaps in your accounting records.

SortScape client records may lack email addresses, breaking Nutshell user matching

SortScape CSV exports often contain client records with phone numbers and physical addresses but no email. Nutshell's data model and API require an email for Person record creation, and owner matching for Deals requires a valid email to link to an existing Nutshell user. FlitStack AI flags records missing email during the pre-migration audit. Your team can supply missing emails from other sources (invoicing system, marketing platform) before migration. Records with no email address and no discoverable email can still migrate to Nutshell as Persons without an email value, but they cannot be assigned as Deal owners and will not receive Nutshell notifications.

Nutshell's contact-volume pricing means large passive client lists affect your monthly plan tier

Nutshell pricing scales by contact count across all People, Leads, and inactive client records — not just active sales prospects. SortScape clients who are purely service recipients with no sales engagement will count toward Nutshell's contact limit once migrated. If your SortScape database contains thousands of passive clients (past customers, inactive accounts) alongside active prospects, the migration may push you into a higher Nutshell pricing tier. FlitStack AI provides a contact-count audit before migration so your team can decide whether to migrate all historical clients or scope the migration to active and recent clients only.