Mautic's Roadmap

Mautic has exciting plans for the future! Below is an outline of the features that we are planning to work on and a rough timeline of when they are expected to be made available.

Some of these features will be community contributed, others may be contributed by an organisation, and some are funded through grants.

Timeframes and release schedule

Mautic follows a monthly release cadence using semantic versioning:

  • Patch (bug fixes only) release monthly
  • Minor (features, enhancements and bug fixes) release quarterly
  • Major (backwards compatibility breaking changes) every two years

A process of moving towards a Long Term Support (LTS) version was initiated towards the end of Q4 2024, which sees a clearly outlined schedule for releases into the future. This is represented below showing the planned dates for major and minor releases. 

In order to catch up with the Symfony release schedule, Mautic 6 is a ‘bridging release’ to update Mautic to use Symfony 6, after which it will only receive bug fixes after its initial launch. It’s expected that work will start straight away on Mautic 7, which will include new features and functionality with pre-releases available during 2025 and a stable release in Q4 2025.

Mautic’s release schedule sees each major version being actively supported for a period of three years, which can be extended for another two years by purchasing Extended Long Term Support. Read more about this in our blog post on the new release schedule.

A screenshot of the new release schedule showing the dates and release phases in different colours from today through to 2035.

Extended Long Term Support (ELTS)

Sometimes users of Mautic need more than three years to plan for updating to the next major version. There can be many reasons for this. Mautic now provides an optional paid service in blocks of one or two years, providing back-ported security fixes to version of Mautic which are no longer actively supported by the community.

This service started with Mautic 4.

Read more on our dedicated resource section about Extended Long Term Support for Mautic.

Strategic Initiatives

Strategic Initiatives are projects which the Project Lead identifies in collaboration with the Product Team as being of central importance to Mautic’s future growth as the leading marketing automation product focused on user privacy, extendability and accessibility. These initiatives are generally centrally funded – either through corporate sponsorship or grant funding – and are managed centrally by team members who work under the direction of the Project Lead. 

All initiatives, whether strategic or community, are grounded in:

  • User insights – Initiatives that are based on what users of Mautic tell us is needed
  • Product vision – Initiatives that move us closer toward our vision for Mautic being the #1 choice for marketers who are concerned about privacy, extendability and accessibility
  • Market insights – Initiatives that are required for Mautic to remain competitive in the Marketing Automation world
  • Community discussion – Initiatives which have been discussed and validated in the Mautic community

Current Strategic Initiatives

Improving the User Experience

Feedback from users across the spectrum has for many years told us that Mautic feels like it’s built by developers, and hasn’t been as user friendly to learn and work with as it might be.

This causes problems because people don’t understand how things work, wording can be confusing and difficult to understand, and we have quite inconsistent ways of doing things within the user interface from the code perspective which makes application-wide changes like enabling dark mode quite difficult to achieve.

Since 2024 there has been a strong drive initially proposed as a Community Initiative and later sponsored by Diamond Partner Dropsolid, to completely overhaul the user interface, adopt the Carbon Design System, and proactively fix the things that people find difficult with Mautic.

Mautic 5.1 and 5.2 saw a huge transformation which is also helping to improve the accessibility of the Mautic user interface, and work continues on further developments.

Follow the UX/UI Tiger Team Assembly on the Community Portal for more news and updates, and join the Slack channel #tt-ux_ui if you’d like to be involved in the team.

Resource Management

Currently there is no easy way to archive old resources that are no longer in use within Mautic. This results in busier instances becoming quite cluttered, and making it difficult to navigate between active and inactive resources.

It’s also not possible to organize resources which are relating to a specific project within Mautic, so that you could see in a single place all the emails, campaigns, segments, tags, landing pages, forms and so forth which relate to that project and see rolled-up project reporting.

In 2025, Gold partner Webmecanik are leading this initiative. Read the proposal on the Community Portal, and follow the accountability project for updates.

Campaign Library

Mautic’s central powerhouse is the Campaign Builder, which allows marketers to build complex workflows with ease using click-and-drag building blocks and connectors. Currently there is no way to move campaigns between instances (for example if multiple customers need the same campaign) or to provide a set of standardized best-practice campaigns to help marketers get started.

This initiative has two phases – the first phase establishes the underlying infrastructure which is necessary to allow the import and export of campaigns and all associated resources. The second phase builds the user-facing interface which allows the marketer to search for and install campaigns which are provided by the community.

Phase 1 is generously funded by NLNet, and Phase 2 will be a follow-up project proposal for a future funding round.

It’s expected that the first phase will be delivered in Mautic 7.0, in Q4 2025.

Mautic Marketplace

The Mautic Marketplace is a central part of our 10 year vision, enabling us to grow a sustainable ecosystem and streamline Mautic’s core.

Currently in beta, the Mautic Marketplace allows users to install plugins from Packagist, using Composer ‘under the hood’.

Future development will see a new user interface being developed aligned with the new Carbon Design System, support for installing themes which will replace the current theme manager, and eventually also campaigns.

A further phase will see the introduction of payment capabilities, enabling developers and marketers to submit their plugins, themes and campaign bundles and receive a revenue share from purchases made via the marketplace.

Parts of this project have been funded by Google Summer of Code, and other aspects we are currently seeking sponsorship to develop.

The Privacy Project

Mautic already gives a great deal of privacy control by enabling data sovereignty by self-hosting, however we want Mautic to be the leading provider of marketing automation for privacy-focused businesses and marketers.

While we already have many great features, like our automated GDPR cleanup jobs and CCPA lookup tasks, we want to take things further, and really drive privacy to the forefront of the marketer’s mind.

This initiative has three phases, firstly addressing some identified areas where Mautic can improve its basic capacity for complying with privacy legislation more fully. Secondly, we aim to develop functionality so that every aspect of tracking that can be used in Mautic can be selectively turned on and off with one clear setting, allowing Mautic to run in full tracking, partial tracking or no-tracking mode. Finally, we plan to develop the functionality that enables the marketer to deal with privacy-related requests centrally within Mautic.

We are aiming that this project will be grant-funded.

Community initiatives

Community Initiatives are projects which are proposed and developed by the Mautic Community. There is a formal process which is followed for new feature ideas.

These start life as a discussion on the Forums, and if there’s sufficient interest, a formal proposal is created on the Community Portal for the Core Team to review and discuss.

Once the Core Team approves the proposal, a targeted release is agreed and the developer works to ensure that the feature is ready in time for the release. You can follow the progress on initiatives here.

Mautic Partners have the right to propose three features per year directly to the Project Lead without having to discuss on the Mautic Forums first, which can be considered for inclusion on the roadmap.

Search

Use the search bar above by typing terms and pressing enter.