Mautic vs Odoo Marketing: which to choose

Mautic vs Odoo Marketing: when to choose each platform

Choose Mautic when marketing needs its own automation platform that sits beside a CRM you already run or plan to keep, and when your team can operate a PHP and MySQL application. Mautic is GPL-3.0 licensed, has no paid edition of the software itself, and is built for campaigns, segments and lead scoring as its core job. Choose Odoo when your sales operation already runs on Odoo, so contacts, opportunities and orders live in one database, and when you accept that some marketing modules need an Enterprise subscription. The two are not interchangeable: Mautic gives you a dedicated marketing engine with its own data model, while Odoo gives you marketing apps that share the ERP's records and upgrade cycle.

The decision usually turns on three questions. First, where does your customer record live? If a CRM is already the system of record, Mautic will need a sync to it, and you should confirm which connectors your CRM supports, because the supplied Mautic plugin documentation covers HubSpot and Salesforce. If Odoo CRM is your record, the sync problem mostly disappears. Second, which Odoo modules do you need? The Community repository includes Email Marketing, SMS Marketing, Events and CRM, but Marketing Automation and Social Marketing ship with Odoo Enterprise, so check the edition of every module on your list before comparing features. Third, how much hosting and upgrade work will your team absorb? Mautic runs cron jobs for segments, campaigns and broadcasts, and the Mautic project advises against shared hosting. Odoo's Community edition has no upgrade service, while Enterprise customers on Odoo Online or Odoo.sh face mandatory major upgrades every two years.

Before you shortlist either platform, ask for a written inventory: each campaign type you run today, each system it touches, and the edition of Odoo each module requires. Run a small illustrative test in both: import a sample of contacts, build one lead-scoring campaign, and push one opportunity change through to the CRM. Then price the work in a fixed-scope quote from DeployOpen, covering installation, the CRM integration, cron and queue setup, backups and the upgrade plan for the next major release. Confirm the Enterprise license terms and support windows directly with Odoo and the Mautic release schedule on the Mautic releases page before you commit.

Which platform fits which scenario

This table matches common team situations to the platform that usually fits better, and names the condition that drives the choice. Read each row against your existing CRM, your Odoo edition and your open-source policy, since those three factors decide most comparisons on this page.

Scenario	Better fit	Condition that drives the choice
Existing non-Odoo CRM that the marketing team already uses	Mautic	Mautic runs as its own application with separate contact data, so it can sit beside any CRM. Confirm which CRM connectors your version supports, such as the HubSpot and Salesforce plugins documented by the Mautic project, and who will maintain the sync.
Odoo CRM and sales team that wants one contact and pipeline data model	Odoo Marketing	Shared records across CRM, sales and marketing remove a sync layer. This holds only if the modules you need are available in your Odoo edition, and the Community edition does not include Marketing Automation.
Need for marketing automation features outside the Odoo Community edition	Mautic	Marketing Automation and Social Marketing ship with Odoo Enterprise, which requires a valid Enterprise subscription. Mautic is GPL-3.0 with no paid edition of the software, so the feature set does not depend on a license tier.
Odoo Enterprise already licensed for the company and marketing wants campaigns inside it	Odoo Marketing	If the subscription already covers the required apps, extra platform cost is low. Confirm that the modules you need are included in your subscription and that your Odoo version is still within support.
Organization with a strict open-source-only policy	Mautic	Mautic is GPL-3.0 with a community-owned project and no commercial entity behind it. Odoo Community is LGPLv3, but Marketing Automation requires Enterprise, which uses a proprietary license. Confirm the policy covers the full module set you plan to run.
Team that wants to limit the number of platforms it must upgrade on a fixed schedule	Odoo Marketing	Odoo's upgrade and support rules set a schedule for the full suite, and on Odoo Online and Odoo.sh major upgrades are mandatory every two years. Mautic instead publishes monthly patch, quarterly minor and two-year major release cadences that you must plan for separately.
Small marketing team that expects to run and tune cron jobs and a queue consumer	Odoo Marketing	Mautic depends on staggered cron jobs and a messenger consumer for queued emails, so someone must own that operational work. Odoo hosted options reduce that server-side work, though on-premise Odoo carries similar hosting duties.
Organization that needs a multi-company setup or custom modules inside the marketing stack	Odoo Marketing	Odoo's Custom plan includes multi-company, Odoo Studio, external API access and custom modules, and only that plan can be hosted on Odoo.sh or on-premise. Confirm the exact plan and edition before you assume these capabilities.

How Mautic and Odoo are built and what that means for operations

Mautic and Odoo Marketing come from different starting points: one is a standalone marketing engine, the other a marketing module inside a business suite. Their stacks, scheduled jobs and hosting options shape the operating work each one creates, so check these before you pick either.

Mautic's PHP and Symfony stack

Mautic is a PHP application built on the Symfony framework, running on MySQL with InnoDB or MariaDB. Its supported PHP range for Mautic 7.0 is 8.2 to 8.5, and the project lists Apache, Nginx or IIS as web servers. Your team owns the PHP, database and web tier upgrades, so confirm who on your side can patch that stack on the release cadence you plan to follow.

Cron jobs that must be staggered

Mautic relies on cron jobs to update segments, update campaigns and trigger campaign steps. The Mautic docs say these jobs should be staggered so they do not run at the same time. Someone must own the schedule, monitor job failures and confirm campaigns are firing on time, because a missed job shows up as stalled sends rather than an error page.

Broadcasts command and message queue

Segment emails are sent through a broadcasts command, and when emails are queued Mautic needs a messenger consumer running to process them. If the consumer stops, queued mail waits without a visible failure in the marketing UI. Ask your platform team how the consumer runs under a process supervisor and how alerts reach them when the queue stops moving.

Hosting beyond shared hosting

The Mautic project states that it should not be installed on shared hosting and recommends a VPS or dedicated server. Budget for a server you control, with its own patching, backups and capacity planning. This is the main infrastructure line item for a self-hosted Mautic, and it recurs every month whether or not campaigns are running.

Odoo's Python and PostgreSQL suite

Odoo is a suite of business applications built on Python and PostgreSQL, covering CRM, sales, accounting and more. Its marketing modules sit inside the same database and codebase as your sales and finance data. Odoo upgrades and module changes therefore touch the whole suite, so test marketing workflows alongside every other app before each upgrade.

Three Odoo deployment paths

Odoo runs on Odoo Online, Odoo.sh or on-premise. According to Odoo's pricing page, only the Custom plan can be hosted on Odoo.sh or on-premise, and only Custom includes custom modules and external API access. Confirm which plan and hosting path your marketing workflows need, because the choice determines who runs the servers and which modules you can add.

Capability, licensing and support compared side by side

This table compares license terms, where marketing automation is available, identity options, release support and hosting requirements for Mautic and Odoo Marketing. Read each row against your own edition plans, because the Odoo rows depend on whether you buy Enterprise and the Mautic rows depend on which release you pin.

Capability	Mautic	Odoo Marketing
License	GPL-3.0 for the GitHub repository, with no paid edition of the software itself	LGPL-3.0 for Community, proprietary Odoo Enterprise Edition License v1.0 for Enterprise
Marketing automation availability	Core product, included in the free self-hosted download	Marketing Automation and Social Marketing ship with Odoo Enterprise, not Community
Email and SMS marketing	Email campaigns and segment emails run through the broadcasts command and queued messenger consumer	Email Marketing (mass_mailing) and SMS Marketing are in the Community repository
CRM data integration	Native contact model; HubSpot and Salesforce connections are separate plugins, so confirm current plugin support for your CRM version	Events and CRM modules are in Community; confirm which marketing features need Enterprise for your CRM workflows
Identity integration	Authentication options are documented; confirm the methods and SSO setup for your release in the Mautic authentication docs	LDAP authentication is documented; confirm whether it is available on your edition and plan before relying on it
Current release and support window	Mautic 7.2 security support ends 30 September 2026; Mautic 7.3 is planned as LTS with security support through 31 December 2027	Odoo 20 standard support planned until September 2029; Odoo 19.0 until September 2028 (Odoo support docs)
Hosting requirements	PHP 8.2 to 8.5, MySQL 5.7+ with InnoDB or MariaDB 10.2+, npm from 5.0 onward, not for shared hosting	Python and PostgreSQL; Odoo.sh or on-premise hosting requires the Custom plan per the pricing page
Upgrade effort	Monthly patches, quarterly minors and biennial majors; plan a test upgrade for each major	SaaS releases every two to three months; Odoo Online and Odoo.sh upgrades are mandatory every two years; upgrade service needs Enterprise

What Odoo marketing modules need Enterprise

Mautic is released under GPL-3.0, and the project describes itself as community-owned with no commercial entity behind it. There is no paid edition of the software itself, so the licensing question is simpler than on Odoo. The free self-hosted download is the product. Managed Mautic and Mautic hosting are separately promoted services, which you buy only if you decide not to run the platform yourself. See Mautic's about page for the project's own description.

No feature gating: the marketing features in the codebase are available under the same license, with no Enterprise module list to check.
Trademark held by the project: MAUTIC is a trademark of the Mautic project of the Open Source Collective, which matters if you plan to rebrand or resell a distribution.
Managed services are optional: a hosted offer is a separate contract with its own pricing and terms, not a license upgrade.
Your costs are operational: you pay for infrastructure, administration, upgrades and any external help, which DeployOpen would scope in writing if you engaged it.

Confirm with the vendor whether any managed offer changes data residency, support terms or upgrade responsibilities before you compare it with a self-hosted install.

What running Mautic next to an existing CRM really costs

The largest recurring cost of Mautic next to an existing CRM is not the software license, since Mautic is GPL-3.0 and has no paid edition of the software itself. The cost sits in the people and infrastructure that keep the stack running: a VPS or dedicated server (the Mautic requirements page says Mautic should not run on shared hosting), PHP and MySQL administration, and the cron jobs that update segments, campaigns and campaign triggers, plus the broadcasts command and the messenger consumer when email is queued. Each of these needs an owner, monitoring and a documented runbook. Ask a partner to price these as separate line items so you can see which ones your own platform team already covers.

The CRM connector is where the one-time and recurring costs diverge. The initial build covers field mapping between Mautic contacts and CRM records, deduplication rules, sync direction and error handling, and it is usually a one-time piece of work. The upkeep is recurring: every CRM upgrade, change to custom objects, and Mautic upgrade can break the connector, and each Mautic release line has its own support window, so the connector must be retested before you move versions. Confirm in the Mautic release notes which version line your chosen CRM integration supports, and ask whether the connector work includes regression testing after each Mautic patch or minor release.

Recurring costs go up when you run Mautic on a version nearing the end of security support, when the CRM is customized heavily, when email volume or the number of queued sends grows, and when staff turnover leaves nobody who understands the cron schedule. Costs go down when you stagger cron jobs, standardize on one CRM integration path and keep a patch cadence. When requesting a quote, ask for a fixed-scope proposal that separates one-time setup and integration build from annual hosting, upgrade, security patching and staff support. DeployOpen does not publish prices, so the written scope is the basis for any figure, and you should compare it with the cost of Odoo Enterprise subscriptions and the time your team spends on the CRM you already run.

What drives the running cost of each platform

Running cost for either platform is mostly recurring work: patching, upgrades, hosting and the people who do them. Odoo and Mautic put that work on different schedules, and the cards below show where each one lands in your budget and what to confirm before you commit.

Hosting footprint and infrastructure

Mautic must run on a VPS or dedicated server, and the project advises against shared hosting. You carry the web server, database, cron host and queue workers as ongoing infrastructure. Odoo Community can be self-hosted from source or packages, but Odoo.sh and on-premise hosting of Enterprise features are tied to the Custom plan. Ask each vendor which components you must host and which you can buy as a service, then price those lines in your own environment.

Mautic cron and queue operations

Mautic relies on cron jobs for segment updates, campaign updates and campaign triggers, staggered so they do not collide, plus a broadcasts command and a messenger consumer when email is queued. Each of these is a running job your team must monitor. Failed or overlapping jobs stall campaigns silently, so the operating effort is ongoing even when the software is stable.

Mautic release cadence

Mautic ships monthly patch releases, minor releases every three months and major releases every two years. Patch and minor work is recurring staff time, and each major release means testing campaigns, plugins and integrations against new requirements. Security support windows end on fixed dates, so a version that is still running after its end date no longer receives fixes. Plan a standing upgrade slot and confirm which version your install will sit on.

Odoo mandatory major upgrades

On Odoo Online and Odoo.sh, major version upgrades are mandatory every two years. Each upgrade runs against an upgraded test database that you should test before production, so the cost is a recurring test cycle that touches your marketing modules and any custom code. Confirm with Odoo which upgrade path, testing support and service fees apply to your plan before you rely on a two-year cycle.

Support windows and Enterprise licensing

Odoo standard support covers the first three years after a major release, including security updates, and extended support after that is limited to Odoo.sh for select versions and on-premise. Security patches come only during standard support. On-premise use of Enterprise, including the marketing automation and social marketing modules, requires a valid Enterprise subscription. Ask for the subscription cost, the modules it covers and the date each major version leaves standard support.

Skills and support options

Mautic needs PHP, Symfony-aware administration, MySQL or MariaDB tuning and cron expertise, and the community provides documentation without a paid support contract. Odoo needs Python and PostgreSQL skills for custom modules, plus Odoo partner or vendor support for Enterprise. Decide whether you will staff these skills in-house, buy a retainer for patching and upgrades, or combine both. DeployOpen offers ongoing support and upgrades as retainers under a written scope.

Moving between Mautic and Odoo Marketing: what transfers and in what order

This sequence shows how contacts, segments, campaigns and consent records move from one marketing system to the other without losing track of who may be contacted, and it ends with a documented cutover rather than a single switch-over date.

Inventory contacts, segments, campaigns and consent records
Export every contact field, segment definition, active campaign, email template and consent or opt-out record from Mautic, and list the Odoo models that will receive them. Assign an owner to each object type, usually the marketing operations lead for campaigns and the data protection contact for consent. The step is done when every object has a row in a mapping sheet that names its source field, its target field and whether it transfers as data, is rebuilt by hand, or is retired. Confirm consent history separately, because a list of current opt-ins does not show when or how consent was given.
Decide the system of record for leads and sales data
Decide which platform owns each lead status, opportunity stage and contact attribute before any data moves. If Odoo CRM owns the sales pipeline, Odoo should hold the commercial record, and Mautic should receive only the fields it needs for segmentation. Write the decision down with the name of the approver. The step is done when the team can state, for each field, which system is authoritative and which one reads from it. Without this decision, the two systems will overwrite each other during the parallel period.
Map data models and flag what does not transfer cleanly
Compare how each platform structures contacts, companies, tags, lists and activity history. Mautic is built around contacts, segments and campaigns, while Odoo places marketing records next to CRM leads, partners and sales activity, so one Mautic contact may correspond to several Odoo records or none. Campaign logic, lead scoring rules and point history usually need to be rebuilt rather than copied. Record every field that cannot be mapped one to one and decide whether to drop it, store it as a custom field or keep it in an archive. The step is done when the list of unmapped fields has been reviewed by both the marketing and sales owners.
Rebuild automations and test them in a staging copy
Recreate each campaign, segment and automation in the target tool, then run it against a test dataset that uses sample or anonymized contacts. Confirm that suppression rules, opt-out handling and sending limits behave the same way they did in the source system. Check the Odoo edition first: the Community repository includes Email Marketing and SMS Marketing, but Marketing Automation and Social Marketing ship with Odoo Enterprise, so any automation you planned on those modules needs an Enterprise subscription. The step is done when a written test log shows each rebuilt automation producing the expected result for each test case.
Test the Odoo upgrade path before production
If the target is an Odoo database that will later move to a newer major version, run the upgrade on a copy first. Odoo's upgrade service produces an upgraded test database that should be checked before it replaces production, and on-premise use of that service requires an Enterprise subscription. Review custom modules, mass mailing templates and integrations for breakage. Odoo Online and Odoo.sh also require major upgrades every two years, so the upgrade test should be scheduled as a recurring task, not a one-off. The step is done when the test database has passed the same checks as the production baseline and the findings are recorded.
Run a parallel period with reconciliation
Keep both systems active for an agreed period while sending only from the system of record. Each day or week, reconcile contact counts, suppression lists and consent status between the two platforms, and investigate every mismatch before the next run. Log any send that went out from the wrong system. The parallel period has no fixed length in this guidance, so the team should set its length in advance and ask the implementation partner to state how it is measured. The step is done when reconciliation reports show no unexplained differences for the agreed number of cycles.
Cut over and retire the old sending path
Switch all live sends to the target system, disable the old scheduled jobs and mailers, and update the sending domain, DNS records and unsubscribe links. In Mautic, the cron jobs for segments, campaigns and broadcasts stop when the instance is retired, so confirm that nothing else still depends on them. Keep a read-only archive of the Mautic database and its consent records for the retention period your data protection policy requires. The step is done when the old system sends nothing, the archive has been verified by restore test, and the cutover record is signed off by the marketing and security owners.

Where Mautic and Odoo marketing projects usually run long

The longest delays in a Mautic project usually come from the setup work around the application, not the install itself. Mautic can be installed from the production package with the web or command-line installer, or through Composer using the recommended project template, and the install is the quick part. The slower work is configuration: the cron jobs for segment updates, campaign updates and campaign triggers, which the docs say should be staggered, plus the broadcasts command for segment emails and a messenger consumer when emails are queued. Each of these needs a scheduler, a monitored process and an owner. Confirm with your hosting provider or platform team that you can run these reliably on a VPS or dedicated server, since the project states Mautic should not be installed on shared hosting. If you connect Mautic to an existing CRM through a plugin such as the HubSpot or Salesforce plugin, budget time for field mapping and agreeing which system owns each contact attribute before the first sync.

Odoo projects run long for different reasons. The first decision is module selection. The Community repository includes Email Marketing, SMS Marketing, Events and CRM, but Marketing Automation and Social Marketing ship with Odoo Enterprise, so a campaign-driven plan may depend on a subscription you have not yet bought. Enterprise databases are activated by entering the subscription code, which means the licensing decision has to be made before the build starts. The larger effort is the data model. Leads, contacts, opportunities and mailing lists sit in the same database, so teams must agree which records are the source of truth for consent, lifecycle stage and ownership before configuration begins. Plan for a test database duplicated with neutralization, which Odoo documents for test copies, so that outbound mail and integrations do not fire against live contacts during testing.

Ask any vendor or partner for a written list of the cron, worker and sync jobs, the fields and mapping rules, the test environment process and the upgrade path to the next supported version. For Odoo, confirm which Enterprise modules your use case needs and the subscription terms that apply. For Mautic, confirm the release you will run and its support window, since security support for each release ends on a published date. Treat these checks as the basis for a fixed-scope plan, so the count of integrations, data sources and environments is agreed in writing before any work starts.

Questions buyers ask before choosing or hiring help

Does Odoo Community include marketing automation?

Not the full marketing automation module. The Odoo Community repository on the 19.0 branch includes Email Marketing (mass_mailing), SMS Marketing, Events and CRM, but the Marketing Automation and Social Marketing modules ship with Odoo Enterprise. Check the Community addons list for your target version before you plan campaigns around it, since module placement can change between releases. If your workflows depend on multi-step journeys, lead scoring or social channels, price the Enterprise subscription into the comparison from the start. The Odoo licenses documentation explains which license governs each edition.

What does running Mautic need from the in-house team?

Mautic needs someone who can run a PHP application stack and its scheduled jobs. The project supports PHP 8.2 to 8.5 for Mautic 7.0, requires MySQL with InnoDB or MariaDB, and runs on Apache, Nginx or IIS. It also depends on cron jobs for segment updates, campaign updates and campaign triggers, plus a broadcasts command and a messenger consumer when email is queued. Someone must own patching, because monthly patch releases and minor releases every three months are the project's stated cadence. Confirm whether your team can take on that cadence, or whether it wants an outside operator for upgrades and backups.

How long does a migration take, and what drives that time?

No supplied fact gives a migration duration, so treat any number you hear as a guess until it is scoped. The main drivers are the number of contacts and custom fields, the number of active campaigns and forms to rebuild, the depth of CRM sync, and how many integrations must be re-created. Odoo's upgrade path adds its own test cycle: the upgrade service produces an upgraded test database that should be tested before production. Ask any provider for a written scope that lists data objects, integrations and test steps, and ask which items are fixed-scope deliverables.

Can Mautic run on shared hosting?

No. The Mautic project states that Mautic should not be installed on shared hosting and recommends a VPS or dedicated server instead. Its cron jobs and queued email processing need a host where you control scheduled tasks and long-running processes. Budget for that server in your hosting cost, and factor in the time to set up monitoring and backups. The Mautic requirements page lists the supported versions of PHP, the database and the web server.

Can an existing CRM stay in place with Mautic or Odoo?

Yes, in both cases, but the integration is the work. Mautic has documented plugins for HubSpot and Salesforce, so you can keep an external CRM and sync contacts and activity into Mautic. With Odoo, the CRM app is part of the suite, so keeping a separate CRM means building or maintaining an integration yourself. Confirm the sync direction, field mapping, duplicate handling and which system owns each record. Ask the vendor or integrator to show the sync working against your own data before you commit.

What support options exist for Mautic and Odoo?

Mautic has no paid edition of the software itself. The free self-hosted download is available from mautic.org, which also promotes separately offered managed Mautic and Mautic hosting services. Odoo offers paid subscriptions: Odoo Online, Odoo.sh and on-premise each carry standard support for the first three years after a major release, including security updates and bug fixes. Odoo's extended support is limited to Odoo.sh for select versions and on-premise, and security patches come only during standard support. Ask each provider which support window applies to the version you choose, and who supplies the patches after it ends.

Can we do this work without outside help?

Yes, if you have people who can run PHP applications, database operations, scheduled jobs and integrations, and who can keep a test environment in step with releases. Mautic's self-hosted download and documented installer make a first deployment possible without a vendor. Odoo Community is also self-hostable under LGPLv3, but an Enterprise subscription is needed for on-premise use of the Enterprise features and for the upgrade service. Outside help is most useful for the initial configuration, integration with existing systems, hardening, backups and upgrade testing. DeployOpen plans, implements, integrates, hardens, backs up, upgrades and documents self-hosted open-source platforms in your own infrastructure, typically under a written, fixed-scope agreement, with ongoing support available as a retainer.

Official sources to check before you decide

Before you shortlist either platform, check the licensing, requirements, release windows and pricing against the vendor's own pages, because the answers that decide this comparison sit in those documents. For Mautic, start with the Mautic LICENSE.txt to confirm the GPL terms that apply to the code you will host, then read the Mautic requirements page for the PHP, MySQL or MariaDB, and web server versions your VPS or dedicated server must meet. The requirements page also states that Mautic should not run on shared hosting, which affects your hosting budget before any integration work begins. For Odoo, read the Odoo documentation on licenses to see where the LGPLv3 Community edition ends and the proprietary Enterprise license begins.

Release windows deserve the same scrutiny. Mautic publishes its cadence on the Mautic releases page, and you should confirm which version will carry security support for the full period you plan to run it. Odoo's standard and extended support documentation governs how long a given Odoo version receives security patches, and it limits extended support options for SaaS and on-premise deployments. Compare those dates with your own upgrade calendar. The Odoo pricing page lists plans, and it is the place to confirm which marketing apps, multi-company options and hosting choices sit in each plan.

Feature placement changes between releases, so confirm current edition contents directly with each vendor before you rely on them. Ask Odoo in writing which marketing modules, such as Marketing Automation and Social Marketing, are included in the Enterprise edition you would buy, and whether your chosen Odoo version supports them on-premise. Ask Mautic which integrations, including its HubSpot and Salesforce plugins, are maintained for the version you intend to install. Record the answers, the version numbers and the dates in your evaluation file, and repeat the check at the start of each procurement cycle.

How DeployOpen helps choose, implement or migrate either platform

DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Mautic vs Odoo Marketing, we start by mapping which marketing workflows, CRM data and sending infrastructure you actually need before recommending either path.

How we scope

Written scope lists which Mautic or Odoo marketing features, editions and CRM connections the engagement covers.
We confirm Odoo module edition needs and Mautic hosting requirements against your environment before work begins.
Engagements are fixed-scope, with deliverables and timelines agreed in writing before any work starts.

How we build

We install and configure the chosen platform in your infrastructure, including cron jobs, queues and sending setup.
Integrations with your existing CRM, identity provider and data sources are built and tested against agreed scope.
Security hardening and test environments are prepared so changes can be validated before production use.

How we hand over

Documentation covers architecture, configuration, runbooks for scheduled jobs and upgrade steps for your team.
Evidence and controls relevant to your compliance assessment are documented, though auditors issue any attestation.
Knowledge transfer sessions walk your administrators through daily operation and routine maintenance tasks.

How we support

Ongoing support, upgrades and continuous testing are available as retainers after handover is complete.
Backups and upgrade planning are scoped so each platform's release and support windows stay on your calendar.
Ask any provider for a quote tied to a written scope, including who maintains integrations after launch.

Mautic vs Odoo Marketing