What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split ?
What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split (batch 1 #44) is a gap most SaaS vendors gloss over — here is the operator-level answer.
Focus on one measurable outcome, a single RevOps owner, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.
Why this is under-answered online
Vendor blogs optimize for top-of-funnel keywords, not your motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallKory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallWhat good looks like
- Definition of done tied to revenue or data quality, not activity counts.
- Documented rollback and a named DRI.
- No shadow spreadsheets for metrics leadership reviews.
<!--pillar-weave-->
Related on PULSE
- [What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split ?](/knowledge/q10362)
- [What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split ?](/knowledge/q10282)
- [What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split ?](/knowledge/q10202)
- [What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split ?](/knowledge/q10122)
- [What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for BDR-to-AE split ?](/knowledge/q10042)
- [What CRM fields prove you fixed MQL decay after migrating to Zoho CRM for services-led sales ?](/knowledge/q10402)
The Three Fields That Kill MQL Decay: Lead Score Delta, Handoff Velocity, and Disqualification Reason
The most common mistake teams make after migrating to Zoho CRM is assuming the BDR-to-AE split alone fixes decay. It doesn't. You need three specific fields that act as early-warning sensors for decay, not just handoff tracking. These fields must be populated automatically, not manually, or they'll rot faster than the MQLs themselves.
Field 1: Lead Score Delta (Custom Field – Integer, hidden from most users) This field stores the difference between the lead score at the moment of BDR assignment and the score at the moment of AE acceptance. A positive delta means the lead got hotter during BDR nurture. A negative delta of more than 10 points within 48 hours is your decay signal. In Zoho CRM, create this as a formula field using the SCORE function and a timestamp-based lookup. The formula should calculate (Current_Lead_Score__c - Lead_Score_At_BDR_Assignment__c). If you see a delta of -15 or more, that MQL is decaying faster than you can react. Set a workflow rule that flags any record with a delta below -10 for immediate BDR re-engagement or disqualification.
Field 2: Handoff Velocity (Custom Field – Decimal, calculated in hours) This is the time elapsed between the BDR marking the lead as "Qualified for AE" and the AE setting the first activity type (call, email, meeting scheduled). In Zoho CRM, you can use the DATEVALUE and TIMEVALUE functions to calculate this in a formula field: (First_AE_Activity_Time__c - BDR_Qualification_Time__c) * 24. Any handoff taking longer than 4 hours during business days is a decay risk. The sweet spot is under 2 hours. If your average handoff velocity exceeds 6 hours, your BDR-to-AE split is structurally broken, and no field will fix it until you align schedules or implement an automated round-robin with SLA enforcement.
Field 3: Disqualification Reason (Picklist – Required field for any lead moved to "Disqualified" or "Lost") This is the most underused field in Zoho CRM for decay prevention. When an AE disqualifies an MQL that the BDR qualified, the picklist must capture the specific reason: "No Budget," "No Authority," "No Need," "Not Ready," "Wrong ICP," "Duplicate," or "Other." If more than 20% of disqualified MQLs fall under "Not Ready" or "Wrong ICP," your BDR qualification criteria are misaligned with AE expectations. This field becomes your decay diagnostic. Run a monthly report grouping disqualification reasons by BDR. If one BDR has a 40% "Wrong ICP" rate, they're padding their pipeline with unqualified leads, directly causing MQL decay downstream.
The Pulse Metric Report: Your Weekly Decay Dashboard in Zoho CRM
A single report in Zoho CRM can surface decay before it kills your pipeline. You don't need multiple dashboards. You need one "Pulse Metric" report that tracks four key fields weekly. This report should be shared with both the BDR manager and the AE manager, with a Slack or email alert triggered when any metric crosses a threshold.
Report Configuration:
- Module: Leads (with conversion tracking enabled)
- Group By: BDR Owner, then AE Owner
- Columns: Total MQLs Assigned, MQLs with Lead Score Delta < -10, MQLs with Handoff Velocity > 4 hours, MQLs Disqualified with "Not Ready" Reason
- Filters: Created Date = Last 7 Days, Status = "Qualified" or "Disqualified"
Thresholds to Watch:
- If more than 15% of MQLs have a Lead Score Delta below -10, your BDR nurture sequence needs immediate revision.
- If more than 25% of MQLs exceed 4-hour handoff velocity, your BDR and AE schedules don't overlap enough. Consider staggering shifts or implementing a "hot lead" alert that pings the next available AE.
- If more than 10% of disqualified MQLs are "Not Ready," your BDRs are pushing leads that need more time. Create a "Nurture" stage with a 30-day re-engagement workflow instead of forcing qualification.
Automation in Zoho CRM: Set up a workflow that runs every Monday at 8 AM. It checks the Pulse Metric report and sends a summary to both managers. If any threshold is breached, it creates a task for the RevOps owner to investigate. This removes the need for manual decay audits. The report becomes your single source of truth for whether the BDR-to-AE split is holding or failing.
The Hidden Decay Field: "BDR Engagement Count" and Why It Predicts AE Acceptance
Most teams track whether a BDR called or emailed, but they don't track the *depth* of engagement. The field "BDR Engagement Count" (a roll-up summary of all BDR activities on the lead record) is a powerful predictor of whether an MQL will decay after handoff. In Zoho CRM, you can create this as a roll-up field on the Lead module that counts all activities (calls, emails, meetings, notes) created by users in the BDR role.
Why it matters: A lead with 3+ BDR touchpoints has a 60% higher probability of being accepted by an AE within 24 hours, compared to a lead with only 1-2 touchpoints. The reason is simple: the AE sees a well-nurtured lead and feels the BDR has done their job. A lead with only 1 touchpoint feels cold, and the AE is more likely to delay or disqualify it.
Setting it up in Zoho CRM:
- Create a custom field called
BDR_Engagement_Count__c(Integer, read-only). - Use a Zoho CRM function or Deluge script that counts activities where the
Created Byuser's role equals "BDR" and theCreated Timeis after the lead'sMQL_Date__c. - Run this script nightly or on lead assignment.
- Set a workflow that flags any lead with
BDR_Engagement_Count__c < 3andLead_Score_Delta__c < -5for a 24-hour BDR re-engagement before it's sent to AE.
The decay signal: If you see a cluster of leads with BDR Engagement Count of 1 or 2 that are also showing negative Lead Score Deltas, you have a systemic issue. Your BDRs are doing shallow qualification—just enough to hit their MQL quota—but not enough to sustain the lead's interest through the handoff. This is the most common cause of MQL decay after a BDR-to-AE split. The fix isn't more fields; it's changing BDR compensation to reward engagement depth, not just MQL count. Track this field for 30 days post-migration. If the average BDR Engagement Count stays below 3, your split is creating decay, not fixing it.
Proof Fields: Lead Source Detail & BDR Touch Timestamp
After Zoho migration, add a custom "Lead Source Detail" field (picklist: Inbound Webinar, Outbound Campaign, Partner Referral, Organic Search). This isolates which source type actually converts to AE-qualified opportunities. Pair it with a "Last BDR Touch Date" timestamp field — auto-populated via Zoho's workflow on any BDR email/call logged. Run a weekly report comparing MQL-to-SQL conversion rates by source detail. A 15-25% improvement in conversion from previously decayed sources (e.g., stale webinars) confirms the split fixed the handoff.
Validation Field: Handoff Quality Score
Create a "Handoff Quality Score" (1-5, integer field) on the Lead/Deal record, set manually by the AE after the first discovery call. Score criteria: 1 = "No context provided", 5 = "BDR fully qualified need/budget/timeline". Track the average score over 30 days post-migration. A stable score above 3.5 indicates the BDR-to-AE split is working — decayed MQLs are being properly vetted before handoff, not just dumped into the pipeline.
Pulse Metric: Time-to-First-AE-Contact
Add a "Time-to-First-AE-Contact" field (calculated, hours). Zoho's formula: [First AE Call Logged] - [BDR Handoff Date]. Report this weekly alongside MQL volume. Target: ≤4 hours for 80% of handoffs. If this metric improves by 40-60% within 60 days of migration, you've eliminated the decay caused by slow assignment or split confusion.
Field 1: BDR_Handoff_Timestamp (Custom DateTime)
This field captures the exact moment a BDR marks a lead as qualified and pushes it to an AE. Unlike standard "Last Modified Date," this timestamp is triggered only by a specific workflow rule — preventing accidental updates from skewing the handoff metric. Use it to calculate time-to-engagement: if the average drops below 4 hours post-migration, you’ve likely fixed decay caused by stale routing.
Field 2: AE_Assignment_Reason (Picklist)
Add a picklist with values like "Round Robin," "Territory Match," or "Manual Override." This field logs why an AE received the lead, exposing whether decay stemmed from assignment logic (e.g., round robin ignoring BDR intent data). After migration, a low "Manual Override" rate (<5%) signals the split is working as designed, not bypassed by reps.
Field 3: MQL_Recycle_Count (Rollup Summary)
Roll up the number of times a lead re-entered MQL status after being disqualified. A drop from >2 to <1 per lead within 30 days of migration proves decay is fixed — leads aren’t bouncing back due to poor qualification or field gaps. Report this weekly alongside pipeline velocity to show board-level impact.
Sources
- Zoho CRM official documentation — covers field types, modules, and migration best practices
- Gartner — provides research on lead management, MQL definitions, and sales process metrics
- HubSpot Blog — offers insights on lead decay, BDR-to-AE handoff, and CRM field optimization
- Salesforce Trailblazer Community — includes discussions on MQL decay tracking and field mapping during migrations
- Forrester Research — publishes reports on B2B lead scoring, pipeline management, and CRM effectiveness
- LinkedIn Sales Solutions — shares expert articles on sales development workflows and CRM field strategies
FAQ
What is MQL decay in the context of a BDR-to-AE split? MQL decay happens when leads passed from BDRs to AEs lose momentum due to slow response, poor data, or unclear ownership. In Zoho CRM, you can track it by monitoring the time between lead assignment and first AE activity, and by comparing conversion rates before and after the migration.
Which CRM fields should I use to prove MQL decay is fixed? Key fields include “Lead Response Time” (hours between BDR qualification and AE assignment), “First Touch Activity Date” (when the AE first contacts the lead), and “Stage Duration” (days in each pipeline stage). Adding a custom “BDR-to-AE Handoff Status” field with values like “Successful” or “Stalled” gives you a clear audit trail.
How do I set up these fields in Zoho CRM after migration? Create custom fields under Leads and Deals modules, then use workflows to auto-populate timestamps when records move between BDR and AE queues. For example, a workflow can update “First Touch Activity Date” when an AE logs a call or email. This ensures data consistency without manual entry.
What reports in Zoho CRM show MQL decay improvement? Build a “Handoff Performance” report with columns for lead source, BDR owner, AE owner, response time, and conversion rate. Use a funnel chart to visualize drop-offs between stages. A weekly “Pulse Metric” report comparing response times and win rates before and after the migration will highlight progress.
How long does it take to see measurable results after implementing these fields? Typically 4-8 weeks for a pilot segment, depending on sales cycle length. You’ll see early signals in response time reduction within 2 weeks, but conversion rate improvements may take a full cycle to validate. Run the pilot on one territory or product line before scaling.
What if my team resists using new fields or workflows? Start with a 2-week pilot on a small team, showing them a simple dashboard that tracks their own handoff efficiency. Use Zoho’s audit logs to catch data gaps without blame. Once they see faster deal progression and fewer lost leads, adoption usually follows naturally.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.