Most consolidation decisions live in licensing spreadsheets. You kill Slack's ₹192K annual bill, ditch HubSpot's ₹150K seat sprawl, and fold invoicing into one platform. The math looks clean: you cut ₹400K yearly spend, call it a win, and move to the next board agenda item. Then the 90 days hit. Custom fields vanish. Workflows need rebuilding. Your team relearns a new interface while your data integrity takes a hit. Integration debt—the hidden cost of consolidation—swallows your licensing savings faster than anyone predicted. This scorecard lets you quantify that debt before you migrate. It shows you where consolidation wins and where it bleeds money you didn't budget for. What integration debt actually is Integration debt is the operational cost of knitting disparate systems together—or tearing them apart and rebundling them. It has four hard components: Custom field loss: Fields you built in HubSpot for sales rules or deal stages don't exist (or have to be rebuilt) in the new platform. Rebuilding them takes engineering or configuration time. Workflow rebuilding: Your Zapier automations, conditional routing, and approval chains. Moving them to native automations in a bundled platform means re-architecting logic that already works. Data quality degradation: Migration never preserves 100% of historical context. Relationship notes, custom record links, and partial data often orphan during export. Your team either cleans it or works around it. Team retraining: Three tools means three interfaces your team knows. One platform means everyone relearns navigation, field locations, and reporting flows. Productivity drops 2–4 weeks per person during transition. The scorecard: Four questions that predict your 90-day cost 1. How many custom fields and stages will you lose or rebuild? Count every non-standard field in your current systems: HubSpot deal stages, Slack integrations that push data into custom fields, invoicing system tax codes or payment terms that don't have native equivalents. Scoring: Fewer than 10 custom fields across all tools: 0 debt points. The new platform likely has equivalents or close workarounds. 10–30 custom fields: 2 debt points. Plan 20–40 engineering hours to rebuild or map them. 31–60 custom fields: 4 debt points. Budget 60–100 hours and assume some fields will compress or drop. 60+ custom fields: 6 debt points. You're not consolidating; you're replacing. Data loss is inevitable. A typical HubSpot+Slack+invoicing stack with moderate customization lands at 20–35 custom fields. That's 2 debt points and 30–60 hours of re-mapping work. 2. How many active automations will you rebuild? List every Zapier flow, HubSpot workflow, and Slack integration that moves data or triggers action. Include approval chains, notification rules, and conditional routing. Scoring: Fewer than 10 automations: 1 debt point. Most platforms have native equivalents. 10–25 automations: 3 debt points. Plan 40–80 hours to audit and rebuild. 25–50 automations: 5 debt points. Budget 80–150 hours and accept that some complex logic may simplify. 50+ automations: 7 debt points. You have automation debt before consolidation debt hits. Most growing businesses run 15–25 automations across three tools. That's 3 debt points and 50–100 hours of rebuild time. At ₹1,500/hour loaded cost, you're looking at ₹75K–₹150K in labor. 3. What percentage of your team will need retraining and how long? Not everyone retrains equally. Sales reps, accountants, and ops teams hit different curves. A sales rep picks up CRM navigation in 1–2 weeks. An accountant rebuilding GL posting rules and tax workflows may need 3–4 weeks. Scoring: Small team (fewer than 10): 2 weeks average retraining, 2 debt points. You absorb it in sprint planning. Mid team (10–30): 3 weeks average, 3 debt points. One person per function is usually unproductive during transition. Large team (30–60): 3–4 weeks average, 5 debt points. 5–10 people are below par for a month. Enterprise (60+): 4 weeks average, 6 debt points. Stagger training in batches or accept 20% productivity loss across the org for one month. A 15-person team at 3 weeks retraining, at ₹40K average cost per person-month, costs you ₹60K in lost productivity (one month × 15 people ÷ 4 weeks into the month). That's 3 debt points and ₹60K in real money. 4. How much data will you orphan or spend hours cleaning? Migration tools claim 99% fidelity. Reality is messier. Partial records, broken links, custom fields with no target destination, and relationship context that lives in notes or third-party apps all require manual cleanup or deliberate abandonment. Scoring: Clean, well-structured data (fewer than 5 years of records, no orphaned entries): 1 debt point. One person spends 2 weeks cleaning. ₹20K. Moderate data sprawl (5–10 years, some orphaned records, custom fields with mixed completeness): 3 debt points. Two people, 3–4 weeks. ₹60K. Heavy data sprawl (10+ years, multiple orphaned systems feeding into your main CRM, in