Read recorded opportunity stage transitions
Inspect recorded before-and-after stages, approved changes and creation entries without reconstructing missing history.
Where to goSales CRM → Opportunity → Deal history → View stage transitions
Before you start
Use your own authorised staff account in the intended Pixie CRM workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.
Follow these steps
- Open an accessible opportunity and choose View stage transitions in Deal history.
- Read entries from newest to oldest. Each card shows its action, time, source stage and pipeline, entered stage and pipeline, actor and opportunity version.
- Use Older entries to read the next page of up to 50 entries; choose Newest entries to return to the latest page.
- Choose Export this page to download only the displayed entries.
- Use Back to opportunity to return to normal opportunity details.
Behavior and limits
- Structured history starts when this feature records a creation or completed stage change. Existing opportunities do not receive an invented historical baseline. Earlier readable activity history remains available separately.
- A successful creation records its starting stage. A stage change saved through Edit details records Saved stage change. A completed move records Stage change, including moves performed through existing bulk-stage workflows.
- A controlled-stage request does not create a transition while approval is pending. A completed approval records Approved change. Rejected requests and no-op moves do not create stage entries.
- Stage entries are saved in the same transaction as the opportunity change. A failed save rolls back both the change and its new entry. Retrying an already-completed create does not duplicate history.
- Ordinary detail edits, archive/restore actions and report reads do not manufacture stage entries. Archived opportunities retain their recorded history under normal current access rules.
- Stage and pipeline labels on history cards reflect the labels captured when the entry was recorded. Later renaming does not rewrite those captured labels. Actor names are resolved from the current staff record; unavailable staff use a fallback label.
- Reading history does not let you change, approve or delete transitions. It does not widen opportunity visibility.
- History pages contain at most 50 entries. The cursor moves to older entry identifiers so entries do not overlap between normal pages. Export this page is not an export of all history.
- Changes made outside the native Sales CRM save/move/approval workflows, including direct database writes, do not automatically create these structured entries.
Check it worked
- Compare the Entered stage with the next newer entry’s From stage when following a normal sequence.
- Check the action badge to distinguish a completed approval from a normal stage change.
- Check the export’s entry count and opportunity identity.
- Return to the opportunity to inspect its current stage rather than assuming the newest historical milestone is a permanent outcome.
Troubleshooting
- No entries yet can be expected for opportunities that existed before tracking and have not changed stage since.
- For older activity without a structured card, use the existing Deal history; the system does not infer machine-readable transitions from its prose.
- A missing pending request is expected: only completed stage changes enter this view.
- If the opportunity is unavailable, check current ownership and Sales CRM access.
- For an interrupted load, reopen the view. Responses for a closed or replaced dialog do not overwrite another dialog.