What Mautic 7.2 Signals for Self-Hosted Sales Teams

The sequence matters more than a single release

Mautic’s published policy describes patch releases as monthly and minor releases as arriving every three months. The visible Mautic 7 sequence gives operators a concrete set of releases to plan around: 7.1.1 Adhara was published May 4, 7.1.2 Aludra on May 28, the 7.2.0 release candidate Lynx on June 2, and 7.1.3 Amadioha on July 7, 2026.

Sources: Announcing Mautic 7.1.1: Adhara Edition, Announcing Mautic 7.1.2: Aludra Edition, Welcome to Mautic 7.2.0 Release Candidate: Lynx Edition, and Announcing Mautic 7.1.3: Amadioha Edition; published May 4, May 28, June 2, and July 7, 2026; all verified August 31, 2026. Cadence policy verified August 31, 2026 from the official release index.

That sequence is useful because it shows maintenance continuing on the stable 7.1 line while a later feature release is available for testing. It does not tell an operator to install every package immediately. It tells the operator to build an upgrade lane that can handle security work, bug fixes, and pre-release evaluation without improvising each time.

Turn release activity into an upgrade operating rhythm

The 7.1.2 notes identify Aludra as a security release and advise administrators to make a full backup and test the upgrade in staging. The same notes list a CKEditor library update and a fix that avoids MJML reparsing in the source editor’s HTML mode. These are concrete reasons to test both infrastructure recovery and the editing workflows users touch.

Source: Announcing Mautic 7.1.2: Aludra Edition; published May 28, 2026; direct release record verified August 31, 2026. The official release index provides Mautic’s published release overview.

A repeatable release review should cover the whole revenue path, not merely whether the application loads:

1. Record the starting state. Note the Mautic version, PHP and database versions, installed plugins, scheduled jobs, and external integrations.
2. Prepare recovery. Take a backup, confirm that it can be restored, and define the conditions that stop the production rollout.
3. Mirror the important workflows. In staging, test forms, segment changes, campaign waits, email editing, API calls, contact ownership, and any path that changes a sales handoff.
4. Check each plugin explicitly. Match the target Mautic version to documented support and to a recorded test result, rather than assuming compatibility from a broad major-version label.
5. Keep an evidence trail. Save the release notes reviewed, test results, exceptions, owner, and rollout decision for the next patch cycle.

Use the Lynx release candidate as a testing input

The 7.2.0 RC notes label Lynx a pre-release for testing, not production. Its editor-related entries include SVG files in the image selector, entity-token labels in CKEditor, MJML theme styling for GrapesJS blocks, and fixes for a CKEditor license-key error and an MJML preview-tag error.

Source: Welcome to Mautic 7.2.0 Release Candidate: Lynx Edition; published June 2, 2026; direct release record verified August 31, 2026. The official release index provides Mautic’s published release overview.

Those notes define a focused test plan: open representative HTML and MJML emails, inspect existing templates, exercise image selection and entity tokens, then compare saved and sent output with the current production version. The notes do not establish a production release date or a final feature set, so neither should enter a migration plan as a fact.

The stable line deserves the same discipline. The 7.1.3 notes list restored GrapesJS typography tools, corrected handling for headings, spans, and paragraphs in the GrapesJS–CKEditor integration, and a fix for table editing. A team that depends on those editor paths should add them to the stable-patch regression set.

Source: Announcing Mautic 7.1.3: Amadioha Edition; published July 7, 2026; direct release record verified August 31, 2026. The official release index provides Mautic’s published release overview.

Update, September 3, 2026: Mautic 7.2.0 stable shipped

Mautic published Mautic Community 7.2.0 Lynx Edition as a stable release on September 2, 2026 — the release record is not marked as a pre-release. The testing-input advice above now converts directly into a staged upgrade plan: the same staging checks, run against the stable package instead of the RC.

For teams running sales pipelines on Mautic, the release notes list several entries worth a specific look in staging: the ability to merge contact stages, a warning about duplicate stage weights, and a new point trigger that fires on contact stage changes. Deal Flow synchronizes deal stages bidirectionally with Mautic contact stages, so an instance that consolidates or reweights its stage list during this upgrade should re-check its stage mappings afterwards. The notes also list plugin-platform additions — extra methods for custom plugins, a new event for plugins with complex permission logic, and a new Marketplace API with reviews and ratings.

Source: Announcing Mautic 7.2.0 Lynx Edition, published September 2, 2026; direct release record fetched September 3, 2026.

Where a commercial plugin fits

Self-hosting gives a team control over upgrade timing, but it also makes the team responsible for the dependency chain. A commercial plugin belongs in that chain as a versioned component with a named vendor, a compatibility statement, release notes, and a support path. Its presence should make responsibility clearer, not remove the need for staging.

Ask two separate questions. First, which Mautic versions does the vendor declare as supported? Second, which exact combinations have been exercised, with what result and on what date? Declared support sets the intended boundary. Recorded testing supplies evidence for an upgrade decision. Keeping those answers separate prevents a fast-moving host release from turning a general compatibility claim into false confidence.

That is the signal in this release cycle: choosing self-hosted Mautic requires a team willing to own a routine. The work is not constant firefighting. It is a small, repeatable release process that protects the forms, campaigns, editor paths, APIs, and plugins carrying revenue work.

Source boundary

Release facts in this article come from the four named Mautic release records fetched August 31, 2026 and the project’s official release index. The original 7.2 material is described strictly as a release candidate; the September 3, 2026 update section draws on the 7.2.0 stable release record, fetched September 3, 2026.