⚠️ Workflow Rules retire Dec 31, 2025. Process Builder already deprecated. Every rule you haven't migrated is now a liability.
Paste your Workflow Rule metadata XML
Retrieve from SFDX: sf project retrieve start -m Workflow — paste one or concatenate multiple .workflow-meta.xml files.
Paste your Process Builder Flow XML
Retrieve from SFDX: sf project retrieve start -m Flow — Process Builder flows have processType=Workflow. Paste one or multiple.
🔄

Drop your Workflow & Flow files here

Retrieve with: sf project retrieve start -m Workflow,Flow

.workflow-meta.xml .flow-meta.xml Multi-file OK
Mix and match — drop Workflow Rule files and Process Builder Flow files together for a combined audit.

Auditing your migration backlog…

Scoring complexity, risks, overlaps, and effort. Usually under a second.

Parsing Workflow Rule and Process Builder metadata
Scoring migration complexity and action types
Detecting risk patterns and recursive loops
Checking for overlap and conflict between rules
Flagging stale, inactive, and poorly-named rules
🔄 Migration Audit
migration_audit.xml
0 rules
0 READINESS

⏱ Estimated Migration Effort

Rule / Process Type Object Actions Effort

Share this audit with your team

Copy a plain-text summary of all findings to paste into Slack, Jira, or your migration doc.

Ready to actually migrate?

Luxera Cloud audits your entire Salesforce org on a schedule — flagging migration risks, broken flows, and config debt before they become incidents. Get the full picture, not just one file at a time.

See Founding Member Pricing →
Founding Member $99/mo locked — limited spots remaining
📄

Get your migration report

Enter your email and we'll send you the full PDF with all findings, effort estimates, and migration recommendations. One email, no spam.

Also audit the flows you migrated from Workflow Rules → 7 flow patterns that break silently in production