If you’re still running Workflow Rules or Process Builder in your Salesforce org, you’re not alone. Thousands of organisations built their automation on these tools—but it’s time to move forward.
Salesforce has been clear: Workflow Rules and Process Builder are retired. Whilst existing automations continue to function, you cannot create new ones, and support will eventually cease entirely. The path forward is Flow—and increasingly, Flow enhanced with Agentforce.
At Purus Consultants, we’ve guided numerous clients through automation migration projects. Here’s everything you need to know about modernising your Salesforce automation.
Why Migrate Now?
Beyond Salesforce’s official retirement timeline, there are compelling business reasons to migrate:
Enhanced Capabilities – Flow offers functionality that Workflow Rules and Process Builder simply cannot match: loops, collections, complex branching, external integrations, and screen-based user interactions.
Better Performance – Modern Flow execution is more efficient, with improved governor limit handling and optimisation capabilities.
AI Integration – Only Flow integrates with Agentforce, unlocking intelligent automation that adapts to context and user needs.
Simplified Maintenance – Consolidating automation into a single tool (Flow) reduces technical debt and makes your org easier to manage.
Future-Proofing – All new automation features from Salesforce will be built for Flow, not legacy tools.
Delay only increases the technical debt you’ll eventually need to address.
Understanding What You’re Migrating From
Workflow Rules
Workflow Rules handle straightforward, linear automation: when a record meets criteria, perform actions like field updates, email alerts, tasks, or outbound messages. They’re simple but limited—you cannot update related records, make complex decisions, or integrate with external systems.
Process Builder
Process Builder added more sophistication: updating multiple objects, more complex criteria, and invoking external processes. However, it’s slow, prone to errors when misconfigured, and notorious for creating maintenance headaches as processes grow complex.
Both tools have served their purpose, but they’re fundamentally limited compared to what Flow can do.
The Migration Strategy
Successful migration requires a methodical approach, not a rushed conversion.
Step 1: Audit Your Current Automation
Before migrating anything, understand what you have:
– Document all active Workflow Rules and Process Builder processes
– Identify what each automation does and why it exists
– Determine which are business-critical versus nice-to-have
– Look for duplicates or overlapping logic
– Assess complexity—simple automations migrate easily, complex ones require more planning
This audit often reveals automation that’s no longer needed or can be simplified.
Step 2: Prioritise What to Migrate
You don’t need to migrate everything simultaneously. Prioritise based on:
– Business criticality—start with the most important processes
– Complexity—tackle simpler automations first to build momentum
– Agentforce potential—identify automations that would benefit from AI enhancement
– Risk—migrate low-risk processes first as you build confidence
Step 3: Redesign, Don’t Just Convert
The biggest mistake organisations make is treating migration as a mechanical conversion: taking old logic and recreating it exactly in Flow.
Instead, this is an opportunity to redesign. Ask:
– Does this automation still serve its original purpose?
– Could this be done more efficiently?
– Are there additional capabilities we should add?
– Would Agentforce integration add value here?
Modern Flow opens possibilities that didn’t exist when your original automation was built. Take advantage of them.
Step 4: Build and Test Thoroughly
For each automation you’re migrating:
Build the Flow – Use modern best practices: clear naming, comments, modular design, and proper error handling.
Test Comprehensively – Test all scenarios, not just the happy path. Include edge cases, invalid data, and volume testing.
Run in Parallel – Where possible, run the new Flow alongside the old automation initially, comparing results to ensure consistency.
Monitor Closely – After activation, monitor the Flow’s execution and performance carefully for the first few weeks.
Step 5: Deactivate Legacy Automation
Only after you’re confident the new Flow works correctly should you deactivate the old automation. Keep documentation of what was replaced and when, in case you need to reference it later.
Workflow Rules: What to Watch For
When migrating Workflow Rules, watch for:
Time-Based Actions – These need to be replicated using scheduled paths in Flow. Timing must match exactly to avoid disrupting users.
Email Alerts – Flow can send emails, but templates and formatting must be migrated carefully.
Field Updates – Straightforward in Flow, but watch for formula fields that might need adjustment.
Outbound Messages – These often indicate external integrations. Consider whether modern REST APIs would be more appropriate than outbound messages.
Process Builder: What to Watch For
Process Builder migrations are more complex due to:
Record Updates – Process Builder can update related records, but Flow offers more sophisticated options through loops and collections.
Multiple Criteria – Process Builder’s branching logic maps to decision elements in Flow, but the architecture may be cleaner if redesigned.
Invocable Actions – These often connect to external systems. Verify that these integrations still work when invoked from Flow.
Recursion Issues – Process Builder is notorious for recursion problems. Use Flow’s built-in safeguards to prevent these issues.
Enhancing with Agentforce
Once you’ve migrated to Flow, consider which processes would benefit from Agentforce integration. Good candidates include:
User-Facing Processes – Anything that currently requires users to fill out forms or make decisions manually could potentially be handled conversationally by an agent calling your Flow.
Complex Decision-Making – If your Flow includes extensive decision logic, an agent might handle it more intelligently by reasoning about context.
Data Retrieval – Flows that fetch and display information are perfect for agent actions—users can simply ask questions rather than navigating to specific records.
Not every Flow needs Agentforce integration, but identifying these opportunities during migration sets you up for future enhancement.
Common Migration Pitfalls
Avoid these mistakes:
Rushing the Migration – Taking time to plan properly saves significant pain later.
Ignoring Governance – Establish clear naming conventions, documentation standards, and approval processes before building Flows.
Over-Complicating – Just because Flow can do something doesn’t mean it should. Keep automations as simple as possible.
Neglecting Training – Your team needs to understand Flow to maintain what you build. Invest in training.
Skipping Testing – Inadequate testing leads to production issues that damage user trust.
The Purus Approach
We follow a structured methodology for automation migration:
1. Discovery – Comprehensive audit of existing automation and business processes
2. Strategy – Prioritisation roadmap aligned with business objectives
3. Redesign – Modern Flow architecture that improves upon legacy logic
4. Implementation – Phased deployment with thorough testing at each stage
5. Enablement – Training and documentation so your team can maintain and extend the automation
6. Optimisation – Post-implementation review and enhancement, including Agentforce opportunities
Our goal isn’t just to move your automation to a new tool—it’s to improve your business processes in ways that weren’t previously possible.
Timeline and Resources
Migration timelines vary significantly based on:
– Number of existing automations
– Complexity of business logic
– Availability of internal resources
– Whether you’re simultaneously implementing Agentforce
A typical organisation with 30-50 Workflow Rules and 10-20 Process Builder processes might expect:
– 2-4 weeks for audit and planning
– 2-3 months for development and testing
– 1-2 months for phased deployment
Larger or more complex orgs require proportionally more time.
Ready to Modernise Your Automation?
If you’re still relying on Workflow Rules and Process Builder, now’s the time to plan your migration. The longer you wait, the more technical debt accumulates.
We can help you assess your current automation, design a migration strategy, and execute the transition smoothly—minimising disruption whilst maximising the opportunity to improve your processes.
Get in touch to discuss your automation migration needs and how we can support your journey to modern, AI-ready Salesforce automation.