{"id":970,"date":"2023-07-09T17:39:53","date_gmt":"2023-07-09T17:39:53","guid":{"rendered":"https:\/\/baseweb.brigittebianchi.com\/?p=970"},"modified":"2025-02-28T16:57:52","modified_gmt":"2025-02-28T16:57:52","slug":"get-ready-to-migrate-your-processes-to-salesforce-flows","status":"publish","type":"post","link":"https:\/\/www.skyblux.com\/en\/welcome\/get-ready-to-migrate-your-processes-to-salesforce-flows\/","title":{"rendered":"Get ready to migrate your processes to Salesforce Flows"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

One of the big differentiators that Salesforce offers is the focus on automations of manual and repetitive time-consuming tasks. Salesforce realized that it has three major automation tools that have overlapping capabilities. These are: Process Builder, Worflows (Workflow Rules) and Flows.<\/p>

As a system administrator, you have probably encountered some of these issues:<\/p>

  1. It is difficult to get an overall picture about existing automations.<\/li>
  2. An increasing need to create more sophisticated or complex processes.<\/li>
  3. It takes a lot of time to maintain all automations and to verify that no processes are the same or somehow overlap or produce errors.<\/li><\/ol>

    This is why it is much more cost-effective in time, cost and maintenance to have a single tool for process automation. Salesforce has proposed 2025 as the target date for migration from Process Builder and Workflows to Flows.<\/p>

    Why Flows?<\/b><\/p>

    Flows have a variety of features and advantages for administrators and users. For example:<\/p>

    1. Flows offer a wider range of action and better performance. For example, in a single flow it is possible to update several records at the same time thanks to the option of creating collections. On the other hand, in a \u00abProcess Builder\u00bb, only the child records or records directly related to the record selected as the main one could be updated. This in turn means that in the case of the \u00abProcess Builder\u00bb several processes would have to be created to satisfy the requirement, consuming more performance and having several processes to maintain and working on the same object.<\/li>
    2. Tienen una herramienta de verificaci\u00f3n y detecci\u00f3n de errores. The \u00abDebug\u00bb tool can be used within the flows to validate where in the process the errors are occurring.<\/li>
    3. They provide the possibility of quick actions before saving the record.<\/li>
    4. They allow automations to guide the customer in their processes (screen flows), etc.<\/li><\/ol>

      In general, flows allow a wider range of tools and possibilities for administrators than what is offered by \u00abProcess builder\u00bb or \u00abWorkflows\u00bb.<\/p>

      Recommendations:<\/b><\/p>

      1. As part of the migration Salesforce will keep its customers informed through its portals and emails about the migration stages. We leave you a timeline with the migration progress so far proposed by Salesforce. In the image below we show you the timeline proposed by Salesforce so far.<\/li>
      2. Start your studies on flows. There are many tools offered by Salesforce to learn about this topic, such as a Trailhead module, which is its official portal. I leave you one of the modules to learn about flows so you can start learning. https:\/\/trailhead.salesforce.com\/es\/content\/learn\/modules\/flow-basics?trail_id=automate_business_processes<\/a><\/li>
      3. Get guidance on best practices when migrating your process builder and workflows. Salesforce is currently building tools so that you can migrate one by one your automation processes to flows. But also keep in mind that three flows per object are recommended. One for \u00abbefore creating and updating\u00bb, one for \u00abafter creating and updating\u00bb and one for \u00abbefore deleting\u00bb. Of course, there may be exceptions, but keep in mind that there will be processes that you will need to analyze and unify during your migration.<\/li>
      4. \u00a0Use tools such as Flow Trigger Explorer to help you get an overview of all the flows associated with an object. It allows you to visualize when a record is created, updated or deleted. It also allows you to see the details of a particular flow. You can use it to understand your current flows and evaluate which ones to merge with your Process Builder and Workflows.<\/li><\/ol>

        What tools does Salesforce offer to migrate to flows?<\/b><\/p>

        Salesforce to date has offered a tool to facilitate process migration. With the help of this tool it will be possible to migrate these types of actions:<\/p>

        1. Registration update<\/li>
        2. Create record<\/li>
        3. Invocation flow<\/li>
        4. Invoke APEX<\/li>
        5. Email alert<\/li><\/ol>

          To find this option you should look for the \u00abMigrate to Flow\u00bb option in Configuration. On the \u00abMigrate to Flow\u00bb page, select the process you want to convert to a flow and then click Migrate to Flow. Next, select the criteria you want to migrate to flow. After migrating the process, you can test the flow in Flow Builder. Test the new flow and, if everything works as expected, activate the flow and deactivate the process you converted.<\/p>

          In summary, during the year 2023, we as administrators will have to start the migration process to flows, in order to have all your processes updated. We can also take advantage of this opportunity to improve processes and improve the performance of our CRM.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t

          \n\t\t\t
          \n\t\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t