Migrate from HighQ to Nutshell

iSheets have no direct Nutshell equivalent — data must be flattened into custom fields

HighQ iSheets are custom database tables with user-defined column schemas and row-level data that can span multiple related entities. Nutshell has only custom fields on People and Companies — no standalone table or custom object structure. We map each iSheet to a target Nutshell object, creating a custom field per column. Multi-column iSheets with complex inter-row relationships require a custom mapping plan before migration; rows referencing multiple entities may need to be split into multiple custom field sets or associated via a custom junction field. iSheets with more than 30 columns push the mapping complexity significantly higher.

HighQ workflow rules cannot migrate — export is the only path

HighQ's workflow engine stores rules as a configuration of triggers, conditions, and multi-step actions tied to Sites, Files, Tasks, and iSheet events. Nutshell has no equivalent cross-object automation engine — its automation is limited to personal email sequences triggered by pipeline stage changes. FlitStack exports your HighQ workflow definitions as JSON including trigger events, condition trees, and action sequences. Your Nutshell admin uses this export as a rebuild reference; equivalent logic must be implemented in Nutshell's automation tool or an external workflow service. This is disclosed upfront so there are no surprises about what does not transfer.

HighQ Sites map to Nutshell Companies but lose site-level permission structure

Each HighQ Site has its own permission set controlling which internal and external users can access which Files, Tasks, and iSheets. Nutshell Companies have no native permission or access-control structure — all CRM users with access to the account can view all People and Companies by default. Site-level access restrictions do not map to any Nutshell construct. We document the permission matrix as a custom field set on the Company record (Site_Permissions__c) for reference, but enforcement must be handled via Nutshell user roles and sharing rules after migration.

HighQ client portal users have no Nutshell equivalent

HighQ's extranet and client portal features allow external stakeholders (clients, opposing counsel, lenders) to access specific Sites, Files, and iSheets without full internal user licenses. Nutshell has no external portal, client-facing workspace, or granular external access model. External users migrate as Nutshell People records tagged with External_User__c, but they cannot log in to Nutshell without a standard paid user seat. Client-facing collaboration must be rebuilt using a separate portal tool or by sharing Nutshell records manually.

HighQ file version history does not transfer — latest version migrates only

HighQ tracks file version history with timestamps and version numbers for every uploaded document. Nutshell's attachment model stores only the current file version with a single upload timestamp. We migrate the latest file version per document and preserve version metadata (original filename, version count, last modified date) as custom fields on the attachment record. If version history must be preserved for compliance or litigation purposes, it must be stored separately and linked by reference.