Migrate from Kuverto to Microsoft Dynamics 365 Sales

Kuverto agents store LLM prompts, instructions, memory settings, and tool permissions. These have no direct Dynamics 365 Sales equivalent. We extract agent definitions (name, description, model, system prompt, temperature, tool grants) and document them as configuration records stored in a Dataverse custom entity. The documented agent logic becomes the specification for rebuilding equivalent Power Automate cloud flows or Copilot Studio agents post-migration. We do not migrate agent execution history or conversation context.

Kuverto Workflows are named automation sequences with trigger conditions and sequential steps (each step = 1 AO in Workflow Mode). We capture the trigger type, step sequence, branching logic, and action types per step. The documented workflow logic is the input for Power Automate flow recreation. Dynamics 365 Sales supports business process flows natively, but Kuverto's LLM-driven workflow logic typically requires Power Automate cloud flows with AI Builder actions or Copilot Studio agents as the functional equivalent.

Kuverto maintains OAuth tokens and API credentials for connected third-party platforms. These credentials are not portable across platforms. We inventory every integration connection (platform name, authentication type, scopes granted) and produce a re-authentication checklist. Your Dynamics 365 admin re-authenticates each integration as a Power Automate connection or Dataverse connection reference. We do not transfer tokens; the destination system must re-authorize each integration from scratch.

Kuverto custom tools define API endpoint specifications, parameter schemas, and response parsing logic. We export tool definitions and map them to Power Automate custom connectors (API definition import, authentication configuration, and trigger/action schema). If the tool calls a CRM object endpoint, we map it to the equivalent Dataverse API call. Custom tools without a Power Automate connector equivalent are documented for manual API integration rebuild.

Kuverto supports team workspaces with user roles controlling who can edit agents, view logs, or manage integrations. We extract role assignments by user and map them to Dynamics 365 security roles (Salesperson, Sales Manager, System Administrator, or custom roles) and Teams. The mapping preserves permission scope for agent management where applicable, though Dynamics 365 security roles are CRM-focused and do not control Power Automate flow permissions (handled separately in the Power Platform admin center).

Pre-built Kuverto agent templates that have been customized are treated identically to custom agents in migration scope. We export the customized template definition as a configuration record in Dataverse. The template name, prompt instructions, and tool grants are preserved for reference during Power Automate or Copilot Studio rebuild. Unmodified templates (reference designs shipped with Kuverto) are not user data and are not migrated; we note which standard templates were in use.

If Kuverto integrations connect to external CRM systems and the customer uses Kuverto as a thin layer over contact data, we extract any contacts stored in Kuverto's integration layer. These map to Dynamics 365 Contact with standard field mapping (name, email, phone, address). Contact records are written to Dynamics 365 via Dataverse API or Bulk API. If no contact data exists in Kuverto beyond integration credentials, this mapping is skipped.

Similar to contacts, if Kuverto integrations maintain company or organization records as part of their connection metadata, we extract and map them to Dynamics 365 Account. Company domain, name, industry, and address fields map to the equivalent Account fields. Account is created before any Contact import so that the parent CustomerId lookup is satisfied at the moment of Contact insert.

AO consumption is Kuverto's internal billing metric and is not user-owned data. Historical AO usage records cannot be exported and have no relevance in Dynamics 365, which uses per-user licensing. We advise customers to audit current AO consumption during discovery so that they can estimate baseline Power Platform and Copilot costs on the Dynamics 365 side, but the AO history itself is not migratable.

Agent execution history and conversation logs are ephemeral operational outputs stored by Kuverto for runtime purposes. These are not configuration data and are not portable. We do not migrate them. If historical agent outputs are business-critical, we advise exporting run reports from Kuverto before the migration window and storing them externally. Dynamics 365 Sales activity logging begins at go-live.