Salesforce Workflow & Process Builder End-of-Life

As of December 2025, Salesforce will officially sunset its Workflow and Process Builder tools in favor of the newer automation tool, Flow. Nonprofits will need a plan to migrate or rebuild their older automations in the new tool. This post guides you through the process, ensuring a smooth transition and unlocking the full potential of Flow for your organization.

Why Migrate to Salesforce Flow?

Well, frankly, because you have to! December 2025 is coming sooner than you think. But good news: Flow is more than just a replacement. It’s a real upgrade to the older options:

• Streamlined Automation: Consolidate all your automation logic in one place.
• Increased Flexibility: Design complex automations with ease, including those requiring loops, collections, and advanced logic.
• Improved User Experience: Create guided visual experiences with screens and user input.
• Future-Proofed Solution: Flow is Salesforce’s preferred automation tool, ensuring ongoing support and enhancements.

For more on how your nonprofit can benefit from Flow, visit our previous post: Hello Salesforce Flow. Farewell Workflows and Process Builder.

Migration Planning: A Step-by-Step Guide

Here are the basic steps for approaching this transition. Remember to do this in a sandbox environment first, so you don’t accidentally break anything your colleagues might rely on for their day-to-day work!

1) Inventory Your Automations:

• Identify all active Workflow Rules and Process Builders: Use Salesforce reports or a tool like “Workbench” to generate a comprehensive list.
• Document each automation: Note its purpose, trigger criteria, and actions performed.
• Assess each automation: Which ones are business-critical? Which are less important? (Are there some that should just be eliminated instead of migrated?)

2) Plan Your Migration:

• Plan multiple phases: Use your documentation and assessment of each automation’s complexity and importance to break down the process into manageable chunks with clear timelines.
• Start with simple automations: Gain experience and confidence with Flow by tackling straightforward pieces first
• Group related processes: Consider migrating related Workflow Rules and Process Builders together to streamline the system.

3) Recreate Your Automations in Flow:

• Use Flow Builder’s visual interface: No code necessary! you’ll drag-and-drop elements to design your automation logic.
• Utilize Flow’s rich feature set: Explore new possibilities with loops, collections, and Apex actions.
• Test thoroughly: Ensure your Flow recreates the original automation’s functionality accurately before deploying your work to Production.

4) Deactivate Old Automations:

• Clean up after yourself: Once a Flow is live and tested, deactivate the corresponding Workflow Rule or Process Builder.
• Monitor closely: Keep an eye on your new Flow for any unexpected behavior, and adjust as needed.

Tips for a Successful Migration

• Embrace the learning curve: Flow may seem daunting initially, but with practice, it becomes intuitive for dedicated admins.
• Start early: Don’t wait until the last minute. Begin your migration planning well in advance of the deadlines.
• Leverage Salesforce resources: Consult Salesforce documentation, Trailhead modules, and community forums for guidance and support. (See more resources here.)
• Work with a partner: If that sounds like a lot – you’re not alone! We’re here to help. Contact us to get started today.