Pipelines

Appearance

Supported Resources ​

Here is a list of resources that are supported by the migration tool. The tool will migrate these resources from the source Amazon Connect instance to the target Amazon Connect instance.

Table of Contents ​

Hours of Operation ​

Supported ​

Yes

Restrictions ​

None

Routing Profiles ​

Supported ​

Yes

Restrictions ​

None

Security Profiles ​

Supported ​

Yes

Restrictions ​

None

Users ​

Supported ​

Yes

Restrictions ​

None

Additional Notes ​
  1. The tool does not support the EXISTING_DIRECTORY Identity Management type. The only supported Identity Management types are SAML and CONNECT_MANAGED.
  2. When migrating from SAML to CONNECT_MANAGED, the tool will create a new user with the same username as the source user. The password will be set to a randomly generated string and the user will be required to reset it using the Forgot Password flow.
  3. When migrating from CONNECT_MANAGED to SAML, the tool will create a new user with the same username as the source user.

Quick Connects ​

Supported ​

Yes

Restrictions ​

None

Prompts ​

Supported ​

Yes

Restrictions ​

None

User Hierarchies ​

Supported ​

Yes

Restrictions ​

None

Agent Statuses ​

Supported ​

Yes

Restrictions ​

None

Lambda Associations ​

Supported ​

Yes

Restrictions ​

None

Additional Notes ​

  1. Every associated Lambda function(s) must be present in the target AWS Account and Region as the Amazon Connect instance.

Quick Responses ​

Supported ​

Yes

Restrictions ​

None

Queues ​

Supported ​

Yes

Restrictions ​
  1. If there is an Outbound Caller ID in the target Queue, it will be unchanged. If there isn't an Outbound Caller ID field, it is not populated because a phone number can only be associated to a single Amazon Connect instance. This can be resolved using a Resource Map.

Flows ​

Supported ​

Yes

Restrictions ​
  1. If a Flow contains any block having a Caller ID or Phone Number Parameter which points to a phone number associated with the instance, will not be migrated.

Flow Modules ​

Supported ​

Yes

Restrictions ​
  1. If a Flow contains any block having a Caller ID or Phone Number Parameter which points to a phone number associated with the instance, will not be migrated.

Lex Bots ​

Supported ​

Yes, with two migration methods available:

  1. CloudFormation Templates (Recommended): Generates individual CloudFormation templates for each bot, including:

    • Bot configuration
    • IAM roles and policies
    • CloudWatch log groups
    • Bot aliases and versions
    • Connect instance associations

  2. Direct API Migration: Uses AWS SDK to directly migrate bots via API calls.

Restrictions ​
  1. Only Lex v2 Bots are supported.
  2. Only the DRAFT version of the Lex Bot is migrated to the target.
  3. You must only have two Aliases in your Bot: TestBotAlias and a custom alias (e.g. Current).
Additional Notes ​

  1. CloudFormation method:

    • Creates separate templates for each bot
    • Preserves all bot configurations and associations
    • Recommended for reliable and repeatable deployments
    • Creates a single version from the DRAFT and associates it with the custom alias
    • CloudFormation method only supports creating one version at a time.

  2. API Migration method:

    • When you run the migrate command, it will create a new Version in the target Lex Bot, and assigns the custom alias to the newly created version, if you have one.

TIP

TestBotAlias always points to the DRAFT version of a Lex Bot and is intended for testing purposes and has lower quotas than a custom alias. Therefore, you should create a custom alias for production use.

Connect Case Fields ​

Supported ​

Yes

Restrictions ​

None

Connect Case Field Conditions/Rules ​

Supported ​

Yes

Restrictions ​

None

Connect Case Layouts ​

Supported ​

Yes

Restrictions ​

None

Connect Case Templates ​

Supported ​

Yes

Restrictions ​

None

Phone numbers ​

Supported ​

No Unsupported

Phone Numbers must to be manually configured in the target Amazon Connect instance because they can only be associated to a single instance at once.

Contact Lens Evaluation Forms ​

Supported ​

Yes Beta

Restrictions ​
  1. Use with caution as Tagging is not supported natively for Evaluation Forms. So we have to rely on the Title field to match the Evaluation Forms.

Contact Lens Rules ​

Supported ​

Yes Beta

Restrictions ​
  1. Use with caution as Cases and Third-party integrations are not supported.