Why CRM Setup Matters in Odoo 19
For many businesses, CRM is one of the first places where an Odoo implementation starts to feel real.
Leads come in. Salespeople follow up. Opportunities move through the pipeline. Quotations are created. Orders are confirmed. From there, the workflow can continue into delivery, invoicing, and customer management.
Because CRM sits so close to revenue, it is easy to treat it as a simple sales tool. Create a few stages, add some contacts, assign salespeople, and start moving opportunities across the pipeline.
However, that approach often creates problems later.
A poorly structured CRM does not just make the pipeline messy. It can cause missed follow-ups, weak forecasting, duplicate opportunities, inconsistent quoting, unclear ownership, and poor visibility for management.
Odoo 19 CRM gives businesses a flexible way to manage the sales process, but that flexibility needs to be designed carefully. The real value comes from configuring CRM around how the business actually sells, not just using the default setup and hoping the team adapts.
This article explains the core setup decisions behind Odoo 19 CRM and how they affect lead qualification, pipeline structure, opportunity ownership, and sales visibility.
The Role of CRM in Odoo
In Odoo, CRM is used to manage the front end of the sales process.
It helps businesses track leads, manage opportunities, schedule follow-ups, assign ownership, measure pipeline performance, and convert sales conversations into quotations.
One of Odoo’s biggest strengths is that CRM connects directly with the broader sales workflow. An opportunity can become a quotation. A quotation can become a sales order. A sales order can then connect to delivery, invoicing, and payment workflows depending on how the rest of the system is configured.
In practical terms, CRM is often the starting point of the lead-to-cash process.
That means CRM setup should be aligned with the business’s sales structure, quoting process, product setup, customer data, pricing strategy, and reporting needs.
When CRM is configured thoughtfully, it gives sales teams a clear process to follow and gives managers better visibility into what is happening before revenue is booked.
Leads vs Opportunities in Odoo 19
One of the first decisions to make when setting up Odoo CRM is whether the business needs a lead qualification step before opportunities enter the sales pipeline.
This distinction matters because leads and opportunities serve different purposes in Odoo.
A lead represents an early-stage sales contact or inquiry that has not yet been fully qualified. This could be a website inquiry, an email request, a marketing contact, or another potential customer that still needs to be reviewed before it becomes an active sales opportunity.
An opportunity represents a qualified sales possibility that belongs in the pipeline. At this stage, the sales team has enough information to begin actively working the potential deal, tracking follow-ups, and moving it toward a quotation or sale.
In Odoo 19, businesses can choose whether to enable the Leads feature from the CRM → Configuration → Settings.
When Leads are enabled, inquiries can be captured and reviewed before they can be converted into opportunities. This gives the business a qualification layer before the opportunity enters the main sales pipeline.
When Leads are not enabled, sales teams can work directly with opportunities. This creates a simpler CRM workflow and may be better for smaller teams or businesses with a straightforward sales process.
The right choice depends on how the business handles incoming demand.
If the company receives a large number of inquiries, has an SDR or qualification team, separates marketing leads from sales opportunities, or needs to screen leads before assigning them to account executives, using Leads makes sense.
If the company has a smaller sales team, fewer incoming inquiries, or a more direct sales process, working directly with opportunities may be cleaner.
Sales Teams and Pipeline Ownership
After deciding whether to include leads in your pipeline, the next major configuration area in Odoo CRM is sales teams.
Sales teams are managed from CRM → Configuration → Sales Teams. From this menu, a company can create teams, assign team leaders, add salespeople, configure email aliases, and manage how leads or opportunities are organized.
How to Configure a Sales Team
In Odoo, a sales team represents a working group inside the CRM. Sales teams can be used to separate sales activity by department, region, product line, sales channel, or sales process.
When configuring a sales team, the first field is the Sales Team name. This name should clearly describe the purpose of the team, such as Outbound Sales, Inbound Sales, Service Sales, or Regional Sales. The name selected here is what users will see when assigning leads, opportunities, and reviewing team activity.
Below the sales team name, Odoo includes options for Pipeline and Leads.
The Pipeline option allows the sales team to manage opportunities through a sales pipeline. When this is enabled, the team can work with opportunities as they move through different pipeline stages.
The Leads option allows the team to manage leads before they are converted into opportunities.
These two options help define how the team will work inside the CRM. Some businesses may work directly with opportunities, while others may use leads first and convert them once they are qualified.
In the Team Details section, the Team Leader field assigns the person responsible for managing the sales team. This user is typically responsible for reviewing the team’s pipeline, monitoring follow-up activity, and keeping opportunities organized.
The Email Alias field allows incoming emails to create CRM records for the team. For example, a company could configure an alias such as outboundsales@email.com. When emails are sent to that address, Odoo can route them into the CRM for that sales team.
The Accept Emails From field controls who is allowed to send emails to that alias. This helps determine whether the alias is open to everyone or restricted to specific users, partners, followers, or employees. For sales teams that receive external inquiries, this setting should be reviewed carefully so the alias works as intended.
In multi-company environments, the Company field can be used to assign the sales team to a specific company. If the field is left visible to all, the sales team is not limited to one company. This is useful in simpler databases, but businesses with multiple companies may need to separate sales teams by company for cleaner reporting and access control.
The Invoicing Target field allows the business to define a monthly revenue target for the sales team. This target can then be used in the sales team dashboard to compare actual invoicing progress against the team’s goal.
The Members tab is where salespeople are added to the team. These users are the people who can work within that team’s pipeline and may be assigned leads or opportunities.
Odoo also includes a Multi Teams setting, which allows the same salesperson to belong to more than one sales team. This setting can be enabled from CRM → Configuration → Settings.
When Multi Teams is enabled, a salesperson can be added as a member of multiple teams. This is useful when a user supports more than one sales process, region, product line, or channel.
Sales teams are important because they influence how CRM activity is structured. Instead of managing every opportunity in one general pipeline, businesses can separate activity by team when different groups follow different sales processes.
How to Assign a Sales Team to a Lead or Opportunity
Once sales teams are configured, the next step is assigning leads and opportunities to the correct salesperson and team.
When working from a Lead, the assignment fields are available directly on the main lead form.
To assign ownership:
- Open the lead from the CRM app.
- Locate the Salesperson field.
- Select the user who should own and follow up on the lead.
- Set the Sales Team field to the appropriate team.
This ensures the lead is visible to the right team and appears correctly in CRM reporting before it is converted into an opportunity.
Once a lead becomes an Opportunity, the Salesperson field appears on the main opportunity form, usually beside the expected closing date and tags. This is where you assign the individual responsible for moving the deal forward.
The Sales Team field is found under the Extra Information tab, in the Tracking section. From there, you can choose which sales team owns the opportunity.
Once the salesperson and sales team are assigned, the opportunity is properly connected to both the individual responsible for follow-up and the team pipeline it belongs to.
When sales teams are configured properly, Odoo CRM becomes easier to manage. Leads and opportunities are assigned to the right people, pipelines stay organized, and managers can review sales activity by team instead of relying on one generic sales view for the entire business.
Designing Pipeline Stages
Pipeline stages are one of the most visible parts of Odoo CRM.
They appear as columns in the Kanban view and represent the steps an opportunity moves through during the sales process.
A well-designed pipeline helps salespeople understand what needs to happen next. It also helps management understand where deals are sitting, which deals are stuck, and how much potential revenue is moving through the business.
A stage should not simply describe where the opportunity is sitting. It should define what must be true for the opportunity to belong there.
To create a new stage, open the CRM pipeline view and use the add stage option at the end of the Kanban view. Odoo will create a new column where the stage name can be entered.
Once the stage is created, it can be moved into the correct order by dragging it to the appropriate position in the pipeline. This order should match the way opportunities actually move through the sales process.
If a stage is no longer needed, it can be removed by clicking the gear icon beside the stage title and selecting Delete.
Before deleting a stage, any active opportunities in that stage should be reviewed and moved to the correct remaining stage. This helps avoid confusion and keeps the pipeline clean.
Stages should not be added or removed casually. Each stage should represent a real sales milestone that the team understands and uses consistently.
Stage Configuration Options
After pipeline stages are created, each stage can be configured in more detail.
To configure a stage, select the gear icon beside the stage title and select edit.
These settings control how the stage appears in the pipeline, which sales teams can use it, how Odoo treats opportunities in that stage, and whether the stage should be considered active, won, or stale.
The Stage Name field defines the name of the pipeline stage. The stage name appears as a column in the CRM pipeline.
The Folded in Pipeline option controls whether the stage is collapsed by default in the Kanban view when there are no records in that stage.
The Color field allows a color to be assigned to the stage. This is mainly a visual aid and can help users identify or separate stages more easily in the pipeline.
The Sales Teams field controls which sales teams can use the stage. This is important when different sales teams follow different sales processes.
The Is Won Stage option identifies whether the stage should be treated as a successful outcome. This should be enabled for a stage that represents a won opportunity. It should not be enabled for active working stages, such as Discovery or Proposal Sent.
The Days to Rot field is used to identify stale opportunities. This value defines how many days an opportunity can remain in the stage without movement before it is considered inactive or at risk.
For example, if the Days to Rot value is set to 5, opportunities that remain in that stage for more than five days without progress can be flagged as stale. This helps sales teams identify deals that may need follow-up or cleanup.
Opportunities that become stale are highlighted in red, and Odoo indicates how many days they have remained inactive.
The Requirements section allows the business to describe what requirements should be met before an opportunity belongs in that stage.
Together, these configuration options help define how each stage should behave in the pipeline. When stages are configured properly, opportunities are easier to manage, stale deals are easier to identify, and each sales team has a clearer view of the opportunities that matter to them.
Understanding the Opportunity Record
Once leads, sales teams, and pipeline stages are configured, the next step is understanding the opportunity record itself.
The pipeline shows where an opportunity sits in the sales process, but the opportunity form contains the information needed to actually manage the potential deal.
At the top of the opportunity form, the Opportunity Name should clearly describe the potential sale. This may be the customer’s name, the project name, the product interest, or a short description of the deal.
The Expected Revenue field represents the estimated value of the opportunity. This amount is used in CRM reporting and forecasting, so it should be entered consistently.
The Probability field reflects the likelihood that the opportunity will be won. Depending on how the CRM is configured, this may be adjusted manually or influenced by Odoo’s probability logic.
The Contact field links the opportunity to an existing customer or contact. This is important because it connects the opportunity to the customer’s broader history in Odoo, including quotations, sales orders, invoices, emails, and other records.
The Email and Phone fields store the main contact details for the opportunity, making it easier for the salesperson to reach the prospect directly from the CRM record.
The Salesperson field identifies the individual responsible for moving the opportunity forward. This user is accountable for follow-up and progression through the pipeline.
The Expected Closing date helps define when the opportunity is expected to close. This field is especially important for forecasting because it gives managers a time-based view of expected sales activity.
Tags can be used to classify opportunities with additional context. For example, tags may identify product interest, service type, priority, industry, lead source, campaign, or customer segment.
The Priority indicator (stars) allows salespeople to visually flag important opportunities. This can help users quickly identify deals that require attention, although it should not replace proper qualification or pipeline management.
The Contacts tab stores additional company and contact details related to the opportunity, such as the company name, address, contact person, job position, and website. This helps keep the opportunity connected to the correct business and decision maker.
The lower section of the opportunity form provides additional context about the company, contact, marketing source, and ownership.
The Marketing section helps track how the opportunity was generated. The Campaign field identifies the specific marketing effort connected to the opportunity, such as a product email campaign, seasonal promotion, or event campaign.
The Medium field describes the channel used, such as email, website, social media, or phone. The Source field identifies the specific origin of the opportunity. This could be a search engine, newsletter, referral, LinkedIn, live chat, chatbot, website page generator, or another source configured in Odoo.
The Referred By field can be used when the opportunity came from a specific person, partner, or customer referral.
The Ownership section identifies which company and sales team are responsible for the opportunity. This is especially important in multi-company environments or when different sales teams manage different pipelines.
Keeping Opportunity Data Consistent
Configuring the CRM is only the first step. For the system to remain useful, opportunity data needs to be entered consistently.
A pipeline can look organized visually but still produce unreliable reporting if users do not maintain the underlying fields properly.
For this reason, businesses should define how opportunity fields should be used before the CRM is rolled out to the team.
The business should decide when expected revenue should be entered. Some companies may enter it as soon as an opportunity is created, while others may wait until the opportunity is qualified.
The business should also decide how expected closing dates should be maintained. If every active opportunity is expected to have a closing date, that expectation should be communicated clearly to the sales team.
Tags should be standardized where possible. If tags are used to classify opportunities by product line, service type, industry, or lead source, the company should avoid allowing every user to create slightly different versions of the same label.
The same principle applies to customer records. If salespeople create duplicate customer contacts or use inconsistent naming, the CRM can quickly become harder to manage.
Consistent opportunity data is what makes the CRM useful beyond the individual salesperson.
It allows managers to review the pipeline, compare team performance, understand expected revenue, and identify where opportunities are getting stuck.
Without consistent data, the CRM may still contain opportunities, but the business will struggle to use that information for decision-making.
Classifying Opportunities with Tags and Source Information
Not every difference in the sales process needs a new sales team or pipeline stage.
In many cases, opportunities can be organized more effectively using tags, campaign details, and source information.
This is an important distinction when designing CRM structure.
Sales teams should generally be used when ownership, workflow, or reporting responsibilities are meaningfully different. Pipeline stages should represent the steps an opportunity moves through during the sales process.
Tags, campaigns, mediums, and sources can be used to add context without changing the structure of the pipeline.
For example, a business may use tags to identify:
- Product interest
- Service type
- Industry
- Priority level
- Customer segment
- Event source
- Campaign name
- Implementation type
- Renewal opportunity
- Upsell opportunity
These labels help users filter, group, and analyze opportunities without creating unnecessary pipeline complexity.
A new sales team should not be created every time the business wants another reporting angle. A new pipeline stage should not be created every time the business wants another classification.
In many cases, tags, campaigns, mediums, and sources are the better tools for classifying opportunities without adding unnecessary sales teams or pipeline stages.
When used properly, they add useful context while keeping the pipeline easier to manage.
Setting Up Lost Reasons and Pipeline Outcomes
A complete CRM setup should define not only how opportunities move forward, but also how they are closed.
In Odoo CRM, opportunities can be marked as won or lost.
A Won opportunity represents a successful outcome. This means the potential deal has been accepted and should no longer be treated as an active opportunity in progress. When the pipeline is configured with a won stage, these opportunities can be moved into that stage and treated as completed.
A Lost opportunity represents a deal that did not move forward. When an opportunity is marked as lost, it is removed from the active pipeline view and can be reviewed later using the Lost filter. This keeps inactive deals from cluttering the pipeline while still preserving the record for reporting and review.
Marking opportunities as lost is important because it keeps the pipeline clean and gives the business useful information about why deals are not closing.
If opportunities are only archived without being properly marked as lost, the business may lose visibility into why the opportunity failed.
Lost Reasons allow the company to categorize why an opportunity did not close. They can be configured through CRM → Configuration → Lost Reasons.
Lost reasons are most useful when they are standardized.
If every salesperson creates their own version of the same reason, reporting becomes difficult to interpret. For example, “Too expensive,” “Price,” “Budget issue,” and “Cost” may all describe a similar issue, but they may appear as separate reasons in reporting.
For that reason, businesses should define a controlled list of lost reasons before the CRM is used heavily.
The goal is not to create dozens of options. The goal is to create enough categories to understand why opportunities are being lost without making the list difficult for users to apply.
Clear pipeline outcomes help keep CRM reporting meaningful. Won opportunities show what succeeded. Lost opportunities show what did not. Lost reasons help explain why.
Preparing CRM for Reporting
CRM reporting starts long before a manager opens a report.
It starts with how leads, opportunities, sales teams, stages, tags, and outcomes are configured.
Odoo CRM can provide visibility into pipeline value, expected revenue, sales team performance, opportunity progress, and lost opportunities. However, the quality of those reports depends on the quality of the information entered into the CRM.
For CRM reporting to be useful, businesses should define which fields are important and how they should be maintained.
At minimum, most businesses should create discipline around the following fields:
- Salesperson
- Sales Team
- Stage
- Expected Revenue
- Expected Closing Date
- Customer
- Tags
- Lead Source
- Lost Reason
These fields help answer important management questions.
When the CRM structure is clean, managers can trust the information they are reviewing. When the structure is inconsistent, reports may still exist, but they become less useful for real decision-making.
This is why CRM reporting should not be treated as a separate step after setup. It is the result of how consistently the CRM structure is configured and used from the beginning.
Preparing CRM for the Next Step in the Sales Process
Once the CRM foundation is configured, the next step is connecting opportunities to the broader sales workflow.
In Odoo, CRM does not have to stop at tracking leads and opportunities. When the Sales app is installed, opportunities can move into quotations and then into sales orders.
That workflow depends on other areas of Odoo being configured properly, including products, pricelists, taxes, payment terms, quotation templates, and customer records.
For that reason, CRM should be treated as the starting point of the revenue workflow, not as a standalone sales board.
A properly configured CRM gives the business a cleaner path from customer interest to qualified opportunity, quotation, order, delivery, invoicing, and follow-up.
In a later article, we will explore how opportunities move through the broader Odoo sales pipeline, including how CRM connects to quotations, sales orders, and the next steps in the sales process.
Final Thoughts
Odoo 19 CRM can be a powerful tool for managing leads, opportunities, sales ownership, pipeline stages, and sales visibility.
However, the value comes from how the system is configured.
When leads, sales teams, stages, opportunity fields, lost reasons, and reporting details are structured properly, CRM becomes easier for the sales team to use and easier for managers to trust.
When these pieces are ignored, the pipeline can quickly become inconsistent, making follow-ups harder to manage and reporting less reliable.
Taking the time to configure Odoo CRM around the way the business actually sells creates a stronger foundation for the workflows that come next, from quotations and sales orders to delivery, invoicing, and follow-up.
Frequently Asked Questions: Odoo 19 CRM Setup
What is the difference between a lead and an opportunity in Odoo?
A lead is an early-stage inquiry that has not yet been qualified. An opportunity is a qualified sales possibility that belongs in the active sales pipeline.
Leads can be enabled from CRM → Configuration → Settings when the business wants to review inquiries before converting them into opportunities.
Should every business use leads in Odoo CRM?
No. Leads are useful when a business has a qualification step before an inquiry becomes an active sales opportunity.
For smaller teams or simpler sales processes, working directly with opportunities may be cleaner.
What is a sales team in Odoo CRM?
A sales team is a working group inside CRM. It can represent a department, region, product line, sales channel, or sales process.
Sales teams help organize ownership, team members, email aliases, revenue targets, and reporting.
What are pipeline stages in Odoo CRM?
Pipeline stages are the steps an opportunity moves through during the sales process.
Examples may include New Inquiry, Qualified, Proposal Sent, Negotiation, Won, and Lost. A good stage structure should reflect meaningful sales progress, not every small action a salesperson performs.
Why are opportunity fields important in Odoo CRM?
Opportunity fields provide the sales context behind each deal.
Fields such as expected revenue, expected closing date, salesperson, sales team, customer, tags, and lost reason directly affect pipeline visibility and reporting.
Why are lost reasons important in Odoo CRM?
Lost reasons help categorize why opportunities did not close.
This gives management better visibility into whether deals are being lost because of price, timing, competition, poor fit, missing features, or lack of response.
What is the most common mistake when setting up Odoo CRM?
The most common mistake is configuring CRM around features instead of the actual sales process.
A strong CRM setup should define how leads are handled, who owns opportunities, which stages are needed, how opportunity data should be maintained, and how won or lost outcomes are recorded.