When Mautic Lead Tracking Should Become Deal Tracking

Why we are publishing this handoff rule now

On September 8, 2026, we reviewed Mautic 7.2’s published contact, stage, segment, and campaign model against the opportunity records Deal Flow adds. Our conclusion is a practical rule: keep engagement on the contact, then create a deal when a commercial event develops state of its own. Adding fields to a contact does not solve that data-model problem; each fact still needs the right home.

What Mautic already tracks well

As checked on September 8, 2026, the official Mautic contact documentation centers the system on identified and anonymous people. Its current documentation also covers custom fields, segments, contact lifecycle stages, and campaign workflows. Those tools help a team understand who someone is, what they have done, and how marketing should respond.

That contact model can also carry a simple sales process. A small team can create contact stages such as Qualified, Demo, Proposal, and Won. Custom contact fields can hold an amount and expected close date, while the contact record carries an owner. Segments can group contacts by field values, while campaigns can react to contact behavior and move contacts between stages.

This setup is reasonable when every active sales conversation has one contact and that contact has one opportunity. If a founder can open a contact and understand the whole commercial conversation, lead tracking may still be the simpler model.

The exact point where the model stops fitting

The boundary appears when a sales fact can no longer be answered at the contact level.

Imagine that Jordan is involved in a renewal and a separate expansion project. The renewal is in negotiation, closes this month, and has one amount. The expansion is still being evaluated, closes next quarter, and has another amount. A single stage, value, and close-date field on Jordan’s contact cannot describe both opportunities at once.

The same problem appears from the other direction. One purchase may involve Jordan as the internal champion, Casey as the budget holder, and Morgan as the technical evaluator. Those people keep their own contact histories, but the amount, close date, and sales stage belong to the purchase they share.

A team has crossed into deal tracking when any of these statements is true:

• One contact can participate in two active opportunities.
• One opportunity can involve several contacts.
• The team needs an amount, close date, owner, or stage for the opportunity itself.
• A pipeline question cannot be answered without exporting and rebuilding contact data elsewhere.

What a deal record changes

A deal record separates the person from the purchase. Contacts continue to hold identity, activity, scoring, and nurture context. The deal holds the commercial state: the opportunity’s pipeline and stage, amount, expected close date, and owner.

That separation changes ordinary work. When a proposal moves forward, the team updates the deal rather than redefining a person’s lifecycle. When a second opportunity opens, it gets a second record rather than overwriting the first. When a new evaluator joins, the team links that contact to the existing deal instead of compressing the buying group into one primary contact.

Each opportunity has its own amount, stage, and expected close date, and the kanban board groups deals by stage. The practical choices behind those fields are covered in the guide to deal value tracking in Mautic.

Deal Flow adds this deal record inside Mautic. A deal links to existing contacts and carries its own pipeline, stage, amount, expected close date, and owner. Several contacts can be associated with the same deal and labeled by buying-committee role, such as champion, decision maker, budget holder, or technical evaluator. Notes, tasks, and attachments stay with the opportunity.

The visible board is useful, but the deeper change is ownership. Contact facts stay on contacts. Opportunity facts stay on deals. The team no longer has to decide which active sale gets to occupy a person’s one set of commercial fields.

A practical handoff rule

Keep early interest in Mautic’s contact model. A form submission, page visit, score change, or nurture response does not need to create a deal by itself. Those events describe engagement with a person.

Create a deal when the team recognizes a specific commercial event it intends to manage. That may be a qualified project, a requested proposal, a renewal under discussion, or another opportunity with a real next step. Write the rule clearly enough that two teammates would create the record at the same point.

Then move opportunity fields off the contact as the working source of truth. Give each current opportunity its own amount, expected close date, owner, and stage. Link the people involved and label their roles. Leave contacts that are still being educated or nurtured as contacts until a commercial event exists.

This is a boundary, not a maturity badge. A one-person sales process can need deal records if customers buy more than once. A larger marketing database may not need them for people who have never entered a sales conversation. Use the shape of the sale, not the size of the database, to make the choice.

Frequently asked questions

Can Mautic track leads without separate deal records?

Yes. Mautic contacts, custom fields, stages, segments, and campaigns can support a straightforward process while one contact maps to one active opportunity. A separate deal record becomes useful when commercial facts no longer fit that one-to-one model.

When should a Mautic team create a deal?

Create a deal when there is a specific commercial opportunity with facts of its own, such as an amount, expected close date, owner, or sales stage. A second opportunity for one contact or several contacts on one opportunity is also a clear signal.

Does deal tracking replace Mautic contacts?

No. Contacts remain the records for people and their engagement. Deals represent commercial opportunities and link the relevant contacts to the amount, close date, owner, stage, and buying-committee context they share.