To support the migration to Flow, Process Builder processes used by Marketing Cloud Connect are being automatically migrated to record-triggered flows. The migration to record-triggered flows occurs automatically for each Salesforce object when a journey that uses a Salesforce Data Event to access the object is stopped or published. When a Salesforce Data Entry journey is published using a Salesforce object, all journeys that depend on the same Salesforce object are migrated to record-triggered flows.
Migration is performed for each object individually. To complete the migrate for all journeys linked to a Salesforce object, you must publish a new version of a Journey associated with each Salesforce object.
Note: Should any errors occur during migration, the system will revert to using Process Builder.
When: If you’ve enabled the View All permission, the retirement is being rolled out in phases, starting after the Spring ’24 release through the end of April 2024. After Process Builder is retired in an account, the migration occurs when journeys that use a Salesforce Data Event to access the object are stopped or published.
If you haven’t enabled the View All permission, the migration starts after the Summer ’24 release. Use the new Enable System Mode Flow Activation permission. Your Salesforce org and the Marketing Cloud Engagement API versions must be V60. Marketing Cloud Engagement updates to the V60 version on August 15, 2024 or after. After the proper permissions are set, the migration occurs when journeys that use a Salesforce Data Event to access the object are stopped or published.
How: To move to record-triggered flows:
After Process Builder is retired in an account, the migration occurs when journeys that use a Salesforce Data Event to access the object are stopped or published. Customers need to move to record-triggered flows by completing these steps before Process Builder reaches end of life support on December 31, 2025.
Related information:
001664960

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.