Migrate to Flow Best Practices

It finally happened: Winter 23 is here. You cannot create new workflow rules (WFRs) anymore.

Migrate to flow functionality is GA (Generally Available).🔥 Before I get into the details of this topic, let me tell you that all my courses are on a huge sale. Check below. 🔥What do you do now? Use this, and a couple of clicks later, your Org will be all on flow? Not so fast.

Let’s review the facts here.

Workflow rules support:

  • 🔁 Field Updates
  • 📧 Email Alerts
  • ☑️ Task Creation
  • 🕊 Outbound Messages

You can do all these things with flow.

First, review all the WFRs you have in our Org. Main parameters to look at (make a table out of this): 💡

  • Object (Opportunity)
  • Trigger (On Create)
  • Criteria (When Close Date <= Today + 30)
  • Action (Email Alert)

Why can’t you just use migrate-to-flow and migrate everything? The limitations are: 😰

  • Does not support tasks
  • Does not support long text fields in the criteria
  • Does not support cross-object reference in the criteria
  • Migrates one WFR to one Flow
  • Does not facilitate renaming/relabeling the flow (same name – renaming manual)

There are several approach alternatives you need to consider:

1️⃣ Custom Development: Analyze and design & build everything

2️⃣ Use migrate to flow when it works: One-to-one migration

3️⃣ Try to create one flow for most WFRs: Major work & Maintenance nightmare

4️⃣ Hybrid: Design your own strategy combining the methods above

I looked at all these factors and come up with a set of recommendations. I reviewed the recommendations in a Salesforce Saturday meeting with the awesome Salesforce ecosystem friends this past weekend. Here is a few of them:

  • Use migrate to flow for Email Alerts. Rename flows to follow a convention. One-to-one migration. Exception: Long text field reference in criteria (LongText is not blank)
  • Fast field updates should be combined in before-save flows. If you have too many variations of workflow criteria, do not force everything into one flow. Come up with logical divisions and split them into multiple naming the flows accordingly.
  • Tasks should be combined in after-save flows. On objects where there is an after-save flow already, the field updates can be included in one after-save flow.
  • When combining many WFRs with various different criteria into one flow, decisions get overly complicated. No access to a formula builder. Split if needed.

Please check the presentation pdf at this link for more information.🔥 All my courses are on a huge sale: ðŸ”¥

  • My bestseller Udemy course is on sale for $9.99, the lowest price of the year. Buy it now and get lifetime access to the course and the reshoot that will be published by the end of 2023. I will publish a new code here every week until the end of October. Click here to buy or use the code: OCTOBER1
  • My bootcamp-style six-week long Advanced Flow course is on a 50% sale. Buy it now and start the course on the 8th of January. Start the year strong: Click here to register.

This post was originally made to LinkedIn on October 17, 2022.

Read the previous post: AND(NextStep = “GoWithTheFlow”​, OR(Type “WFR”​, Type “PB”​))


Migrate to Flow (Beta) in Spring 22

Hello folks,

I try out Beta features, but I do not spend much time on them. In the end, beta means: “I can take away this feature if I need to.” Do you remember Salesforce Anywhere? You most probably don’t. I rest my case.

However, Migrate to Flow (Beta) requires extra attention. Although the product is in beta – and you will know that it is in beta once you try it -, Salesforce committed to retiring workflow rules; therefore, Salesforce must roll out this product in the end.

Folks who have been following me will know I have done a few sessions on migrating WFRs and Processes to Flow, one in Florida Dreamin’ in person and a few virtually. You can see a few videos on this topic on my YouTube channel. Please check the resources section below for links.

The tool only works on workflow rules for now. It does not support processes. I assumed it would support most workflow rules, but I was wrong.

I had two workflow rules in my Preview Org that I have built for my sessions before. I tried to migrate these workflow rules using this tool. Unfortunately, one did not convert due to an update on a long text area field. The other one was not supported because it created a task.

This wasn’t very reassuring, to be honest. But I had to test the tool, so I created a simple field update flow to migrate that.

The use case is as follows: When a picklist value is updated with a specific value on the lead record, the workflow rule updates the other picklist value.

The tool worked without a problem for this use case.

And as you would expect, it converted the workflow rule to a before save flow which is faster and more efficient.

Here is the message you see on the screen when the new flow is created:

“Because this workflow rule only updates fields, we converted it to a before-save flow for optimal performance. A before-save flow quickly updates fields on the record that triggers the flow.

This conversion changes the order in which this automation is executed. To have this flow run after other related automation, change it to an after-save flow. For both before-save and after-save flows, we recommend that you perform end-to-end testing for all scenarios in which the automation is triggered.”

Did you notice something here that immediately caught my attention? Salesforce practically wiped out the terms before save and after save from the record-triggered flow configurator screen; they buried the terms into the description fine print. This flow is called a fast field update flow on that screen. And after save is called actions and related records.

However, these terms don’t exist on this screen or the Trigger Explorer screen. And if I am going to be picky before-save is written with a dash here, without a dash on the Trigger Explorer.

It seems like Salesforce needs more clarity around the terms they use.

The release notes are very brief for the Migrate to Flow (Beta) tool. It does list what it supports; however, it does not list what it does not. I would recommend adding that to the release notes.

Related content (all videos):


P.S. Originally published on 02/14/2022.

Read the previous issue of the newsletter here.

Read the next issue of the newsletter here.

Subscribe to the weekly educational Salesforce Flow Tips newsletter here.