What's happening?
Customers encounter difficulties when migrating static segments, marketing forms, and journeys from outbound marketing to real-time marketing. Specifically, customers experience issues with:
- Migrating static segments to real-time marketing.
- Migrating existing outbound marketing forms (including embedded forms) to real-time marketing.
- Publishing journeys after migrating them between environments.
Reason:
- Outbound marketing forms and real-time journey forms are fundamentally different and cannot be automatically transitioned or edited interchangeably.
- Migrating journeys and related records separately between environments is not a recommended practice and can lead to publishing issues.
Resolution:
Migrating Marketing Forms:
- Outbound marketing forms cannot be automatically transitioned to real-time journey forms due to underlying conceptual differences.
- Forms must be rebuilt from scratch in real-time marketing.
Real-time journey forms offer the following advantages:
- No need to manually create form fields; all entity attributes, including custom attributes, are readily available.
- No need to create a separate form page for embedding; embed code snippets can be generated directly.
- Published real-time journey forms are hosted on the Content Delivery Network (CDN), significantly reducing loading times.
For detailed guidance, refer to the official Microsoft documentation: Transition marketing pages and forms - Dynamics 365 Customer Insights | Microsoft Learn
Migrating Journeys Between Environments:
- Journeys and related records should not be migrated separately between environments, as this is not a best practice and can cause publishing issues.
- Follow the recommended steps provided in the official documentation for transferring data and configurations between environments: Transfer data and configurations between environments using the Configuration Migration tool - Dynamics 365 Customer Insights | Microsoft.