Migrate from Kuverto to Freshsales

Kuverto agents contain LLM prompts, instructions, memory settings, and tool permissions with no direct Freshsales equivalent. We extract each agent's system prompt, model selection, temperature, and tool permission list as structured data and store it in Freshsales custom fields on the Contact object (e.g., agent_system_prompt__c, agent_model__c, agent_tools__c). For agents managing customer-facing conversations, we recommend creating a Freshsales Custom Object (via Freshworks developer platform entity storage) to represent the agent as a record type rather than a contact field extension. The mapping approach is decided during scoping based on whether agents represent internal automations (contact custom fields) or customer-facing bots (custom object records).

Kuverto workflows are named automation sequences with trigger conditions and sequential steps. Freshsales Workflows are rule-based automations triggered by CRM record events (create, update, field change). We capture the Kuverto workflow structure including trigger, step sequence, branching logic, and conditional delays, and deliver a written inventory mapping each Kuverto step to a Freshsales Workflow action (field update, task creation, email send, assignment rule). The rebuild is manual because Kuverto's step-count-based automation model does not map to Freshsales event-triggered workflow rules without admin-level redesign.

Kuverto stores OAuth tokens and API credentials for connected third-party platforms (Salesforce, HubSpot, Slack, Gmail, Stripe, etc.). These credentials are scoped to Kuverto's environment and are not portable. We inventory every connected integration during scoping and produce a re-authentication checklist that maps each Kuverto integration to its Freshsales equivalent (Freshsales has native integrations with Salesforce, HubSpot, QuickBooks, and 100+ platforms via Freshworks marketplace). The customer's admin re-authenticates each integration in Freshsales post-migration using the same OAuth flows or API key provisioning.

Kuverto custom tool definitions include API endpoint specifications, parameter schemas, and response parsing logic. We export each tool definition as structured metadata and assess whether the tool's output maps to a Freshsales contact custom field (for per-contact tool results), an account custom field (for per-company results), or a Freshsales Custom Object (for relational tool data with lookups to contacts and accounts). Custom tools requiring external API calls that Freshsales cannot invoke natively are documented as integration rebuild requirements in the handoff package.

Kuverto team workspaces with user roles controlling agent edit access, log viewing, and integration management map to Freshsales roles with profile-based permissions. We extract Kuverto role assignments and map them to Freshsales role names (Admin, Standard, etc.) with field-level security settings applied per role. Role-permission granularity differs between platforms, so we flag any Kuverto permission that does not have a direct Freshsales equivalent (e.g., Kuverto's agent memory configuration access maps to Freshsales Admin only for custom object management).

Kuverto agent templates are pre-built agent designs that users customize. We export the customized template definition using the same treatment as custom agents: system prompt, model, tools, and memory settings become Freshsales custom fields or a Custom Object record. Unmodified templates (reference designs shipped with Kuverto) are documented as template inventory for the customer's admin to assess whether equivalent templates exist in Freshsales Freddy AI or the Freshworks marketplace.

If Kuverto agents have processed or stored contact and company data as part of their tool use (e.g., contacts created via agent actions, account data pulled from integrations), we migrate this data to Freshsales Contacts and Accounts using the standard CRM object model. We resolve Kuverto's contact records by email as the dedupe key, create Accounts before Contacts to satisfy lookup dependencies, and flag any contact records with missing email addresses for manual review in the reconciliation queue.

If Kuverto agent integrations have logged email, call, meeting, or task records against contact data, we migrate these to Freshsales as Activities. Emails become EmailMessage records linked to Tasks; calls become Tasks with TaskSubtype=Call; meetings become Event records; tasks become Tasks. We resolve the parent Contact or Account reference for each activity record at migration time. Any engagement logs without a resolvable contact reference are mapped to the nearest Account or held in a manual review queue.