CRM tools calculate stage duration differently based on whether they track cumulative pipeline age or time in the current or completed stage. HubSpot defines "Time in current stage" as the time the record has spent in the current pipeline stage. Freshworks tracks the total duration a deal has existed in the sales pipeline from its creation to its current position using the Age in Days metric.
Direct answer: separate cumulative pipeline age from current or completed stage time
Sales operations managers auditing pipeline bottlenecks must distinguish between cumulative pipeline age and time in the current or completed stage. These two metrics answer different questions about deal velocity. Cumulative age measures the total lifespan of a record within the system, while specific stage duration measures how long a record has resided in its current position.
HubSpot provides a calculated property that isolates the time a record has spent in the current pipeline stage. This metric focuses exclusively on the active stage, ignoring prior stages. It allows managers to see how long a specific deal has been sitting in its present state without the noise of earlier pipeline phases.
Freshworks uses the Age in Days metric to track the total duration a deal has existed in the sales pipeline. This measurement runs from the deal's creation to its current position. It represents the cumulative time spent across all stages, not just the current one.
The distinction matters for forecasting accuracy. A fast current stage can sit beside a high cumulative age only when the deal entered that stage recently. Conversely, a deal with a low cumulative age might be stuck in its current stage if it was created recently and has not moved. Mixing these metrics can obscure true bottleneck locations.
This difference requires separate analysis for each platform. You cannot directly compare a HubSpot "Time in current stage" value with a Freshworks "Age in Days" value as equivalent metrics. One measures the current stage's duration, while the other measures the deal's total lifespan.
Key takeaways for how to track deal stage duration in crm tools
- Close creates Opportunity Status Change activities when you change an Opportunity’s status, according to Close.
- Microsoft defines the active stage identifier as the unique identifier of the active stage for the Business Process Flow instance, according to Microsoft.
- Freshworks excludes the current stage's duration from its metric, which only becomes available once the deal moves to the next stage, according to Freshworks.
- Freshworks tracks the total duration a deal has existed in the sales pipeline with the Age in Days metric, according to Freshworks.
- Freshworks measures the time a deal spent in each completed stage of the sales pipeline with the Days in Stage metric, according to Freshworks.
HubSpot current stage time and Freshworks completed stage days
HubSpot and Freshworks use distinct logic to measure how long a deal remains in a specific pipeline stage. Understanding these differences is essential for accurate forecasting, as the two platforms define "time in stage" in ways that produce different data points for the same deal.
In HubSpot, the "Time in current stage" property calculates the duration a record has spent in its current pipeline stage, according to HubSpot. HubSpot also notes that these calculated properties automatically update based on a record's current and historical stage values, meaning if a deal is closed and then reopened, the values will continue to update, reported by HubSpot. This automatic recalculation ensures that the duration reflects the most recent state of the deal without manual intervention.
Freshsales Analytics handles stage duration differently by separating total pipeline age from completed stage time. The "Age in Days" metric tracks the total duration a deal has existed in the sales pipeline, from its creation to its current position, as stated by Freshworks. This cumulative measure helps sales operations managers identify deals that have been open for extended periods regardless of their current stage.
For specific stage analysis, Freshworks uses the "Days in Stage" metric, which measures the time a deal spent in each completed stage of the sales pipeline, according to Freshworks. Crucially, the current stage's duration is not included in this metric and only becomes available once the deal moves to the next stage, reported by Freshworks. This distinction means that Freshworks provides a historical view of completed stages, while HubSpot provides a live view of the active stage.
When auditing your data, note that Freshworks Days in Stage measures the time a deal spent in each completed stage, and the current stage is omitted until the deal moves to the next stage, while HubSpot Time in current stage is the time the record has spent in the current pipeline stage. To align your reports, you must decide whether you need live active time or historical completed time. If you need to track bottleneck stages in real-time, HubSpot's updating property is the relevant field. If you need to analyze average duration for past stages, Freshworks' completed stage metric is the appropriate source. Verify which metric your team uses for forecasting to ensure consistency.
Open your CRM's reporting module and locate the specific field or property that tracks 'Time in Current Stage' to verify if it updates in real-time or only upon stage transition.
Pipedrive and Microsoft: Reporting on stage movement and active processes
Pipedrive provides specific reporting tools to track how deals move through your pipeline. The Insights deal progress report allows you to view the movement of your deals through stages within a specified time frame, showing how well your deals are progressing through your sales cycle, as reported by Pipedrive. When you measure by the number of deals, you’ll see the number of deals that have entered each stage in the timeframe selected, according to Pipedrive. It is important to note that the entered stage deal count also includes deals that have skipped that stage while moving on to a future stage, as stated by Pipedrive. For example, if a deal has moved from stage two directly to stage five in the time frame selected, it will show as having entered stages three, four and five, according to Pipedrive. This logic ensures that the report reflects the full path of the deal's progression rather than just the stages where it physically paused.
In the deal’s detail view, you‘ll find the deal progress bar, showing you what pipeline stage the deal is currently at and the number of days it took to complete each stage, as documented by Pipedrive. This visual element provides a quick snapshot of historical stage duration for individual opportunities.
Microsoft Dynamics 365 uses a different approach by tracking the active stage of a business process flow. The Opportunity Sales Process table contains a unique identifier of the active stage for the Business Process Flow instance, according to Microsoft. Microsoft provides best practices for using the Active Stage (activestageid) column on the business process flow table, as outlined by Microsoft. One specific application of this data is to send an email to a user if the Qualify the stage of the Opportunity Sales Process is active for longer than 15 days, as suggested by Microsoft. This allows you to set up automated alerts based on how long a deal remains in a specific stage, helping to identify potential stalls in the sales process.
When auditing your CRM, verify how your specific platform handles skipped stages. If your tool uses a logic similar to Pipedrive's Insights report, ensure your team understands that skipped stages are counted in the entered stage totals. If you use Microsoft Dynamics 365, check the activestageid column to see which stage is currently active for each opportunity. These distinct methods of tracking stage movement require different approaches to data interpretation. Review your current reporting setup to confirm how skipped stages and the active stage identifier are recorded. Adjust your dashboard metrics to align with the specific calculation logic of your chosen platform to avoid misinterpreting deal velocity.
A filled reference table of pipeline fields by publisher
The table below lists the eight specific fields and metrics tracked across the five platforms. Each row isolates a single calculation logic or behavior, ensuring you can audit your pipeline without conflating cumulative age with completed stage days.
| Publisher | Field or Metric | Calculation Logic or Behavior | Source Document |
|---|---|---|---|
| HubSpot | Time in current stage | The time the record has spent in the current pipeline stage. | HubSpot |
| Freshworks | Age in Days | Tracks the total duration a deal has existed in the sales pipeline from creation to its current position. | Freshworks |
| Freshworks | Days in Stage | Measures the time a deal spent in each completed stage of the sales pipeline. | Freshworks |
| Pipedrive | Progress report | Views the movement of deals through stages within a specified time frame to show sales cycle progression. | Pipedrive |
| Pipedrive | Skipped stages | If a deal moves from stage two directly to stage five, it shows as having entered stages three, four, and five. | Pipedrive |
| Microsoft | Active stage | Unique identifier of the active stage for the Business Process Flow instance. | Microsoft |
| Close | Status change | Opportunity Status Change activities are created when you change an Opportunity’s status. | Close |
| Freshworks | Edit history | Logs field data modifications for a duration of 6 months, with a maximum allowance of 50 fields. | Freshworks |
Handling edge cases: Skipped stages and reopened deals
Non-linear movement through a pipeline often confuses standard duration metrics, particularly when deals skip stages or revert to earlier positions. For Pipedrive, the system handles these irregular movements by relying on the most recent update to a deal’s stage. Specifically, Pipedrive progress reports use the most recent updates to deal stages, meaning if a deal is moved from Stage 2 back to Stage 1, the deal is represented in Stage 1 Pipedrive. This behavior means a deal moved from Stage 2 back to Stage 1 is represented in Stage 1. When auditing bottlenecks, account for a move from Stage 2 back to Stage 1, which the progress report represents in Stage 1.
If your team frequently moves deals backward in the pipeline, verify how your specific CRM tool records these reversals. While Pipedrive explicitly represents reverted deals in their current stage, other platforms may calculate cumulative time differently. For instance, some tools might retain the original entry date for a stage even if the deal leaves and returns, while others reset the timer. Check your own platform’s documentation for similar edge case rules.
To manage these edge cases effectively, follow these steps:
- Identify deals that have moved backward in the pipeline during the current quarter.
- Check the reporting view for those specific deals to see which stage they are currently attributed to in the system.
- Compare the reported stage duration against the actual time spent in that stage to identify any discrepancies caused by the reversal.
For Pipedrive users, the key takeaway is that the progress report reflects the latest state. If a deal moves from Stage 2 to Stage 1, it is counted under Stage 1 in the report Pipedrive.
When deals skip stages entirely, Pipedrive includes them in the counts for the skipped stages. The entered stage deal count also includes deals that have skipped that stage while moving on to a future stage Pipedrive. This rule applies when measuring by the number of deals, where you see the number of deals that have entered each stage in the timeframe selected Pipedrive.
Freshworks field edit history limits
Match each internal pipeline stage to the tracking field you use in your CRM. When selecting which fields to monitor, consider the retention and update limitations documented by your platform. For Freshsales, field edit history tracking applies to all field types, but there is a maximum allowance of 50 fields according to Freshworks. Additionally, the system can log and retain field data modifications for a duration of 6 months, as noted by Freshworks. Be aware that it may take up to 5 minutes for changes to show in the Deal fields' edit history, reported by Freshworks.
Check that the fields you monitor stay within the 50-field limit for Freshsales. Confirm your audit schedule accounts for the 6-month retention window and the 5-minute update delay.
Related guides
FAQ: How to track deal stage duration in crm tools
Does HubSpot update the time in current stage property while a deal is active?
Yes. HubSpot properties automatically update based on a record's current and historical stage values, as stated in the "Use stage calculated properties" documentation HubSpot. The system continues to update these values even if a deal or ticket is closed and then reopened.
How does Pipedrive handle deals that skip a pipeline stage?
Pipedrive counts skipped stages as entered in its deal progress reports. The "Insights reports: deal progress" documentation notes that the entered stage deal count includes deals that have skipped that stage while moving on to a future stage Pipedrive.
What is the maximum duration Freshworks retains for field edit history?
Freshworks retains field data modifications for a duration of 6 months, according to the "How to track Field Edit History of Deals?" guide Freshworks. This retention period applies to the logged field data changes within the CRM.
Can Microsoft Dynamics 365 report on the active stage of a business process flow?
Yes, the Opportunity Sales Process table contains a unique identifier for the active stage of the Business Process Flow instance. This is documented in the "Opportunity Sales Process (OpportunitySalesProcess) table/entity reference" Microsoft.
Does Close create activities when an opportunity status changes?
Yes, Opportunity Status Change activities are created when you change an Opportunity’s status, as described in the "Opportunity Status Changes" developer documentation Close.