Migrate from Kuverto to Nutshell

Kuverto stores OAuth tokens and API keys for connected third-party platforms (Salesforce, HubSpot, Slack, Gmail, Stripe, etc.) scoped to Kuverto's environment. These credentials are not portable. We produce a full inventory of every Kuverto integration connection during scoping — including the platform name, connection type (OAuth or API key), and scopes granted — so the customer's admin can re-authenticate each integration in Nutshell post-migration. Integration re-authentication is a manual step; Nutshell supports OAuth for its native integrations (Google Workspace, Microsoft 365, Slack) and API key configuration for third-party tools.

Kuverto team workspaces with role assignments (who can edit agents, view logs, manage integrations) map to Nutshell Team Members. Nutshell does not have a granular role-permission model equivalent to Kuverto's workspace-level access control — all team members on a Nutshell account have full CRM access within their assigned permissions scope. We map Kuverto workspace roles to the nearest Nutshell team member assignments and flag any role that requires Nutshell's higher-tier admin settings.

Kuverto Custom Tools are API endpoint definitions with parameter schemas and response parsing logic. Nutshell does not have a custom tools or API connector layer — it is a standard CRM with custom fields on People, Companies, and Leads (text, long text, currency, date). We treat Kuverto Custom Tools as configuration-only assets: we export their definitions (endpoint URL, parameters, expected response structure) and document them as a reference for the customer's admin to implement in Nutshell's custom fields or in a separate integration layer (Zapier, Make, or a custom connector) if required.

Kuverto Agent Templates (pre-built agent designs that ship with the platform or are customized by the customer) represent prompt structures, tool permission sets, and LLM instruction patterns. Nutshell has no agent or AI bot layer — its automation consists of rule-based triggers (task assignment, status change, date reminder). We export the template definition as documentation and flag it as a candidate for Nutshell's automation rules or a supplemental AI tool outside the CRM.

Kuverto Agents are the primary unit — LLM prompts, instructions, memory settings, and tool permissions define their behavior. Nutshell has no agent or bot concept. We export each agent's definition (name, description, system prompt, model selection, memory window, and tool list) as a written asset. The customer's admin uses this export to design equivalent Nutshell automation rules or to provision a separate AI agent tool.

Kuverto Workflows are named automation sequences with trigger conditions and sequential steps in Workflow Mode. Nutshell Automations are rule-based triggers (when a field changes, when a date arrives, when a Deal enters a stage) with CRM actions (assign owner, create task, send email). We sequence the Kuverto workflow steps as a written workflow map — trigger, each step, branching logic, and output — and deliver it as a rebuild reference for Nutshell Automations. Workflow logic does not migrate as code.

AO consumption is Kuverto's internal billing metric and has no equivalent in Nutshell. We do not migrate historical AO usage. We include a pre-migration AO audit in discovery to flag any unused AO packs so the customer does not lose prepaid credits at cutover.

Agent execution history and conversation logs are Kuverto's operational outputs, not configuration data. They are not portable. We advise customers to export any required run reports or conversation histories from Kuverto before the migration window if they are business-critical. We do not include historical logs in the migration scope.