Known Limitations¶
The following limitations apply to the current version of the tool. Unsupported components are detected during the preflight scan and reported.
| Limitation | Details |
|---|---|
| Single account only | Migration operates within a single AWS account. Cross-account migration is not supported. |
| Same region required | The Pinpoint application and Amazon Connect instance must be in the same AWS region. |
| No event migration | Historical events and analytics data are not migrated. Customers may reference Pinpoint for historical metrics. |
| No push or in-app migration | Push notifications and in-app messaging are not supported in this migration path. |
| Custom channels | Custom channel integrations are not recreated. |
| Lambda custom actions | Lambda code hooks within journeys are detected, flagged, and the journey is skipped. |
| Holdout groups | Holdout groups are not supported and are not migrated. |
| No unsubscribe migration | Email unsubscribe/suppression lists are not migrated. Customers must configure unsubscribe logic in the target environment. |
| Importing existing phone numbers | Phone number import is out of scope. |
| Validating SES identities | SES identity validation remains a manual step. |
| Journey activity limit | Journeys exceeding 10 activities are flagged and skipped. The tool reports each skipped journey with the reason. |
| Complex journey patterns | Deeply nested conditionals and complex time-window conditions are detected, reported, and skipped. |
| Contact Flow action limit | Connect Contact Flows are limited to 250 actions. When a journey produces a flow exceeding this limit, the tool emits a warning. The flow is still exported but must be split manually in Connect. |
| Unresolved journey placeholders | Contact Flows with placeholder ARNs that could not be resolved from migration state require manual updates before the flow is functional. |
| Push notifications in journeys | PUSH activities in journeys are exported as Lambda invoke placeholders. A Lambda bridge to SNS or Firebase must be implemented manually. |
| Inline campaign messages | Campaigns using MessageConfiguration only (no named template) cannot have a Connect template ARN resolved automatically. |
| IMPORT-type segments |
After migration, you must upload the original customer list using the Import from CSV feature in Amazon Connect. See the Amazon Connect imported segments guide. |
| Behavior-based segment dimensions | Recency-based segment filters have no Customer Profiles equivalent and are not migrated. |
| Multi-value segment array filters | Segment attribute filters check only the first array index (_0). Endpoints with a matching value at a later index are not matched by the segment. |
| Endpoint limits | Endpoints beyond the Customer Profiles address slot limits are exported as custom attributes in S3 for customer review. Pinpoint endpoint attributes that contain lists of values are converted to separate indexed fields (for example, preferences_0, preferences_1). The original list structure is not preserved. |
| Template placeholder mapping | Some template placeholders that reference endpoint-specific attributes may require manual mapping. |
| WaitUntil (absolute time) | Wait activities using absolute time (WaitUntil) are converted to a fixed duration at export time and do not adjust at runtime. |
| Conditional helpers in templates | {{#if}} and similar helpers are not remapped. Only simple {{Path.Field}} variable substitution is processed. |
| Voice template migration | Voice templates are imported as Outbound Whisper Contact Flows, not as Q in Connect message templates. These flows are not tracked in migration state and cannot be referenced by campaign or journey imports. |
| Push template Default fallback | If a platform sub-template (for example, APNS or GCM) is not explicitly configured in the Pinpoint template, the Default fallback is applied. Platform-specific fields such as ImageUrl (Android) or MediaUrl (APNS) are not available from the Default sub-template and will not be set in the imported Q Connect template. |
| Service quotas | The tool checks quotas during preflight but does not request increases. Customers must request increases through AWS Support before retrying migration. |
| Knowledge base integration required | A Q_MESSAGE_TEMPLATES knowledge base integration must be configured on the Connect instance before template import can run. |
| No byte-for-byte equivalence | The tool does not guarantee byte-for-byte equivalence between Pinpoint and Connect resources. Semantic deltas are reported. |
| ConditionalSplit (non-event) branching | Non-event-based ConditionalSplit activities are converted to EndFlowExecution. The journey entry continues, but branching logic is not preserved. Review the export warnings for affected journeys. |
| 5 condition limit per Compare action | MultiCondition and ConditionalSplit activities with more than 5 event branches cannot be converted. The journey is skipped with a JourneyCompatibilityError. Reduce the number of branches in Pinpoint and re-export. |
Journey handling for unsupported patterns¶
Journeys are migrated as complete units. If the tool detects unsupported steps or activities within a journey, the entire journey is skipped. No partial resources are created. This prevents incomplete or broken configurations in Connect. The tool reports each skipped journey with specific details about the unsupported patterns detected.