Migrate from Jobnimbus to Nutshell

JobNimbus contacts map directly to Nutshell People. Nutshell People store name, email, phone, address, and custom fields in the Person tab. JobNimbus contact type (Lead vs Contact) is preserved as a custom field for segmentation since Nutshell separates People and Leads into distinct objects.

JobNimbus contacts with type='Lead' route to Nutshell Leads. Contacts with type='Contact' route to Nutshell People. The split is determined by JobNimbus contact type at migration time. Lead status maps to Nutshell Lead status via a value-by-value lookup.

JobNimbus companies map to Nutshell Companies. Company name, domain, address, and industry map directly. JobNimbus parent-company hierarchy maps to Nutshell's parent-company field if configured.

JobNimbus jobs are project-level records with a linked primary contact. They map to Nutshell Deals as the destination record type. Job name becomes Deal name; job amount (if set) becomes Deal value; job status maps to pipeline stage via the board-stage mapping defined for that job's parent board.

JobNimbus boards define Kanban columns (stages) for jobs. Each board becomes a Nutshell Pipeline. Board columns map to Nutshell pipeline stage names. If a JobNimbus account has multiple boards, each board gets its own Nutshell pipeline so stage logic stays scoped.

JobNimbus custom fields on contacts and jobs (Date, Decimal, Number, Text types) require custom fields to be created in Nutshell. FlitStack AI creates them on the appropriate Nutshell object tab (Person, Company, Lead, or Deal) before the data loads. Field type is preserved—Number stays Number, Text stays Text.

JobNimbus Engage text message history is imported as Nutshell Engage activities linked to the Person record. Engagement timestamps and content are preserved. Note that Nutshell Engage is a separate add-on; if it is not active in the destination account, texts are preserved as Notes for reference.

JobNimbus file attachments on contacts and jobs are downloaded and re-uploaded to Nutshell Files, linked to the corresponding Person, Company, or Deal record. File size limits apply—Nutshell handles files up to 25MB per upload.

JobNimbus users are matched to Nutshell users by email address. Unmatched owners are flagged before migration; teams either invite the user to Nutshell first or assign records to a fallback owner so no record lands without an owner.

JobNimbus automations (triggers on contact status, job stage changes, etc.) do not have a direct equivalent in Nutshell and cannot be migrated. We export the automation definitions as a JSON reference file for your team to rebuild in Nutshell's automation tools or in Zapier/Make.

JobNimbus estimates (line items, materials, pricing) have no direct Nutshell equivalent. Estimates are preserved as PDF attachments or as Note records with structured content so the data is accessible in Nutshell even if the line-item structure cannot be fully reconstructed.

JobNimbus invoices and payment records have no native Nutshell equivalent. Invoice status and totals are preserved as Note records or custom fields on the related Deal for reference. Actual invoicing must happen in QuickBooks, which Nutshell integrates with natively.

JobNimbus tasks and notes attached to contacts and jobs map to Nutshell Tasks and Notes. Original timestamps, assigned users, and parent record links are preserved. Task status maps to Nutshell task status (Open/Completed) via value mapping.