Lex v1 to Lex v2 bot migration failed

We apologize for the inconvenience you're experiencing with the migration from Amazon Lex V1 to V2. Internal server errors during migration can occur for various reasons. Some V1 features might not have direct equivalents in V2.

Let's look at the error you received as follows:

1. 'The following prompts and statements weren't migrated. Please refer to documentation for recommended approach. Hang-up phrases" -> Amazon Lex V2 does not support hang up phrases (abort statements). Configure a Lambda function and enable the dialog code hook in the fallback intent. The Lambda function can output a clarification prompt as a response and the retry value in a session attribute. If the retry value exceeds the maximum number of retries, you can output a hang up phrase and close the conversation. [1]

2. 'The following Lex features can't be migrated. Please refer to documentation for recommended approach. Bot alias' -> The migration process from V1 to V2 does not migrate certain elements automatically including aliases, Amazon Kendra indexes, AWS Lambda functions, conversation log settings, messaging channels like Slack, and tags. [2]

3. 'The following invalid response cards can't be migrated.' -> This seems to be an incomplete error message. Nevertheless, the response cards seem to be invalid and hence, can't be migrated.

Review your bot configuration for any such features that could be causing the migration to fail. If the problem persists, please reach out to AWS Support and we would be happy to take a closer look.

References:

[1] https://docs.aws.amazon.com/lex/latest/dg/message-prompts-phrases.html

[2] https://docs.aws.amazon.com/lex/latest/dg/migrate.html