Understand Automation Changes in Salesforce

Learning Objectives

In this project, you'll:

Determine which automations can be migrated to flows.
Discover what prevents workflow rules from being eligible for migration.
Discover what prevents processes from being eligible for migration.

Workflow Rules or Processes or Both?

What types of declarative automations exist in your Salesforce org? Workflow Rules? Processes? Both of these older automation tools are now disabled, but that's not the only reason to migrate these automations to flows.

Why should you move to flows?

Flow Builder's new functionality makes it the main automation tool in Salesforce.
Flow Builder's configurable entry conditions allow a flow to run only when certain conditions are met, dramatically improving performance.
The Fast Field Updates option makes flows run almost 10 times faster than workflow rules and processes.
Flows are easier than workflow rules and processes to maintain, troubleshoot, and debug. Moving all automation to one tool makes it easier to find issues and create updates.
Flow Trigger Explorer helps you control the order in which record-triggered flows are triggered.

Sandbox or Scratch Org

Anytime you're working on flows, migrating, creating, updating, or debugging, be sure to build and test in a sandbox or scratch org. Because some flows affect the data in the org, never debug flows in production with live data. Always ensure that the flow is working properly in your test environment before you move it to production.

About Migrating a Workflow Rule

The Migrate to Flow tool is great for migrating workflow rules when they meet the right criteria. Here are some things to consider before you migrate workflow rules.

If a workflow rule contains only field updates on only the triggering record, the migration tool sets the optimization setting to Fast Field Updates. Fast Field Update flows run much faster than others.

Because of the different timing of how workflow rules run compared to flows, record-triggered flows can behave differently from similar workflow rules. Assign a priority value to flows using Flow Trigger Explorer to guarantee their execution order.

If the the workflow rule you're looking for isn't listed on the Migrate to Flow page, it may be due to the presence of a feature that's not supported by the migration tool, such as:

Criteria with no defined workflow actions
Global variable fields
Fields on related records
Object record types
The Does Not Contain, Includes, Excludes, or Within operator
The Greater Than, Greater Than or Equal, Less Than, or Less Than or Equal operator on a picklist field
Formulas that use HOUR, MINUTE, SECOND, TIMENOW, TIMEVALUE, ISCLONE, or $RecordType
Task workflow actions
Relative date values (such as “Last 7 Days” or “Tomorrow”) in date fields
Multiple currencies

About Migrating a Process

Migrating processes is different from migrating workflow rules in a few ways.

The Migrate to Flow tool now supports partial migration for most actions. At a minimum, you can partially migrate all actions except for invocable actions. The migration results identify which actions need further configuration in Flow Builder for your migration to be complete.

Supported	Non-supported
Processes that start when a record changes	Processes that start when a platform event message is received or when invoked by another process
Record update Record create Invoke flow Invoke Apex Email alert	Scheduled actions Field traversals

Processes with recursion (allowing the record to be evaluated up to six times during a single save operation) aren't fully supported. Migrated processes with recursion evaluate the record only one time. Test and make sure that any processes with recursion work as intended after migration.

Processes are migrated to flows with the Actions and Related Records optimization setting. You can change the optimization setting to Fast Field Updates after the process is migrated.

The invoke flow action is migrated as a subflow element, which runs in the same transaction as the parent flow.

Processes with invoke flow actions involving external callouts, external actions, or pauses should be redesigned using an asynchronous path.

Create a New Trailhead Playground

For this project, you need to create a new Trailhead Playground. Scroll to the bottom of this page, click the playground name, then click Create Playground. It typically takes 2–3 minutes to create a new Trailhead Playground.

Yes, we really mean a brand-new Trailhead playground! If you use an existing org or playground, you can run into problems completing the steps in this project.

Launch Your Trailhead Playground and Install a Package

Let's get started by opening your Trailhead Playground and installing a package. First, scroll to the bottom of this page and click Launch. If you see a tab in your org labeled Install a Package, great! Follow the steps below.

If not, from the App Launcher (), find and open Playground Starter and follow the steps.

Click the Install a Package tab.
Paste 04tDp000000hNTw into the field.
Click Install.
Select Install for Admins Only, then click Install.

When the package is finished installing, you see a confirmation page and get an email to the address associated with your playground.

Now you're ready to do some migrating!