---
title: "POST /migrations"
method: POST
path: "/migrations"
---

# POST /migrations

`POST /migrations`

Starts migrating a bot from Amazon Lex V1 to Amazon Lex V2. Migrate your bot when you want to take advantage of the new features of Amazon Lex V2.

For more information, see [Migrating a bot](https://docs.aws.amazon.com/lex/latest/dg/migrate.html) in the _Amazon Lex developer guide_.

## Request body

- object
  - `v1BotName` string, required — The name of the Amazon Lex V1 bot that you are migrating to Amazon Lex V2.
  - `v1BotVersion` string, required — The version of the bot to migrate to Amazon Lex V2. You can migrate the <code>$LATEST</code> version as well as any numbered version.
  - `v2BotName` string, required — <p>The name of the Amazon Lex V2 bot that you are migrating the Amazon Lex V1 bot to. </p> <ul> <li> <p>If the Amazon Lex V2 bot doesn't exist, you must use the <code>CREATE_NEW</code> migration strategy.</p> </li> <li> <p>If the Amazon Lex V2 bot exists, you must use the <code>UPDATE_EXISTING</code> migration strategy to change the contents of the Amazon Lex V2 bot.</p> </li> </ul>
  - `v2BotRole` string, required — The IAM role that Amazon Lex uses to run the Amazon Lex V2 bot.
  - `migrationStrategy` 'CREATE_NEW' | 'UPDATE_EXISTING', required — <p>The strategy used to conduct the migration.</p> <ul> <li> <p> <code>CREATE_NEW</code> - Creates a new Amazon Lex V2 bot and migrates the Amazon Lex V1 bot to the new bot.</p> </li> <li> <p> <code>UPDATE_EXISTING</code> - Overwrites the existing Amazon Lex V2 bot metadata and the locale being migrated. It doesn't change any other locales in the Amazon Lex V2 bot. If the locale doesn't exist, a new locale is created in the Amazon Lex V2 bot.</p> </li> </ul>

## Response `202`

Success

- StartMigrationResponse
  - `v1BotName` string — The name of the Amazon Lex V1 bot that you are migrating to Amazon Lex V2.
  - `v1BotVersion` string — The version of the bot to migrate to Amazon Lex V2.
  - `v1BotLocale` 'de-DE' | 'en-AU' | 'en-GB' | 'en-IN' | 'en-US' | 'es-419' | 'es-ES' | 'es-US' | 'fr-FR' | 'fr-CA' | 'it-IT' | 'ja-JP' | 'ko-KR' — The locale used for the Amazon Lex V1 bot.
  - `v2BotId` string — The unique identifier for the Amazon Lex V2 bot.
  - `v2BotRole` string — The IAM role that Amazon Lex uses to run the Amazon Lex V2 bot.
  - `migrationId` string — The unique identifier that Amazon Lex assigned to the migration.
  - `migrationStrategy` 'CREATE_NEW' | 'UPDATE_EXISTING' — The strategy used to conduct the migration.
  - `migrationTimestamp` string, date-time — The date and time that the migration started.

## Other responses

- `480` — LimitExceededException
- `481` — InternalFailureException
- `482` — BadRequestException
- `483` — AccessDeniedException
- `484` — NotFoundException

---

[API](https://skmtc.net/aws/apis/lex-models.md) · [All operations](https://skmtc.net/aws/apis/lex-models/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/lex-models/versions/7b110b0aa60e/schema)