How to Audit Your HubSpot Workflows Before a Major CRM Migration

Why Workflow Audits Are Critical Before Migration

Migrating from HubSpot to another CRM—or consolidating multiple HubSpot portals—is one of the most complex projects a RevOps team will tackle. Your workflows represent years of institutional knowledge, business logic, and operational dependencies that don't transfer automatically.

Without a thorough audit, you'll either recreate broken processes in your new system or lose critical automation that your sales, marketing, and service teams depend on daily. I've seen migrations where teams discovered missing lead routing logic three weeks post-launch, resulting in hundreds of unassigned leads and a scramble to rebuild.

The goal isn't just documentation—it's strategic evaluation. Some workflows should migrate exactly as-is, others need redesigning, and many should be retired entirely.

Phase 1: Create a Complete Workflow Inventory

Export Your Workflow Metadata

Start by building a comprehensive list of every workflow in your portal. Navigate to Automation > Workflows and use the export function to download a CSV of workflow names and basic metadata. However, this export lacks critical details, so you'll need to supplement it.

For each workflow, document:

• Workflow name and ID (the ID appears in the URL when editing)
• Object type (contact, company, deal, ticket, custom object)
• Enrollment trigger type (form submission, list membership, property change, manual, etc.)
• Status (active, paused, draft)
• Last modified date and by whom
• Estimated enrollment volume (check the Performance tab)

Categorize by Business Function

Group workflows into functional categories to understand dependencies:

1. Lead routing and assignment - Round-robin, territory-based, or score-based routing
2. Lead nurturing and scoring - Drip campaigns, behavioral scoring updates
3. Sales process automation - Deal stage updates, task creation, internal notifications
4. Data hygiene - Property standardization, duplicate management, lifecycle updates
5. Integration triggers - Webhooks, third-party syncs, Slack/email notifications
6. Customer success - Onboarding sequences, renewal reminders, NPS triggers

This categorization helps you identify which teams depend on which workflows and ensures you don't miss stakeholder input during evaluation.

Phase 2: Document Business Logic and Dependencies

Map Enrollment Criteria in Detail

The enrollment trigger is where most migration complexity lives. For each active workflow, document the exact enrollment logic in plain language that a non-technical stakeholder could validate.

Example documentation format:

Workflow: MQL to Sales Assignment
Triggers when: Contact property "Lifecycle Stage" changes to "MQL"
AND Contact property "Country" is any of [US, CA, UK]
AND Contact property "Lead Source" is not "Partner Referral"
Re-enrollment: Disabled

Pay special attention to:

• Re-enrollment settings - These often contain critical business rules
• Suppression lists - Which contacts are explicitly excluded
• Goal criteria - What removes contacts from the workflow
• Branching logic - If/then conditions that route contacts differently

Identify Cross-Workflow Dependencies

Workflows often trigger other workflows or depend on upstream automation. Map these relationships:

• Does this workflow set a property that triggers another workflow?
• Does this workflow add contacts to a list used by other automation?
• Are there workflows that should run sequentially but aren't explicitly connected?

Create a simple dependency diagram. Even a spreadsheet showing "Workflow A triggers Workflow B by setting property X" will save hours during migration planning.

Document Integration Touchpoints

Every webhook, custom code action, or third-party integration needs special attention:

• Webhook URLs - Where do they point? What payload do they send?
• Custom code actions - Export the actual code and document what it does
• Third-party app triggers - Zapier, Make, native integrations that fire from workflows
• Internal notifications - Who receives alerts and why?

Phase 3: Evaluate and Prioritize for Migration

Apply the RICE Framework to Workflows

Not every workflow deserves migration. Evaluate each using modified RICE scoring:

• Reach: How many records does this workflow affect monthly?
• Impact: What happens if this workflow doesn't exist? (1-3 scale)
• Confidence: Do stakeholders confirm this workflow is still needed?
• Effort: How complex is recreation in the target system?

Workflows with high reach and impact but low confidence need stakeholder validation before you invest migration effort.

Flag Workflows for Retirement

During your audit, you'll find workflows that should be killed, not migrated:

• Zero enrollments in 6+ months - Likely obsolete
• Duplicate logic - Multiple workflows doing similar things
• Workarounds - Automation built to fix a HubSpot limitation that doesn't exist in your target CRM
• Owner departed - No one knows why it exists, and testing shows no impact when paused

Before retiring, pause the workflow for 2-4 weeks and monitor for complaints or downstream effects.

Create Migration Priority Tiers

Organize workflows into tiers based on your evaluation:

Tier 1 - Day One Critical: Lead routing, deal stage automation, integration syncs Tier 2 - Week One Required: Internal notifications, task automation, basic nurturing Tier 3 - Month One Nice-to-Have: Advanced nurturing, data hygiene, edge case handling Tier 4 - Retire: Obsolete, redundant, or no longer needed

Phase 4: Create Actionable Migration Documentation

Build Workflow Specification Sheets

For each Tier 1 and Tier 2 workflow, create a specification sheet your implementation team can use:

• Business purpose: One sentence explaining why this exists
• Enrollment logic: Exact criteria in target system terminology
• Actions: Step-by-step what the workflow does
• Testing criteria: How to validate it works correctly
• Owner: Who approves this workflow as correctly migrated

Establish a Testing Protocol

Define how you'll validate migrated automation:

1. Create test records matching enrollment criteria
2. Verify correct routing/actions occur
3. Confirm notifications reach correct recipients
4. Check integration data flows to third-party systems
5. Validate suppression logic prevents incorrect enrollment

Plan for Parallel Running

For critical workflows, plan a parallel running period where both systems operate simultaneously. This requires:

• Clear cutoff dates for each workflow tier
• Monitoring dashboards in both systems
• Rollback procedures if the new system fails

Final Recommendations

Start your workflow-audit" title="HubSpot Workflow Audit">workflow audit at least 8-12 weeks before your target migration date. The documentation process alone typically takes 2-4 weeks for portals with 50+ active workflows.

Involve stakeholders early—sales managers, marketing ops, customer success leads—to validate that your documentation matches their understanding of how things should work. You'll often discover that the workflow logic has drifted from the intended business process.

Finally, treat this audit as a gift to your future self. Regardless of migration, this documentation becomes invaluable for onboarding, troubleshooting, and continuous optimization.