Migrate from Kuverto to Salesforce Sales Cloud

Kuverto agents may have queried or created Contact records in connected platforms during workflow execution. We extract any Contact records stored in Kuverto's integration connections and migrate them to Salesforce Contact. The mapping preserves Name, Email, Phone, Title, and any custom properties as Salesforce custom fields. Contact is inserted after Account because Contact requires AccountId as a foreign key.

Kuverto workflows that interact with CRM integrations may have created or updated Company records. We extract Company records and map them to Salesforce Account. The company domain becomes the Account Website field and is used as the dedupe key during import. Account is inserted before Contact so that the AccountId lookup is satisfied at Contact insert time.

If Kuverto agents have created Deal records in connected CRM integrations, we extract them and map to Salesforce Opportunity. Deal properties (amount, close date, stage) map to Amount, CloseDate, and StageName respectively. The destination Salesforce org must have the relevant Sales Process and Record Type configured before Opportunity insert.

Kuverto agents are the core migration asset that has no direct Salesforce CRM equivalent. We extract every agent definition — including name, description, LLM model, system prompt, memory settings, and tool permissions — and produce a structured inventory document. This document serves as the specification for rebuilding agents in Salesforce using Agentforce, Einstein Copilot, or Flow-based automation. Agents are documented in dependency order if one agent calls another.

Kuverto Workflows are named automation sequences with trigger conditions and sequential steps. We extract the full step list, branching logic, delay actions, and CRM action types (create record, update field, send email) for every active workflow. The output is a step-by-step rebuild guide mapped to Salesforce Flow equivalents. We do not migrate Workflows as Flow code because the execution models differ fundamentally — Kuverto Workflows execute within agent contexts, while Salesforce Flow executes on CRM record events.

Kuverto stores OAuth tokens and API keys for every connected platform. These credentials are scoped to Kuverto's environment and cannot transfer to Salesforce. We inventory every integration connection during scoping and produce a re-authentication checklist specifying which Connected App or Named Credential to create in Salesforce for each integration. The customer's admin completes re-authentication before cutover.

Kuverto custom tools define API endpoint specifications, parameter schemas, and response parsing logic that agents call. We export tool definitions as OpenAPI-style specifications. In Salesforce, these map to either Apex REST classes, Named Credentials with external service registration, or MuleSoft Composer flows. The mapping is case-by-case depending on the tool's complexity and the destination Salesforce edition.

Kuverto workspace roles (Admin, Editor, Viewer) that control agent editing, log access, and integration management map to Salesforce Profiles and Permission Sets. We extract the role assignment matrix and produce a permission specification document that the Salesforce admin uses to configure Profiles (object-level access) and Permission Sets (field-level and feature access) in Setup.

Kuverto agent templates are reference designs shipped with the platform or customized by the customer. Customers who have customized templates receive the same inventory treatment as custom agents. We export the customized template as a named agent definition in the inventory document with a note that it originated from a platform template.

If Kuverto agents have logged engagement records (call logs, email sent/received, meeting outcomes) into connected CRM integrations, we extract them and migrate to Salesforce Task (TaskSubtype=Call for calls), Event (for meetings), and EmailMessage (for emails). Activity timestamps are preserved as ActivityDate on Task and StartDateTime on Event. Parent-record lookup (WhoId, WhatId) is resolved at migration time.

Agent Operation consumption is Kuverto's internal billing metric, not user-owned data. Historical AO usage cannot be exported and is not relevant to Salesforce. We capture current AO consumption during scoping as a baseline for the customer to estimate their equivalent Salesforce Flow or Agentforce cost post-migration, but no AO data migrates to Salesforce.

Agent conversation logs and execution history are Kuverto's operational outputs stored for debugging and audit purposes. They are not configuration data and are not portable. We advise customers to export any required run reports from Kuverto before the migration window if historical agent output is business-critical. Salesforce does not have an equivalent conversation log object; this data is not migrated.