Glossary
Opportunity
By Emil Björk · Microsoft business apps consultant, Gothenburg
A qualified sales pursuit in Dynamics 365 Sales — moves through stages from qualify to close, with estimated revenue and probability.
An opportunity in Dynamics 365 Sales is a qualified, in-progress sales pursuit — a real deal with a customer, an estimated value, a likely close date, and a probability of winning. Opportunities are the pipeline: the sum of open opportunities, weighted by their probability, is what a sales forecast is actually built from. Each opportunity moves through configurable business process flow stages — typically Qualify → Develop → Propose → Close — with stage-gated fields capturing the deal's evolution, so a deal can't slide into "Propose" without the fields that stage requires (a proposed amount, a decision date) already being filled in.
In practice, an opportunity is where the CRM data model earns its keep as more than a contact list: it links to Accounts and Contacts, accumulates activities (calls, meetings, emails) automatically as they're logged, and can include product line items with quantities and prices that roll up into the estimated revenue figure rather than requiring the salesperson to type a number by hand. That structure is also what makes forecasting meaningful — sales forecasting rolls opportunities up by manager hierarchy, so a sales leader sees a real, editable roll-up of every rep's pipeline rather than a spreadsheet someone compiled manually, and AI-predicted insights layer on top to flag deals that look at-risk (gone quiet, past their expected close date) or high-momentum (rapid activity, strong signals) based on patterns in the underlying activity data.
Where confusion shows up: an opportunity's close as Won or Lost is often treated as the end of the record's usefulness, but both outcomes carry real information forward — a Won opportunity typically converts to a Quote, Order, or Invoice, continuing the same customer relationship into fulfilment, while a Lost opportunity is expected to carry a coded loss reason (price, competitor, timing, no decision) specifically so that pattern can be analysed later. A sales team that closes opportunities as Lost without ever coding why is throwing away the one dataset that would tell them what's actually costing them deals.
Related terms
Mentioned in these guides
- Account hierarchies in Dynamics 365
- Aging reports in Business Central
- Bulk delete jobs in Dataverse
- Projects in Business Central
- Business Central vs Dynamics NAV
- Business process flows in Dynamics 365
- Calculated and rollup columns in Dataverse
- Cascading delete in Dataverse
- Case management deep dive in Dynamics 365 Customer Service
- Connection records in Dataverse
- Consolidations in Dynamics 365 Finance
- Conversation Intelligence in Dynamics 365 Sales
- Copilot across Dynamics 365
- Copilot agents vs Copilot Studio
- Copilot for Sales features
- Customer Insights – Data explained
- Customer Insights – Journeys explained
- Customer Insights – Journeys vs HubSpot
- Customer Voice survey integration with Dynamics 365
- Customer Voice surveys in Dynamics 365
- Dataverse alternate keys
- Dataverse data model fundamentals
- The Dataverse security model
- Document templates and Word mail merge in Dynamics 365
And 60 more — this term shows up across the library.