---
sourceDocument: Brazil Impact
sourceDocumentLink: https://www.servicenow.com/docs/r/impact

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Jumpstart Your Migration to ServiceNow Otto for Virtual Agent

# Jumpstart Your Migration to ServiceNow Otto for Virtual Agent {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Jumpstart Your Migration to ServiceNow Otto for Virtual Agent

This accelerator is designed to help ServiceNow Impact customers migrate from an existing NLU-based Virtual Agent to the new ServiceNow Otto for Virtual Agent.
It provides guided coaching, key resources, and best practice guides to ensure a smooth transition.
The engagement starts with an explanation of the architectural and functional differences between NLU-based and LLM-based Virtual Agents, focusing on intent recognition, topic design, and conversation handling.
It then maps existing topics to their Otto equivalents and delivers a structured migration plan for confident execution.
Show full answer Show less  

## Key Features

* **Target Audience:** Customers with a live NLU Virtual Agent instance.
* **Guided Coaching Sessions:**
  * **Session 1 (up to 1.5 hours):** Covers NLU vs. Otto architecture, NLU topic migration tool walkthrough, Otto topic structure, LLM conversational flow design, and redesign strategies.
  * **Session 2 (optional, up to 1 hour):** Q\&A session for additional migration support upon customer request.
* **Temporary Instance:** Provisioned for 30-day access to support hands-on exploration and migration activities.
* **Technical Support:** Access to a Technical Accelerator Consultant for ongoing questions and guidance.
* **Resources Provided:** Coaching session presentation deck and requested customer-specific resources.
* **Package Availability:** Available for Impact Guided, Guided+, Advanced, and Total packages.

## Customer Roles and Responsibilities

* **Platform Owner:** Oversees platform accountability, governance, and alignment with business strategy. Their involvement is required.
* **System Administrator(s):** Maintain platform stability, manage application support, and handle configuration tasks. Their participation is required.
* **Trusted Service Partners:** Recommended to attend coaching sessions to understand best practices and support ongoing migration efforts.

## Prerequisites and Considerations

* Customers must have an existing NLU Virtual Agent with live topics before engaging in this accelerator.
* ServiceNow does not implement recommendations on customer sub-production or production instances; customers are responsible for execution.
* Additional legal terms, specifications, and requirements are detailed in the Impact Accelerator Terms Matrix.

## What Customers Can Expect

By participating, customers will gain a clear understanding of the differences between NLU and Otto Virtual Agents, receive practical tools and strategies to plan their migration, and have expert support to confidently transition their conversational topics to the LLM-based Otto platform. This accelerator reduces migration complexity and accelerates adoption of the latest Virtual Agent capabilities within ServiceNow.  
This accelerator provides an overview and demonstration of migrating NLU-based Virtual Agent to ServiceNow Otto for Virtual Agent.

## Accelerator Overview {#jumpstart-migration-to-otto-for-virtual-agent__section_accelerator_overview}

Jumpstart Your Migration to ServiceNow Otto for Virtual Agent provides Impact
<var class="keyword varname">ServiceNow Otto</var> customers with guided coaching to support the migration of an existing NLU-based Virtual Agent to <var class="keyword varname">ServiceNow Otto</var> for Virtual Agent. This offering also includes key resources and leading practice guides to help customers get started.

Working in a copy of the customer's instance, this engagement begins by explaining the key architectural and functional differences between NLU-based and LLM-based Virtual Agent. It covers how intent recognition, topic design, and
conversation handling differ between the two approaches so customers have a clear foundation before any migration work begins. From there, the engagement maps existing topic coverage to <var class="keyword varname">ServiceNow Otto</var> for Virtual Agent equivalents and produces a structured migration plan that customers can confidently execute.

## Package Availability {#jumpstart-migration-to-otto-for-virtual-agent__id_hpq_ndr_jkc}

Note:  
This Accelerator is available for Impact Guided, Guided+ (SV or PG), Advanced, and Total packages.

## Prerequisites {#jumpstart-migration-to-otto-for-virtual-agent__section_prerequisites}

Customer must have an existing NLU Virtual Agent with live topics.

## What You Get {#jumpstart-migration-to-otto-for-virtual-agent__section_what_you_get}

Session Preparation

:   The Technical Accelerator Consultant:

    * Provisions a temporary instance (if applicable)
    * Activates and configures related plugins
    {#jumpstart-migration-to-otto-for-virtual-agent__ul_session_prep}

Customer Coaching Session #1 (up to 1.5 hours)

:   Includes the following:

    * Overview of NLU vs. ServiceNow Otto for Virtual Agent architecture differences
    * Walkthrough of the NLU topic Migration Tool
    * Demonstration of ServiceNow Otto for Virtual Agent topic structure and LLM-based conversational flow design
    * Leading practice and redesign strategies
    {#jumpstart-migration-to-otto-for-virtual-agent__ul_coaching_session_1}

Customer Coaching Session #2 (Optional up on Customer request -- up to 1 hour)
:   Opportunity for Q\&A related to migrating to ServiceNow Otto for Virtual Agent.

## Outputs {#jumpstart-migration-to-otto-for-virtual-agent__section_outputs}

* 30-day access to the temporary instance and Technical Accelerator Consultant with whom you met for any further questions or in-depth explorations
* Copy of the Coaching Session Deck
{#jumpstart-migration-to-otto-for-virtual-agent__ul_outputs}

## Requested Customer Resources {#jumpstart-migration-to-otto-for-virtual-agent__section_requested_customer_resources}

The same personnel may fulfill multiple responsibilities.  
{#jumpstart-migration-to-otto-for-virtual-agent__table_customer_resources__entry__4}

| Customer Resource | Responsibilities | Required | Recommended |
|:-|:-|:-:|:-:|
| Platform Owner | Responsible for the overall accountability of the ServiceNow platform. Provides leadership and oversight to the System Administrators, ensures team alignment to business strategy and the ServiceNow roadmap, and is actively involved in the overarching governance of the platform. | ✓ |   |
| System Administrator(s) | Responsible for maintaining the stability and usability of the ServiceNow platform by performing application maintenance, managing support for Cases related to ServiceNow applications, and contributing to ServiceNow software releases by delivering configuration tasks and features. | ✓ |   |
| Trusted Service Partners | Attend ServiceNow Impact Accelerator coaching session(s) to understand leading practices and potentially support the customer going forward. |   | ✓ |
[Table 1. Customer resource and responsibilities]

{#jumpstart-migration-to-otto-for-virtual-agent__table_customer_resources}

## Requested Information/Access {#jumpstart-migration-to-otto-for-virtual-agent__id_q4p_sdr_jkc}

Note:  
Additional details on supplemental legal terms, prerequisites, specifications, requirements, and exclusions can be found in the [Impact Accelerator Terms Matrix](https://www.servicenow.com/legal/servicenow-impact.html).

## Exclusions {#jumpstart-migration-to-otto-for-virtual-agent__id_kck_5dr_jkc}

ServiceNow is not responsible for implementing recommendations on Customer's sub-production or production instances.

