Migrate from Sunbase Data to Nutshell

Sunbase Contact records map to Nutshell Person. Standard fields (name, email, phone, address) transfer directly. Industry-specific contact fields from Sunbase's CRM module map to custom fields on Person if the Nutshell plan supports them; Pro ($42/user/mo) and above include custom field capability. Sunbase's custom field definitions do not export, so we request a customer-provided custom field manifest during scoping to ensure values land in correctly typed destination fields. Duplicate detection uses email as the primary key.

Sunbase Lead records map directly to Nutshell Lead. Lead source, status, and owner assignment transfer as standard fields. Sunbase lead fields tied to automation workflows (such as auto-assignment triggers) are migrated as data only; the automation logic itself is non-exportable from Sunbase and must be rebuilt in Nutshell's automation layer post-migration if the customer has a Pro plan or above.

Sunbase Deals map to Nutshell Opportunities. Deal name becomes Opportunity name; deal monetary value becomes Amount; deal stage maps to a Nutshell pipeline stage. Sunbase pipeline configurations are non-exportable, so we create a new pipeline in Nutshell using stage names extracted from Sunbase during discovery. Closed-Won and Closed-Lost reasons from Sunbase custom fields map to Nutshell Opportunity loss_reason or a custom field on the Opportunity.

Sunbase Projects (installation jobs, job-site operations) have no direct Nutshell CRM equivalent. If the customer is on Nutshell Enterprise ($79/user/mo) with custom objects enabled, we create a Project custom object with metadata fields (status, budget, linked contact) as custom fields. For customers on lower Nutshell tiers, Projects are migrated as Companies with a project-identifier tag in the name and key metadata stored in the Company description or a custom field. Work Order-to-Project relationships are preserved as cross-record references in the migration manifest for manual reconnection.

Sunbase Work Orders contain permit information, task details, system specifications, and linked employee assignments. With no Nutshell equivalent, Work Order data is migrated as a Note attached to the related Company (or Project custom object if Enterprise) with the Work Order identifier in the title. Key metadata fields (permit status, task details, system specs) are stored as custom fields if available, or as formatted text in the Note body. This is a data-preservation approach, not a functional equivalent.

Nutshell does not include a native billing or invoicing object. Sunbase Invoices are migrated as Notes attached to the associated Company or Opportunity record, preserving line items, payment status, and project linkage in structured text. The customer should maintain invoice history in a dedicated accounting platform (QuickBooks, Xero, or similar) post-migration; Nutshell is not a billing system and this migration does not replicate Sunbase's financial module functionality.

Sunbase Employee records (HR data, crew assignments) that overlap with customer contacts migrate as Nutshell Person records tagged with an Employee list membership. Internal-only employees with no CRM contact counterpart are migrated as inactive Person records or held in a separate export manifest for the customer's HR system migration. GPS location history and detailed HR fields beyond contact info cannot be represented in Nutshell's CRM data model and are excluded from migration scope.

Sunbase Appointments with date, time, assigned contact, and status map to Nutshell Meeting records. We preserve the appointment date and time in Nutshell's start_time and end_time fields, set the associated Person or Lead as the Meeting attendee, and record the status. Sunbase's Google Calendar sync linkage is not transferable; the calendar connection must be re-established in Nutshell post-migration by reconnecting the Google Calendar integration in Nutshell settings.