Migrate from Bluetrait to Nutshell

Bluetrait Company records map directly to Nutshell Company. The company name, domain, address, phone, and custom fields transfer as-is. We use company name as the dedupe key during import. If the source account uses the Bluetrait CRM module with separate Client records linked to Companies, we preserve the Client-to-Company relationship as a custom Company field in Nutshell rather than creating duplicate records.

Bluetrait Client records (the CRM layer representing individual contacts within a company) map to Nutshell Person. The Client's email, phone, role, and any custom fields transfer to Nutshell's Person object. We link each Person to its parent Company record using Nutshell's Company lookup. If the source Bluetrait account uses Client records as the primary contact representation without a separate Company record, we create a placeholder Nutshell Company using the Client's domain or organization name.

Bluetrait's CRM module Customers and Leads map to Nutshell Person records. Lead status, lifecycle stage, and custom CRM fields migrate to Nutshell custom fields on Person. If the customer uses both the MSP Companies module and the CRM Customers module in Bluetrait, we deduplicate by email during scoping to avoid creating duplicate Person records in Nutshell.

Bluetrait Tickets map to Nutshell Tasks. Ticket status (open, pending, resolved, closed) maps to Task status (open, waiting, completed). Ticket priority maps to Nutshell's priority field. Internal notes and comments migrate as Task notes. We note that Nutshell does not have a separate Ticket object; the customer's team must adopt the Task model for issue tracking in Nutshell or connect a dedicated helpdesk integration post-migration.

Bluetrait Timesheet entries have no direct Nutshell equivalent because Nutshell does not have a native timesheet object. We migrate timesheet data (date, hours, user, task/project link, timesheet type) as Nutshell Tasks with custom fields for hours_logged, timesheet_type, and project_reference. The customer selects whether to create one Task per timesheet entry or roll up entries by day or project during scoping. Auto-billing from timesheets does not migrate and must be reconfigured manually in the destination billing tool.

Bluetrait Projects (with linked tasks, budgets, and project statuses) map to a Nutshell Task grouping structure using custom fields for project_name, budget_amount, and project_status. We do not migrate project-level budget tracking as native Nutshell fields; these become custom fields on the parent Task record. If the project management complexity is high, we recommend a dedicated project management tool post-migration.

Bluetrait Invoices and Quotes migrate as static record inventories: line items, taxes, payment status, and invoice totals transfer to a reference document for manual re-entry in the customer's chosen billing tool. Nutshell does not have a native invoicing or billing module; Quotes are available for proposals but require manual creation or an integration with a billing platform like QuickBooks, Xero, or Stripe. Recurring billing automation from Bluetrait does not export and must be reconfigured in the destination billing system.

Bluetrait Products (with SKU, pricing, and recurring billing frequency) map to Nutshell Product records. We transfer product name, SKU, unit price, and recurring frequency as custom fields in Nutshell since Nutshell's product model is simpler. Subscription cadence requires manual re-setup in Nutshell or a connected billing platform.

Bluetrait Users map to Nutshell Users. We resolve by email match. Any Bluetrait User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. 2FA status and password data do not transfer; users must authenticate via the customer's chosen identity provider (G Suite, Microsoft 365, or Nutshell-native) post-migration.