Import and export flows between flow designers in Connect Customer

Publisher

Amazon Web Services

URL

https://docs.aws.amazon.com/connect/latest/adminguide/contact-flow-import-export.html

Published

unknown

Updated

unknown

Accessed

2026-09-07

HTTP status

200

License

Proprietary. (c) Amazon Web Services Inc. AWS Site Terms. No license notice printed in the fetched body.; no-redistribution; short excerpts and locators only

Source notes citing this source

• A flow can be exported only if it has fewer than 200 blocks and a total size below 1MB, and the flow designer provides a block counter to track the 200-block limit. in context
• On import Amazon Connect resolves referenced resources by ARN and falls back to matching a resource of the same name when the ARN is not found; a flow with unresolved resources can be saved but cannot be published if any required parameter is unresolved. in context
• AWS documents the flow import and export feature as being in Beta status and warns that flows exported during the beta may fail to import after future releases. in context
• AWS states that support for importing legacy flows into the flow designer ends on 03/31/2026 and that legacy flows must be manually imported through the updated flow designer to convert them to the new flow language format. in context
• Amazon Connect can export a flow only if it has fewer than 200 blocks and a total size under 1 MB; AWS recommends splitting larger flows. in context
• When an Amazon Connect flow is imported into a different instance, resource ARNs no longer match, so Connect falls back to resolving resources by name; a flow with an unresolved required parameter cannot be published. in context
• AWS set 03/31/2026 as the date when importing legacy-format flows into the Amazon Connect flow designer stops being supported; flows kept offline in the old format had to be converted before then. in context
• The flow export formats documented by Amazon Connect (JSON with instance-specific ARNs) and Genesys Cloud Architect (i3 flow files) are platform-native, so a cross-vendor migration should plan to rebuild routing logic rather than import it. inferred in context

Cite this source record

APA

WarmTransfer. (2026, September 7). Import and export flows between flow designers in Connect Customer. WarmTransfer. https://warmtransfer.net/knowledge/sources/aws-connect-flow-import-export

BibTeX

@misc{warmtransfer-aws-connect-flow-import-export,
  title  = {Import and export flows between flow designers in Connect Customer},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/aws-connect-flow-import-export},
  note   = {Amazon Web Services, accessed 2026-09-07}
}