Skip to main content

Leads v Opportunities in Microsoft Dynamics CRM





When my company InfoStrat implements Dynamics CRM for a client, one of the first questions we are likely to hear is when to use the Leads entity and when to use Opportunities.

Leads is a smaller entity whose fields include topic, name, job title, email, company name, phone numbers and address.

Opportunities has topic and name information along with more fields such as the estimated close date, estimated revenue, and win probability.  It is related to Accounts and Contacts, and has lookups into each of these related entities.

The following are my thoughts on when to use each:

  1. Leads are for prospecting.  This is where you would put a mailing list from business cards that you gather at a trade show, or website visitors who register for an event or white paper.
  2. I don't mind having a large number of leads even knowing that most will never convert to opportunities.  In general, I do not want to clutter up my Accounts and Contacts with those low probability customers.
  3. Opportunities are won or lost, but you would not want to count leads that go nowhere in the same way as a proposal that was lost.  This is a good reason to distinguish between leads and opportunities. 
  4. Opportunities are the heart of sales activity.  You will use opportunities as the basis for sales pipeline meetings, and a trigger to check in with customers and prospects regarding opportunities and bids.  
  5. If you know the value and estimated date for a customer purchase, it is an opportunity rather than a lead.  Leads have much more uncertainly around them than opportunities.  
Microsoft Dynamics CRM has a built-in function to convert a lead into an Account, Contact, and Opportunity record.  This process is used during the qualification process.  Once you understand that the prospective customer has a demonstrated interest in a specific offering, you may want to convert the lead to an opportunity. 

You can build marketing lists for both leads and contacts (as well as accounts).  This means that you may end up with a parallel set of marketing lists for each.  Be sure to send marketing outreach to both leads and contacts where appropriate.

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan