Yes even in 2025, many Salesforce users have not moved to Flow..

Salesforce is formally retiring Workflow Rules and Process Builder. As of December 31, 2025, support for both tools will end. Some existing automations may still execute, but they will no longer be supported, and Salesforce will not guarantee their performance.

Need Help With Salesforce? Book a Health Check Now

Why This Matters Now:
For most orgs, the ability to create new Workflow Rules and Process Builders has already been removed. This means all net-new automation must be built in Flow. More importantly, legacy automations present operational risk – they are unsupported, harder to debug, and incompatible with Salesforce’s roadmap.

Key Migration Deadlines (Updated for 2025):

Now: Creation of new Workflow Rules and Process Builders is disabled in most Salesforce orgs.
Dec 31, 2025: End of support. No bug fixes, enhancements, or guarantees from Salesforce.
Post-2025: Existing legacy automation may still run but is at risk of breaking.

Recommended Actions for 2025:

Inventory Your Automation
- Use Salesforce’s “Where is this used” and “Flow Migration Tool” to identify active Workflow Rules and Process Builders.
Segment Automation into Risk Levels
- High risk: time-based actions, cross-object updates, integrations.
- Medium: heavy usage or customer-facing processes.
- Low: internal alerts or non-critical tasks.
Migrate Strategically
- Don’t rely solely on the Migration Tool. Use it for initial mapping, but validate all logic manually.
- Rebuild high-risk processes in Flow using best practices (use Subflows, error handling, before-save triggers).
Document and Test Everything
- Regression test every new Flow against your current automation. Create test data. Use debug logs.
Update Your Documentation and Training
- Ensure your team knows how to build and maintain Flows. Update internal knowledge bases and onboarding content.

Optimize Salesforce Now

Flow in 2025: What’s New and Improved

Orchestrator: Build multi-step processes with human approvals.
Subflows: Modularize automation for scalability.
Error Handling: Robust tools for troubleshooting.
Trigger-Based Flows: Use before-save updates for efficiency.

Don’t Forget:

ISVs & Managed Packages: Some automation lives in third-party code. Contact vendors to confirm Flow compatibility.
Governance: Institute code review and QA process for all new Flows.

Bottom Line:
Flow isn’t just replacing Workflow and Process Builder — it’s a fundamentally more powerful, scalable platform. But it requires thoughtful planning and skilled implementation. If you haven’t started your migration, now is the time.

If you’d like a checklist or migration plan template, I can create that next.