Migrate from Shark Byte CRM to Nutshell

Shark Byte Customer records represent the end-client organization or homeowner and contain both company-level fields (name, address, service history) and individual contact details (name, phone, email, role). We split these into Nutshell Company records (for organizational-level customers) and Person records (for individual contacts at each customer site). The primary Customer identifier and service history attach to the Company as custom fields. Role information from the source becomes a custom Person field in Nutshell.

Shark Byte Contact records map directly to Nutshell Person records. Name, phone, email, and role fields migrate 1:1. Any custom fields on the Contact record migrate to Nutshell custom Person fields. The Person record is linked to the parent Company record via Nutshell's company-person relationship at migration time using a dedupe key of email address.

Shark Byte Estimates are the core product object and include line items, labor rates, material costs, and the contract-term classification (1-3 year, 3-5 year, 10+ year). We map Estimates to Nutshell Opportunities with the total estimated value as the Opportunity amount. Contract-term classification migrates as a custom picklist field on the Opportunity. Individual line items are stored as a JSON blob in a custom text area field for reference, since Nutshell's native Opportunity does not include a line-item sub-object. If Nutshell Quotes is active on the destination account, we can map Estimate line items to Quote Line Items instead.

Shark Byte Proposals are generated from Estimates and include pricing, scope, and terms. We map Proposal records to the related Nutshell Opportunity and preserve the proposal document as a file attachment on the Opportunity record. The proposal status (draft, sent, accepted, rejected) migrates as a custom Opportunity field. If the original Proposal PDF is available from Shark Byte exports, we import it as a Nutshell attachment on the linked Opportunity.

Shark Byte Service Agreements are recurring maintenance contracts tied to specific contract-term buckets (1-3, 3-5, 10+ years). We map these to Nutshell Opportunities with a custom Service Agreement flag set to true, contract start and end dates as custom date fields, and term length as a custom picklist field matching the source classification. Annual or recurring value migrates to the Opportunity amount field with a custom recurring flag indicating the payment model.

Shark Byte Work Orders track individual jobs dispatched to technicians with status, assigned technician, and line items. We map Work Orders to Nutshell Task records with status mapped to Nutshell's Task status values. The assigned technician resolves to the Nutshell User record by email match. Work Order line items and equipment specifications migrate as custom Task fields. Any linked photos from mobile surveys migrate as file attachments on the Task.

Shark Byte CRM attachments (scope documents, mobile survey photos, signed agreements) on Customer, Estimate, Proposal, and Work Order records migrate to Nutshell file attachments on the corresponding destination record. We extract all available attachments at original resolution where possible. Some images from older mobile surveys may be compressed in the source; we note any resolution gaps during extraction. The parent record type is preserved during migration so attachments land on the correct Nutshell entity (Company, Person, or Task).

Shark Byte custom fields on Estimates (equipment specifications, contract classification codes, regional pricing modifiers) require pre-creation in Nutshell before migration. We define the custom Opportunity fields with matching types during the schema design phase, including picklists, date fields, and text fields. The custom field names in Nutshell mirror the Shark Byte field labels for admin recognition after cutover.

Shark Byte custom fields on Service Agreements (coverage tier, auto-renewal flags, escalation clauses) migrate to Nutshell custom Opportunity fields. We create these as a separate field group during schema design so they are visually grouped on the Opportunity layout alongside the standard contract-term fields.