> ## Documentation Index
> Fetch the complete documentation index at: https://learn.getodin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow V1 Migration Tool

> Migrate your existing Workflows V1 to Workflows V2 using the in-platform migration tool.

<Info>
  The migration tool is live as of **June 1, 2026 (v2.1.0)**. Workflows V1 will be removed on **September 7, 2026** — see the steps below to migrate.
</Info>

Workflows V1 is being deprecated in favor of [Workflows V2](/tools/workflows-v2), which introduces a redesigned visual canvas, more trigger types, improved debugging, and version history. Rather than rebuilding your workflows from scratch, the in-platform migration tool lets you migrate existing V1 workflows to V2 in place.

For background on the deprecation timeline and what's changing, see the [Workflows V1 Deprecation](/changelogs/feature-deprecations/workflows-v1-deprecation) page.

## Before You Begin

<CardGroup cols={2}>
  <Card title="Migration tool now available" icon="circle-check">
    The Migrate Flow tool is live as of June 1, 2026. You can migrate any V1 workflow today — V1 workflows continue to run normally until September 7, 2026.
  </Card>

  <Card title="Plan for downstream updates" icon="triangle-exclamation">
    After migration, any agents or integrations that call the V1 workflow will need to be updated to point to the new V2 workflow before **September 7, 2026**, when V1 is removed.
  </Card>
</CardGroup>

## How to Migrate a Workflow

<Warning>
  After migration, you must **run and verify every individual step** of the workflow in V2 — not just an end-to-end execution. Per-step verification is the only reliable way to catch subtle behavior differences between V1 and V2 (variable references, trigger payload shape, branching, retries, etc.).
</Warning>

<Steps>
  <Step title="Take inventory of your V1 workflows">
    Go to **Workflows** and list every V1 workflow that is still in use. Note down:

    * Which workflows are triggered by **agents, APIs, or external integrations** — these will need downstream updates after migration.
    * The **owner** of each workflow, so the right person validates it post-migration.
    * A **reference output** from a recent successful V1 run for each workflow — you'll compare V2 output against it later.
  </Step>

  <Step title="Open a workflow in the V1 builder">
    Navigate to **Workflows** and open the workflow you want to migrate. Make sure it is in a stable, working state — migrate published, tested flows first.
  </Step>

  <Step title="Click 'Migrate Flow'">
    In the **top-right corner** of the V1 builder, click **Migrate Flow**. This kicks off automated validation against the V2 catalog.
  </Step>

  <Step title="Review the migration summary">
    The migration modal shows a **Pass** or **Fail** status along with any errors or warnings.

    | Outcome             | What it means                                         | What to do                                    |
    | :------------------ | :---------------------------------------------------- | :-------------------------------------------- |
    | **Pass**            | All actions and configurations are compatible with V2 | Click **Continue & Import** to proceed        |
    | **Fail (warnings)** | Some actions may behave differently in V2             | Cannot self-migrate — submit a support ticket |
    | **Fail (errors)**   | Incompatible actions detected                         | Cannot self-migrate — submit a support ticket |

    <Warning>
      Workflows that fail validation cannot be self-migrated. Contact your Odin AI account manager or open a ticket through the [support portal](https://apeople.automationanywhere.com/) for assisted migration.
    </Warning>
  </Step>

  <Step title="Click 'Continue & Import'">
    This creates the V2 version of your workflow with all actions, triggers, and configuration carried over. The original V1 workflow is **not** deleted or disabled.
  </Step>

  <Step title="Run and verify every step in the V2 workflow">
    Do **not** rely on a single end-to-end run. Walk through the workflow step by step:

    1. **Open the V2 builder** and review the canvas — confirm every action, trigger, branch, loop, and connection from V1 is present.
    2. **Verify configuration on each step** — credentials, input fields, mapped variables, dropdown selections, and expression references should all match V1.
    3. **Run the workflow in test/debug mode** with a realistic input payload.
    4. **For every step, open the run details** and check:
       * Step **executed successfully** (no error, no skipped state)
       * **Input** to the step matches what V1 would have sent
       * **Output** of the step matches the V1 reference output (shape and values)
       * **Variable references** downstream resolve correctly (no `undefined`, no `{{...}}` left unrendered)
       * **Branch / loop logic** evaluates to the same path as V1
       * **Retries, timeouts, and error-handler steps** behave as expected
    5. **Re-run with edge-case inputs** (empty fields, large payloads, failure paths) and repeat the per-step check.
    6. **Log any mismatches** against the V1 reference output and fix them in the V2 builder before publishing.

    <Tip>
      Use the V2 **Executions log** to drill into each step's input/output JSON. This is the fastest way to spot variable-mapping or schema differences between V1 and V2.
    </Tip>
  </Step>

  <Step title="Publish the V2 workflow">
    Only publish once every step has been verified. Click **Publish** to make the migrated workflow live. V2 keeps full **version history**, so you can roll back to an earlier version if needed.

    <Note>
      The original V1 workflow remains accessible and can continue to run until **September 7, 2026**, when V1 is removed. You may need to update any agents or integrations that were calling the V1 workflow to point to the new V2 workflow before that date.
    </Note>
  </Step>

  <Step title="Update downstream callers">
    Before **September 7, 2026**, update anything that calls the V1 workflow to point to the new V2 workflow:

    * Agents that invoke this workflow
    * External integrations using the V1 endpoint or ID
    * Automations and scheduled jobs
  </Step>

  <Step title="Monitor the V2 workflow in production">
    For the first few production runs:

    * Watch the **Executions log** and spot-check each step's output against the V1 reference.
    * Keep the V1 workflow live (it remains accessible until **September 7, 2026**) so you can re-route traffic if a regression appears.
    * Roll back via V2 **version history** if needed.
  </Step>

  <Step title="Repeat for every remaining V1 workflow">
    Migration is **per workflow** — there is no bulk action. Work through your inventory from Step 1 until all V1 workflows are migrated, step-verified, and published.
  </Step>
</Steps>

## Validation: Pass vs. Fail

The migration tool validates your V1 workflow before migrating it. Understanding the validation outcome helps you decide next steps.

| Outcome             | What it means                                         | What to do                               |
| :------------------ | :---------------------------------------------------- | :--------------------------------------- |
| **Pass**            | All actions and configurations are compatible with V2 | Click **Continue & Import** to proceed   |
| **Fail (warnings)** | Some actions may behave differently in V2             | Cannot migrate — submit a support ticket |
| **Fail (errors)**   | Incompatible actions detected                         | Cannot migrate — submit a support ticket |

<Warning>
  Workflows that fail validation cannot be self-migrated. Contact your Odin AI account manager or open a support ticket through the [Odin AI support portal](https://apeople.automationanywhere.com/) for assisted migration.
</Warning>

## After Migration

Once a workflow is published in V2:

* The **original V1 workflow remains accessible and will continue to run** until **September 7, 2026**, when V1 is removed. Migrating does not disable or delete the V1 workflow.
* Any **agents, integrations, or automations** that called the V1 workflow endpoint will need to be reconfigured to call the new V2 workflow before September 7, 2026.
* Use the **Executions log** in V2 to monitor runs and verify the migrated workflow behaves as expected.
* V2 **version history** saves every published state, so you can roll back to an earlier version if needed.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Can I migrate all workflows at once?">
    No. Migration is triggered per workflow using the **Migrate Flow** button in the V1 interface. Each workflow must be validated and migrated individually.
  </Accordion>

  <Accordion title="What happens to the V1 workflow after I migrate?">
    The original V1 workflow remains accessible and will continue to run until **September 7, 2026**. It is not disabled or deleted after migration. On September 7, 2026, all V1 workflows will be removed and any that haven't been migrated will stop functioning.
  </Accordion>

  <Accordion title="Do I need to update integrations after migrating?">
    Yes. Agents, external integrations, or automation processes that call the V1 workflow by endpoint or ID will need to be updated to point to the new V2 workflow after migration.
  </Accordion>

  <Accordion title="What if my workflow fails validation?">
    Workflows with errors or warnings cannot be self-migrated using the tool. Submit a support ticket through the [Odin AI support portal](https://apeople.automationanywhere.com/) for assisted migration.
  </Accordion>

  <Accordion title="Will my workflow configuration be preserved?">
    The migration tool is designed to carry over your existing workflow configuration to V2. After migration, review all steps, triggers, and settings in the V2 builder and test before publishing.
  </Accordion>

  <Accordion title="What is the deadline to migrate?">
    Workflows V1 will be removed on **September 7, 2026**. The migration tool is available from June 1, 2026, giving you approximately three months to migrate. V1 workflows will continue to run during this window, but we recommend migrating as early as possible to allow time to update downstream integrations and verify behavior in V2. See the [Workflows V1 Deprecation](/changelogs/feature-deprecations/workflows-v1-deprecation) page for the full timeline.
  </Accordion>
</AccordionGroup>

## Support

For migration assistance or questions about incompatible workflows, contact your Odin AI account manager or open a support ticket through the [Odin AI support portal](https://apeople.automationanywhere.com/).

<CardGroup cols={2}>
  <Card title="Workflows V1 Deprecation" icon="triangle-exclamation" href="/changelogs/feature-deprecations/workflows-v1-deprecation">
    Full deprecation timeline, impact details, and what's changing.
  </Card>

  <Card title="Workflow Builder V2" icon="arrow-right" href="https://ai-kb.automationanywhere.com/tools/workflows-v2">
    Learn what's new in Workflows V2 and how to build with the updated canvas.
  </Card>
</CardGroup>