Deal movement
Find out why a deal's expected close date moved, using the change history your sales tool keeps and a simple log.
A moved close date raises a question rather than answering one. These guides show where your sales tool records each change and how to log the reason, so the forecast call can talk about evidence instead of guesses.
Deal movement
Recover a deleted rep's Microsoft 365 mailbox in 30 days
Find a deleted rep's Microsoft 365 mailbox on the Deleted Users page, plan around the 30-day limit, and protect deal files and forecast history.
Closed deal record changes: 3 things to log later
Three things to record when a closed deal's stage, term, or invoice balance changes later, so revenue reviews can explain each move.
Close-date imports: 6 checks for date errors
Check close-date imports for rewritten years, swapped dates and clock-time errors. Use six checks, test rows and stored CRM values before uploading.
CSV deal export: 5 checks before loading a table
Five checks to run on a CRM deal export before loading it into a table, covering bad rows, footer lines, filters, special numbers and review.
3 time zone checks before you trust a deal close date
Three checks to confirm a deal close date lands on the same day in your CRM, database and forecast across time zones and daylight saving rules.
Seat overage after a mid-term upgrade: 3 figures
Track the 3 figures behind a seat overage after a mid-term upgrade, record the seat cut, and prepare a deal review with dated evidence.
GitLab order processing dates: 4 published rules
GitLab's published handbook sets 4 order rules: stage before submit, a 30-day quote start window, close date changes, and a $1.00 PO match.
Stalled deal benchmarks: 2 survey figures to compare
Salesloft's estimated 19.7% pipeline disruption share and approximately 32% instant diagnosis rate, with survey scope and practical review steps.
Stale deals: 5 checks before your next forecast call
Review stale deals before your forecast call with five checks for idle records, follow-up reminders, deal changes, activity logs and CRM hygiene.
ISO week dates: 3 checks before a close date load
Check ISO week and day-of-year strings, and mixed fields, before loading close dates from spreadsheets or database exports into your CRM.
Zoho Mail forwarding limits: 3 caps before a handoff
Zoho Mail allows 3 admin-added and 3 user-added destinations, for 6 total. Check each mailbox's counts and forwarding rules before a rep handoff.
Mid-term upgrade deal amount: 4 steps to explain it
Split a mid-term upgrade by date, value each part at its own price, check which price the credit uses, and decide on a term reset.
Deal risk scores: 2 rules before the review call
Use two HubSpot example risk score rules to prepare deal reviews: more than 14 days without activity and three or more close date pushes.
CRM logging: 4 habits to keep deal records current
Keep deal records current with four CRM logging habits: follow new leads, check call and SMS records, create leads from email, and test Kanban.
Deal change records: 3 tools and their limits
Compare Box, Dropbox, and Box Notes for deal change records, including version limits, editor attribution, and a practical logging routine.
Quote expiry checks: 5 steps before you move a close date
Five checks for revenue leaders deciding whether a close date should move: a quote's purpose, expiry, extension, billing limits and follow-up.
Microsoft 365 audit log retention: 5 rules to check
Check five Microsoft 365 audit log retention rules, including qualifying user licenses, historical default periods, ten-year add-ons and policy limits.
Dynamics 365 task sync: 5 checks for missing tasks
Check five Dynamics 365 task sync rules, from two-way sync to filter matches, to trace why a task disappeared from a rep's Exchange mailbox.
Cancellation billing day: 8 steps to check credit
Check cancellation billing days in 8 steps using Chargebee's example: compare timestamps, identify the billing window, and check the $110 credit.
Stripe subscription schedule phase limit: up to 10 phases
Stripe allows up to 10 current or future phases on one subscription schedule. Check each planned change against that cap before it enters the forecast.
STL settings for a monthly bookings trend: 4 checks
Check four STL settings before reading a monthly bookings trend: data frequency, the seasonal default of 7, COMPONENT_deg, and jump size limits.
Reopen a won or lost deal in 5 CRMs: what to re-check
See how 5 CRMs handle reopened deals, what resets for close dates and probability, and the specific checks to run before your next forecast call.
Pipedrive deleted products: check the 30-day restore window
Check Pipedrive's 30-day restore window for deleted products and 1,000-product cap before trusting a software deal's total. Compare rules across four tools.
Compare close dates: 3 rules for date and time fields
Three rules for comparing close dates across date, timestamp, time and interval values, plus a proration caveat for reading moves.
Stalled deal alert: 6 steps to set it up in your CRM
Set up a stalled deal alert in six steps: pick the inactivity rule, check your plan, attach an action, set the delay and send window.
Funnel chart totals: 3 metrics and why deals repeat
Why a funnel total can count one deal in several stages, and how to tell count, annualized value and weighted value columns apart before you quote it.
Close date mismatches: 5 mistakes in forecast records
Five date interpretation mistakes can make close dates disagree in forecast reports. Check these before calling a mismatch deal movement.
Date and time formats: 4 tools for forecast exports
Compare documented date entry and time storage rules in Sheets, Dataverse, Freshsales, and Pipedrive for forecast close-date preparation.
Deal link caps: 10,000 in HubSpot, 1,000 in Close
HubSpot's custom association ceiling goes up to 10,000, Close allows 1,000 opportunities on each lead, and Microsoft needs an account or contact.
Stale deal signals: 5 publishers to check before the call
Compare how Freshsales, Pipedrive, HubSpot and Close flag stale deals, and what Microsoft's seven-day refresh does, before your weekly forecast call.
Catalog price before the software deal total: 2 checks
Check two prices, the catalog unit price and the deal price, in Pipedrive and HubSpot before you read the weekly software deal total.
Activity linking cap: 2,000 activities and 5 deals
Check the 2,000 activity cap and the five-deal linking rule in HubSpot before the weekly call, so a missing note is not read as a quiet deal.
Due date checks for sales follow-ups: 8 rules
Run 8 date checks so follow-up tasks and forecast close dates stay aligned across Close, Trello, Todoist, Google Docs, and Microsoft.
Check deal stage duration across 4 CRM tools
See how Freshworks, Pipedrive, Microsoft, and HubSpot show stage time, report limits, and when a progress bar stops after a win.
Stage duration: 8 checks before the weekly call
Check eight duration and history measures across four CRM tools, including completed-stage timing, change logs and reporting rules before the weekly call.
Deal field edit history: 6 Freshsales tracking rules
Review 6 Freshsales field history rules, from selecting deal fields in admin settings to viewing changes and old and new values for related contacts.
Verify 8 date and score rules for forecast accuracy
Verify 8 date and score rules in HubSpot, Pipedrive, Freshworks, and Microsoft Dynamics so the weekly forecast uses current close dates and scores.
Forecast rules for verbal commitments: 7 rules
Use 7 forecast rules to reflect verbal commitments, paused deals, and known risks before opportunity data is updated in the system.
Deal forecast months: date rules across 4 tools
Check date rules across Microsoft, HubSpot, Pipedrive and Close, distinguishing forecast schedules, revenue dates and filters for won deals.
Quota line checks across 4 sales publishers
See four documented quota checks: a hand-uploaded Microsoft column, a HubSpot goal gap, a Freshsales manager line, and a Nutshell user and fiscal year.
Assign leads equally across 5 CRM platforms
Compare equal lead assignment on five CRM platforms, including territory rules, Away users, condition limits, and round-robin checks before a forecast call.
Required-field rules in 4 tools before stage change
Compare required-field rules in HubSpot, Pipedrive, Microsoft, and Zoho, including which checks block a stage change and which paths do not.
Quote checks before the forecast call: 4 tools
Check Dynamics 365 draft and revision ID, HubSpot primary quotes, Pipedrive document versions, and Zoho insert-record fields before a forecast call.
Meeting reminder and booking rules in 4 tools
See when Close shows a meeting reminder, which calendars it syncs, and the HubSpot, Pipedrive, and Microsoft booking rules to check.
Weekly deal review filters across 4 sales systems
Save a weekly deal review view in HubSpot, Pipedrive, Microsoft, and Close. Check ALL or ANY groups, who can see the view, and documented limits.
Sales follow-up checks for 4 task attributes
Check the next sales follow-up for due time, linked record, assignee, and completion state, using documented rules from four sales tools.
Recover deleted sales records: 4 CRM restore rules
Compare recovery windows, permissions, and exclusions across HubSpot, Pipedrive, Microsoft Dataverse, and Close before restoring deleted sales records.
Find deal attachments: 4 publisher rules to check
Check four publisher rules for where a sales file sits, who can open it, what the display shows, and how long a shared link stays open.
Check the buying company on a deal: 5 record limits
Verify the buying company and linked people on a software deal using five tools' stated limits before your next forecast call.
What 3 systems store on a lost deal: 6 fields
See which six fields HubSpot, Pipedrive, and Microsoft store on a lost deal, and what to fill in before your next review.
Open, won, and lost stage rules in 4 sales tools
HubSpot, Close, and Pipedrive rules for open, won, and lost stages, plus the two Open reasons Microsoft names, before your forecast call.
Close date change log: why the date moved
Build a blank close date change log from vendor documentation so a forecast call can record why a deal's expected close date moved.