Map Mautic Contact Stages to Deal Stages: A Worked Setup

Set up two stage models with separate jobs

This article records a September 6, 2026 operating decision for the Deal Flow 0.9.4 release, not a timeless sync recipe. The shipped version keeps the two records separate, so recheck this manual map after any release that changes stage behavior.

Start with a contact lifecycle of Subscriber → Marketing Qualified → Sales Qualified → Customer. Each label describes the relationship with a person. A subscriber has entered the audience, a marketing-qualified contact has met the team’s engagement criteria, a sales-qualified contact is ready for direct sales attention, and a customer has reached the organization’s customer definition.

Next, create a deal pipeline of Qualified → Demo → Proposal → Negotiation → Won/Lost. These labels describe decisions about an opportunity, not the lifecycle of every person attached to it. Qualified means the opportunity meets entry criteria. Demo, Proposal, and Negotiation record concrete sales progress. Won and Lost close the opportunity with different outcomes.

Associate relevant contacts before testing the manual checklist. Include several buying roles and lifecycle stages so the review rule faces the same multi-contact conditions as a real deal.

Choose two manual review points and keep the rest separate

This example uses two checklist prompts rather than configured mappings. The intermediate stages stay independent because a demo, proposal, or negotiation describes opportunity progress without necessarily changing each participant’s lifecycle.

The first review point is Qualified ↔ Sales Qualified. When a deal becomes Qualified, its owner reviews the associated contacts and updates a contact manually only if that person meets the Sales Qualified definition. When a contact becomes Sales Qualified, the owner reviews every associated deal and moves a deal only if that opportunity meets the Qualified criteria. The labels are a checklist connection, not an automated link.

The second review point expresses the business intent Won → Customer. A won deal prompts the owner to review every associated person, but it does not establish that every stakeholder is a Customer under the contact lifecycle definition. Update qualifying contact records manually. A contact becoming Customer should likewise prompt review, not an automatic change to every opportunity involving that person.

Review associated records instead of copying one status broadly

Deal Flow’s current CRM setup guide, verified on 2026-09-06, states that deal stages and Mautic contact stages are separate in the shipped version. There is no automatic mapping in either direction. Teams that use both models define an operating rule and update each record manually after a stage decision.

Manual review matters because a deal can have several associated contacts, while one contact can participate in several deals. Copying a deal status to an entire buying group can assign the wrong lifecycle state to one person. Copying one person’s lifecycle status to every connected opportunity can move deals that have not met their own criteria. Review each associated record on its own terms.

Test the manual checklist in both directions

Use test records that expose the review burden rather than hiding it. First, create one test deal and associate several test contacts in different lifecycle stages. Move the deal to Qualified. Confirm that no contact stage changes automatically, open every associated contact, and apply the written Sales Qualified definition to each person before making any manual update.

Then test the reverse checklist. Associate one test contact with more than one test deal, place those deals in different stages, and change the contact to Sales Qualified through the same path your live process will use. Confirm that no deal moves automatically. Inspect each associated deal and apply its Qualified criteria before moving anything manually. Repeat the review for Won and Customer.

Record the expected result before each test. The checklist should name an owner, preserve a record that should not move, and leave a trace. Testing both directions proves the review process; it does not imply an automatic software action.

Operate the setup without collapsing the models

Once the tests pass, publish who owns each check, which records they inspect, what definition controls an update, and where they record the decision. Review contact-stage campaigns alongside the deal workflow so lifecycle changes receive deal review.

Keep Subscriber and Marketing Qualified independent from the deal pipeline. Keep Demo, Proposal, and Negotiation independent from the contact lifecycle. Keep Lost separate unless the team later defines and tests a person-level lifecycle outcome that truly fits a specific contact. This preserves the distinction the setup was designed to protect: contacts describe people; deals describe opportunities.

Frequently asked questions

Should every deal stage map to a Mautic contact stage?

No. The current shipped version has no automatic stage mapping. This setup uses manual review points for Qualified and Won while leaving Demo, Proposal, Negotiation, and Lost independent from contact lifecycle stages.

What happens to contacts when a deal stage changes?

The current shipped version does not automatically update contact stages. At a documented review point, the owner checks every associated contact and manually changes only the records that meet the contact-stage definition.

What happens to deals when a contact stage changes?

The current shipped version does not automatically move associated deals. The owner reviews each associated deal and moves a deal manually only when the opportunity meets that deal stage’s criteria.

Why keep the Lost deal stage separate from contact stages?

A lost opportunity does not necessarily end a person’s lifecycle. Keeping Lost separate prevents a deal outcome from assigning one contact-stage conclusion to every participant.