As an admin, you might be dreading the migration process to Flow.You’re not only being pulled away from building new and shiny solutions for your users for what may seem like busy work. You’re also going to have to spend a lot of time retraining your brain from Process Builder to Flow so that the migration process goes smoothly, and so you can reach your full Flow potential.Don’t stress too much: we’re back with part 2 of our series on the great Flow migration with Jack Lavous of Elements.cloud to dig deeper into how Jack was able to transition to Flow with ease. In this episode, Kristi and Jack discuss the biggest mistakes made and lessons learned so that you’re as prepared as you can be to go with the Flow.Listen to this episode to learn: How to balance your Flow transition with other projectsHow to mitigate risk from migrationThe best resources for learning Flow ##Episode Summary Most admins are probably not too excited about the migration process to Flow.You’re not only being pulled away from building new and shiny solutions for your users for what may seem like busy work. You’re also going to have to spend a lot of time retraining your brain from Process Builder to Flow so that the migration process goes smoothly, and so you can reach your full Flow potential.As Host Kristi Campbell, Senior Salesforce Admin & Salesforce MVP, puts it, “it's easy for people to internalize those things and learn them, which is the point. But then you lose the why.” As in, why are we moving over to Flow in the first place? Because ultimately, all that hard work is going to pay off and make all your automations a lot easier to deal with.In part 2 of our series on Flow migration with Jack Lavous, Kristi and Jack dig deeper into how Jack’s company, Elements.cloud, made the migration process go a little bit more smoothly. Jack tells us more about automations he created and tricks he employed to minimize the risk that comes with migration and keep things more streamlined and organized. They also discuss the biggest mistakes made and lessons learned, as well as their favorite online resources, so that you’re as prepared as you can be to go with the Flow.##Key Takeaways Think beyond the norm. With Process Builder, admins were getting comfortable with one process to rule them all. Flow is more versatile in that it lets you control the order of operations through sub-Flows, meaning there is more than just one flow per object.It’s easy to get stuck in old habits, but that can also limit your thinking. Understanding how sub-Flows work is a crucial part of your Flow migration that could save your object from breaking.Field naming conventions are more important than you think. Naming your Flows may seem like a simple one-off task, especially when you’re beginning the migration process. But choosing a specific and accurate name is important for the future you who might be searching for a specific Flow in six months. There’s no right way to name your Flows — just make sure to pick names or create an organized system that makes sense to you and your users. If you’re stuck, the Salesforce Discord Wiki has a detailed guide to field conventions.There are plenty of resources available online that can make your Flow migration easier. Not all of us may be as lucky as Jack — surrounded by experienced Salesforce professionals who can share their experience with Flows. But many of those experts are sharing their expertise online for admins who may need some help.Jack recommends Trailhead, Jen Lee’s blog and the Ohana Slack group. Kristi’s favorites include the SalesforceBreak Slack and Flow Office hours, hosted every Friday by Terry Miller and Andy Engin Utkan. There are also expert-led paid courses available. ##Featured Guest: Jack Lavous of Elements.cloud💥 What he does: Business Excellence Manager and Salesforce Business Analyst at Elements.cloud, an integrated intelligence platform for Salesforce.💻 Elements.cloud on the web: Twitter | LinkedIn 🔗 Jack on the web: Twitter | LinkedIn | Trailblazer🧠 Jack’s big idea: “[Migration is] not the cool stuff. You're not building anything new and shiny for your end-users. But it's also having the understanding of your stakeholders above you in terms of the hierarchy. It’s managing them — for them to understand how important it is that you actually do this migration and this cleanup. I think that's one of the biggest hurdles. If you've got them on side, then they will allow you to find that time to be able to do it.”##Episode Highlights Key excerpts from the episode transcript💡Your Flow migration doesn’t have to happen all at once.[02:21] Jack: “I blocked myself out segments. So for example, I'm working on project A — I do that for two, three hours in a day. If I have a spare hour, for example, I jump back into this migration. [...] It's being really disciplined to do it, because it is really tough. Because the project’...
