What Mautic 7 Changes for Sales Pipeline Operations

Campaign changes deserve an operations review

Mautic’s 7.0 announcement, published January 20, 2026, says campaigns can be imported and exported together with related assets so teams can move campaign setups between environments. The same announcement says segment email sending can either continue as contacts enter a segment or lock the audience to those present when sending begins. Those Mautic 7.0 details were checked August 25, 2026.

Mautic’s 7.1 announcement, published April 1, 2026, adds event statistics directly to the campaign graph, scheduling labels on arrows, and what the project describes as more predictable republishing behavior for existing contacts. Those Mautic 7.1 campaign details were checked August 25, 2026.

Contact Stage and Owner fields can now enter through forms

The April 1, 2026 Mautic 7.1 announcement says Stage and Owner fields are available in the contact-fields list for form mapping. It also says all forms can trigger campaigns on submission and all form actions are available for every form under a unified form model. Mautic’s form-change description was checked August 25, 2026.

For a sales operation, that creates a useful review point rather than an automatic pipeline design. Decide who is allowed to set a contact owner or contact stage through a form, test how blank and repeat submissions behave, and confirm the downstream campaign rules. Keep contact-level Stage and Owner mapping conceptually separate from the deal-level stages used to represent opportunity progression.

API v2 is a separate integration surface to evaluate

The January 20, 2026 Mautic 7.0 announcement introduces a REST API at /api/v2, built on API Platform, with interactive documentation and more consistent endpoints. Mautic’s API announcement was checked August 25, 2026.

The Mautic developer documentation identifies /api/v2 as the base endpoint, says authenticated users can browse interactive endpoint documentation there, and documents default pagination plus JSON-LD, JSON, and HTML response formats. The API v2 documentation was checked August 25, 2026.

That does not mean an existing integration should be moved without inspection. Inventory every endpoint your revenue process calls, record its authentication and response assumptions, and test pagination, writes, errors, and retries against a representative staging instance. Treat an API migration as its own scoped change; this post makes no claim that Deal Flow uses Mautic API v2.

The upgrade boundary includes infrastructure

Mautic’s releases page listed 7.1.2 as the latest Mautic 7 release and PHP 8.2–8.5 as its required range when checked August 25, 2026. The current-version record is maintained on Mautic’s releases page.

The January 20, 2026 Mautic 7.0 announcement says PHP 8.2 is the minimum, manual updates through the user interface were removed, and AMQP queue support and the previous API rate limiter were removed. It directs administrators toward Composer or a release package for updates. Those upgrade details were checked August 25, 2026.

The practical implication is to review more than application screens. Confirm the target PHP runtime, document the supported update method, and identify any queue or API traffic controls that depend on removed behavior. Preserve a restore-tested backup and rehearse the upgrade in an environment that represents production data volume, scheduled jobs, plugins, and external connections.

A focused pre-upgrade review for pipeline operators

1. Map the revenue path. List the forms, contact fields, segments, campaigns, API calls, and external jobs involved from first response through handoff.
2. Test campaign state. Exercise audience entry, waits, graph events, republishing, and campaign transfer between environments where your process uses them.
3. Retest field authority. Verify who or what can write contact Stage and Owner values and which automations react to those writes.
4. Separate API evaluation from upgrade execution. Keep current integrations stable while you test any API v2 work against documented endpoints and response formats.
5. Rehearse recovery. Record the update procedure, rollback threshold, owners, and acceptance checks before changing the live system.

This is an operations checklist, not a claim that every Mautic 7 change affects every pipeline. Start with the components your instance actually uses and preserve evidence from the staging run so the production decision is based on observed behavior.

Sources checked August 25, 2026

• Mautic releases — current Mautic 7 release and PHP range.
• Mautic 7: Columba Edition is released — published January 20, 2026.
• Mautic 7.1 Canis Major edition is released — published April 1, 2026.
• Mautic API v2 developer documentation — base path, discovery, pagination, and response formats.

Release details are perishable. Recheck the vendor’s current pages and the exact target release before approving an upgrade.