Migrate from Sharp CRM to Nutshell

Sharp CRM Contact records map directly to Nutshell Person records. Standard fields (name, email, phone, address) migrate as typed fields on Person. The Sharp CRM contact-to-company link is preserved by creating Nutshell Company records first, then resolving the AccountId lookup at Person import time. Any contact records without an associated company land as standalone People with no Company link; these are flagged for the customer to resolve post-migration.

Sharp CRM Company records map to Nutshell Company records. The company name becomes the Name field, and domain or website data maps to the URL field. Company records are migrated first in the sequence so that the people-to-company relationship resolves cleanly. Duplicate company records (same legal name from multiple data sources) are flagged and deduplicated before import to prevent split AccountId assignments on related contacts.

Sharp CRM Deals map to Nutshell Deals with pipeline stage mapped to Nutshell's stage field. The deal value and close date transfer directly. Owner assignment resolves by matching Sharp CRM owner email to Nutshell User email. Deals without a linked contact or company at migration time land as orphan Deals and are flagged for the customer's admin to link before the CRM goes live.

Sharp CRM pipeline stages are customer-specific configurations that do not export in standard schema. We document the customer's current stage names and order during scoping, then build an explicit stage-mapping table in Nutshell before import. Nutshell's stage values are selected from a predefined list or configured per pipeline; the mapping table ensures deal records land in the correct stage rather than the default first stage.

Sharp CRM custom fields are common due to the platform's vertical market positioning (healthcare, real estate, financial services). We enumerate all custom fields during scoping by data type (text, number, date, picklist, checkbox) and create matching custom fields in Nutshell under the respective entity (Person, Company, Lead) before the import file is prepared. Nutshell's documentation explicitly requires defining custom fields before mapping import files to them to avoid hours of post-import cleanup. Any Sharp CRM custom fields without a clear Nutshell equivalent are flagged for the customer to resolve before import.

Sharp CRM Tasks migrate to Nutshell Task records with title, due date, status, and assignee preserved. Assignee mapping resolves Sharp CRM owner email to Nutshell User ID. Tasks associated with a Person or Company carry the activity link to the target entity. Open tasks are migrated with their original due dates so that the customer's team can triage them immediately after cutover.

Sharp CRM Activities (calls, emails, notes) attach to Contacts or Companies and are mapped to Nutshell Activity records by type. Email body content migrates as plain text; call duration and disposition migrate to custom fields on the Activity record. Activity timestamps are preserved so the Nutshell timeline reflects the original interaction date rather than the migration import date.

Sharp CRM Users (name, email, role) are mapped to Nutshell User accounts by email match. Active and inactive status is preserved from Sharp CRM. Nutshell seat count is re-evaluated post-migration since Sharp CRM's flat-rate model meant no per-seat tracking. Any Sharp CRM user without a matching Nutshell User goes to a reconciliation queue for the admin to provision before record import begins.

Sharp CRM tags or labels on Contacts and Deals are exported as tag arrays and mapped to Nutshell's tagging system. Tags on People attach to the Person record; tags on Deals attach to the Deal record. Tag arrays with more than 20 tags per record are flagged since Nutshell's tag display may truncate long lists.