Migrate from Workbooks to Nutshell

Workbooks Organisation records map to Nutshell Account. The Organisation Name, address fields (street, city, region, postcode, country), Industry, Classification, and any Organisation-level custom fields migrate directly. We resolve the Organisation as the parent record before importing any linked Person records, because Nutshell's Person-Account link requires the Account to exist at the moment of Person insert. The Organisation ID is stored as a custom field wb_org_id__c on the Nutshell Account for reconciliation and audit.

Workbooks Person records map to Nutshell Person. The Organisation-to-Account link is resolved at migration time by matching the Workbooks Organisation name to the migrated Nutshell Account, preserving the parent-child relationship. Standard Person fields (first name, last name, email, phone, job title, department) migrate directly. Role-type fields such as decision-maker or technical contact map to Nutshell Person role fields. Any Person-level custom fields migrate as typed equivalents on the Nutshell Person record.

Workbooks Opportunity records map to Nutshell Opportunity with stage, probability, and value preserved. The Organisation lookup resolves to the migrated Nutshell Account; the Person lookup resolves to the migrated Nutshell Person. Expected close date, owner assignment, and probability weight migrate directly. We configure Nutshell pipeline stages during migration so that Workbooks stage names map to the corresponding Nutshell stage values before any Opportunity records are inserted.

Workbooks Cases map to Nutshell Cases with status, priority, assigned user, related Organisation, description, and case activity history preserved. Case status values map to Nutshell Case status picklist entries. Open and resolved cases migrate with their full status history. Case custom fields migrate as typed fields on the Nutshell Case. We flag any dependent picklists that require Workbooks portal configuration before the Case custom field values can be validated against Nutshell's picklist constraints.

Workbooks Activities are a unified object with a type property distinguishing calls, emails, meetings, and tasks. We split them into Nutshell Tasks (for call and task types) and Events (for meeting types) during the transform phase. The activity date, duration, subject, description, owner, and related Organisation and Person links all migrate. Nutshell's API rate limits find operations with non-stub responses, so we apply exponential backoff and batch chunking when loading large activity sets to avoid triggering the limit that gates retrieval requests.

Workbooks Quotations are available on the Business tier and Business Pro only. The quotation header (related Organisation, owner, validity date) and line items (product, quantity, unit price, discount) are extracted. Line items map to destination quote line records or Opportunity Product records. If the Workbooks subscription is on CRM or CRM Pro tier, Quotations do not exist in the data export and are flagged as out of scope during scoping. Nutshell's native Quotes product ($67 per month on Enterprise) is the destination for quotation data if the customer holds the appropriate subscription.

Workbooks Invoices are available on the Business tier and Business Pro. Invoice header data, line items, payment status, and credit note associations migrate as structured records. We flag Invoices as requiring a manual workflow in Nutshell because Nutshell does not have a native Invoice object in its standard schema at the Foundation or Pro tiers. If the customer holds Nutshell Enterprise with the Quotes add-on, we evaluate Invoice migration as custom Note records with attached PDF documents. Workbooks PDF attachments stored against invoices are downloaded separately and attached to the corresponding destination records.

Workbooks deployments vary significantly in which custom fields exist and what they are called. There is no unified schema export listing every custom field across all record types. We request a Workbooks login with read-only access and enumerate custom fields per record type before writing the migration spec, ensuring we capture every bespoke field and do not silently drop data. iFrame fields migrate as URL strings because they store a reference, not rendered content. File upload fields require separate binary extraction. Nutshell creates custom fields during import when needed; the customer can also pre-create them in Nutshell settings before migration.