You've scaled to ₹50M in annual contract value and Pipedrive still works—until the moment it doesn't. Your forecast says ₹120M in the next quarter. Your finance team knows it's ₹85M. Your CEO is confused. Three deals live in two reps' names. Your weighted probability column has become pure noise. The stage definitions your inside sales team invented in month three no longer match how enterprise deals actually move. This is where Pipedrive stops being a ledger and starts becoming a liability. The problem isn't Pipedrive itself. It's built for teams closing ₹2–10M in annual recurring revenue with linear, 4–6 stage sales cycles. Above ₹50M, your deal physics change. Forecast accuracy requires deal routing clarity that Pipedrive's shared-ownership model can't enforce. Your migration window is narrow—wait until you're at ₹80M and you'll spend four months rebuilding forecasting logic that should have migrated cleanly at ₹55M. Move too early and you're paying for complexity you don't yet need. Where Pipedrive's forecast math breaks Pipedrive calculates probability-weighted revenue by multiplying deal value by the stage win percentage. At ₹5M pipeline with uniform deal sizes, this works. Each deal's contribution is visible. By ₹50M, you have 50+ open deals, some weighted at 25%, others at 80%, all with different sizes and cycle lengths. The formula becomes: Forecast = Σ(deal value × stage probability) — except probability becomes guesswork when deal maturity isn't aligned with stage name. The moment a deal spends four months in "Proposal" instead of three weeks, your stage-probability assumptions shatter. If your Proposal stage is 60% probability because that's how long it took in 2023, but it now takes eight months for enterprise clients to get legal sign-off, you're forecasting ₹120M when reality is ₹75M. Pipedrive has no way to detect that your stage definitions have drifted. You notice it during monthly board calls, not in the system. A second math break: when deals sit in "Negotiation" for two months with no activity, Pipedrive still counts them at 75% probability. There's no auto-decay, no "move to Stalled" trigger based on days-in-stage. Your forecast includes dead deals because you haven't manually closed them. By ₹50M pipeline, you have 10–15 of these per quarter, adding ₹8–15M of phantom revenue to your forecast. The shared-deal-ownership inflation trap At smaller scales, deal routing is informal. A customer success rep and an AE might both touch a deal, and Pipedrive lets you assign it to both. The system doesn't care. Your forecast sums their contributions. By ₹50M, this becomes a ₹20M problem. Here's the real scenario: A deal enters Pipedrive at ₹2M, assigned to Rep A. Your channel partner contributes a warm introduction, so you assign it to Rep B as well. The deal sits in Proposal for 12 weeks. Your partner closes a contract with the customer's legal team, so you add Rep C. Now the deal is assigned to three people. Your forecast triple-counts it: ₹2M × 3 = ₹6M in the system, but it's still one ₹2M deal. By the time you close it, your Q3 forecast is ₹40M, reality was ₹28M, and finance is asking why your forecast accuracy is 70%. Pipedrive has no deal-routing rules. No way to say "Enterprise segment deals must have one owner." No way to lock ownership once a deal passes $500K ACV. No way to auto-alert when a deal has more than two stakeholders. Enterprise sales require deal governance. Pipedrive offers deal chaos with a friendly UI. Stage design doesn't match your real cycle When you built your Pipedrive pipeline in year one, you copied HubSpot's standard: Prospecting → Qualification → Proposal → Negotiation → Won. That was fine when your ACV was ₹500K and deals closed in six weeks. Your enterprise deals now take 18 weeks, and they don't move linearly. A ₹10M deal might enter Proposal at week six (you've qualified), then move back to Qualification at week ten because the customer's CFO demands a second business case. Pipedrive stages are sequential—moving backward is weird and rarely happens, so people just leave the deal in "Proposal" while it's actually re-qualifying. Your stage definitions are now fiction. Real enterprise cycles look like: Lead → Qualify (3 weeks) → Discovery (4 weeks) → Design (6 weeks) → Proposal (4 weeks) → Legal (8 weeks) → Signature (1 week). Some deals skip Design. Some loop back from Legal to Proposal. A few restart at Discovery when a new champion joins. Pipedrive's linear model can't represent this. You end up cramming complexity into stage names ("Proposal / Legal" becomes the de facto bucket), and your forecast becomes noise because the stage definitions don't mean anything consistent anymore. What exports cleanly (and what dies) When you decide to migrate from Pipedrive to Salesforce or Orin, here's what you'll recover: Contacts and companies: Name, email, phone, address, custom fields—all export as structured CSV. Plan two hours of field mapping, one hour of deduplicatio