Does self-hosted Mautic cost less than Account Engagement?
Mautic has no license fee, so the answer depends on what you pay recurringly to run it against what you pay Salesforce for Account Engagement today. The Mautic software is licensed under GPL-3.0, according to the license file in its repository, and the project offers the free self-hosted download with no paid edition of the software itself. Your side of the comparison is therefore infrastructure (a VPS or dedicated server, since the project advises against shared hosting), email sending, the time your team spends keeping Mautic and its Salesforce connection current, and support. The GPL-3.0 point describes how the software is licensed, not how your contracts or obligations are affected, so confirm any licensing questions with your legal team.
Account Engagement pricing is not something this page can state. Edition prices, contact or prospect limits, and any add-ons must come from your own Salesforce order form and renewal paperwork, because published figures change and depend on negotiated terms. Pull the current edition, the prospect count you are billed on, and the renewal date, then build the Account Engagement line from those. Ask your Salesforce account team to confirm in writing which limits apply to your org, since overage terms matter as your database grows.
The largest front-loaded cost on the self-hosted side is the one-time migration of prospects, programs and scoring. Mautic imports contacts from CSV and recommends background imports for large files, so the data movement itself is modest, but rebuilding nurture programs as campaigns, mapping scoring and grading rules, and validating the Salesforce plugin usually take the most staff time. Price that work as a fixed-scope project with a written deliverable list, whether an internal team or an implementation partner does it, and ask any partner for a quote built from that scope. Once migration is complete, the recurring costs are hosting, sending, patching and staff time, and those are the lines to compare against the Account Engagement renewal.
Which cost components move between the two sides
This table sets each cost component of Account Engagement against its self-hosted Mautic counterpart and marks whether it is one-time or recurring. Read it to see where spending shifts from a vendor subscription to your own infrastructure, staff and partner work, and which items you should price on both sides before comparing totals.
| Cost component | Account Engagement side | Self-hosted Mautic side | One-time or recurring |
|---|---|---|---|
| Subscription or license | Salesforce subscription to Account Engagement, sized by edition and contact tier; confirm current terms in your order form | No license fee for the software under GPL-3.0; cost is the infrastructure and people that run it | Account Engagement: recurring. Mautic: none for software |
| Contact or edition tiers | Tiers and contact limits set the subscription; growth in prospects can move you to a higher tier | No contact tier; cost rises with database size, sending volume and server capacity | Recurring on the commercial side; capacity costs recur on the self-hosted side |
| Hosting | Included in the vendor subscription | VPS or dedicated server, since the Mautic requirements page says shared hosting is not supported; PHP 8.2 to 8.5 and MySQL 5.7 or MariaDB 10.2 or higher | Recurring |
| Email sending | Usually included in the subscription within sending limits; confirm limits and any overage terms | Separate SMTP or transactional email provider billed by volume, plus sending domain and reputation work | Recurring |
| Salesforce integration | Native connection maintained by Salesforce as part of the platform | Mautic Salesforce plugin, configured from the Mautic documentation; setup and ongoing upkeep through your team or partner | Setup is one-time; upkeep recurs with Salesforce and Mautic releases |
| Implementation | Salesforce or partner configuration of Account Engagement features and tracking | Installation, cron and queue setup, plugin configuration and integration testing | One-time |
| Migration of prospects and programs | Export of prospects and activity from Account Engagement, then rebuilding Engagement Studio programs | CSV import through the Mautic interface or the background import command, then rebuilding programs as campaigns | One-time |
| Support | Vendor support covered by the subscription tier you hold | Paid support or retainer from a provider, or internal staff time; confirm response expectations in writing | Recurring |
| Upgrades | Handled by the vendor on its release schedule | Mautic releases follow a monthly patch, quarterly minor and two-yearly major cadence; each upgrade needs testing and planning | Recurring |
| Internal skills | Admin and marketing operations roles focused on Salesforce configuration | Staff or partner time for PHP, database, cron, email deliverability and Salesforce plugin maintenance | Recurring |
What moves the comparison most
Six variables decide whether self-hosted Mautic or Account Engagement costs less for your team. Several of them interact, so measure each one before you compare quotes or list prices. The figures below are for your own environment, and each card says how to measure it.
Contact volume per tier
Account Engagement pricing depends on the number of prospects and contacts in your org, so this is usually the first line of any quote. Mautic has no contact-based license, so its cost grows with database size, hosting capacity and the work needed to keep queries fast. Export your current prospect count from Account Engagement and note how many records are inactive for more than a year, since many teams can archive or purge those before migration. Ask your Salesforce admin whether the count matches the Salesforce lead and contact totals.
Send volume and deliverability work
Sending cost depends on how many emails you send each month, and on who manages sender reputation. Under Mautic, your team or partner owns the sending domain, SPF, DKIM and DMARC records, bounce handling and complaint monitoring, so you need an SMTP or transactional email provider with its own fee. Pull the last twelve months of monthly send volume and bounce and complaint rates from Account Engagement reporting. Ask whether your sending provider's pricing is based on volume or on the number of contacts.
Salesforce users and synced objects
The Salesforce integration is where most of the ongoing work sits. Account Engagement is native to Salesforce, while Mautic connects through its Salesforce plugin, which needs configuration, field mapping and monitoring for each object you sync. Count the Salesforce users who work with marketing records, plus the objects in scope such as leads, contacts, accounts, campaigns and custom objects. Each additional object or custom field adds mapping and testing work that recurs after every Salesforce release.
Active programs to rebuild
Each active Engagement Studio program, nurture or automation must be rebuilt as a Mautic campaign, and the rebuild is a one-time cost that scales with program count and complexity. Simple drip sequences move quickly, while programs with branching logic, scoring thresholds and Salesforce-triggered actions need more testing. Export a list of active programs with their steps, triggers and last-modified dates, then mark which ones still run. Retired or duplicate programs should be removed before you estimate rebuild effort.
Availability and on-call coverage
Account Engagement's availability is provided by Salesforce, so your team does not staff for uptime of the platform itself. A self-hosted Mautic instance needs monitoring, patching, backups and someone on call for failed sends or stalled jobs. Define the availability your marketing team needs, such as whether a broken send at 8 pm can wait until morning. Ask any partner quoting support to state response times in writing, since DeployOpen offers ongoing support as a retainer priced from the written scope.
PHP, Linux and cron skills
Mautic runs on PHP with Symfony, a Linux web server, a MySQL or MariaDB database and scheduled cron jobs for segment updates, campaign triggers and broadcasts, so the skills you already have determine whether the work stays in house. Mautic also requires a queue consumer when emails are queued, and the documentation says cron jobs should be staggered. Survey your current team for these skills before you decide on internal staffing or outside support. If the team has no PHP or Linux operations experience, budget for training or partner support as a recurring cost.
How to build the comparison with your own numbers
This sequence turns the cost question into a three-year comparison built from your own contact counts, send volumes, order form lines and migration scope. Each step ends with a figure you can check against your contract and your environment before any vendor quote is requested.
Record your current contact count and send volume
A marketing operations lead pulls the active prospect count and the monthly email volume from Account Engagement, along with the number of prospects that received email in the last twelve months. Record the figures by month for at least the last year so seasonal peaks are visible. Confirm with your Salesforce administrator how many prospects are synced to CRM, since those records drive both the Account Engagement bill and the sync effort. The step is done when you have one table of monthly contacts and sends that you can reuse in every later step.
Pull subscription lines from the order form
Someone with access to the signed order form and renewal paperwork lists every recurring line item: edition, contact tier, add-on packs, sandbox or additional environments, API access and support level. Mark which lines are tied to contact count and which are fixed, and note the renewal date and any uplift clause. Ask your Salesforce account team to confirm in writing that the list is complete, because add-ons are often on separate order lines. The step is done when the recurring total for a full year is written down with its source document named.
Price a hosting environment for Mautic
Your infrastructure or platform team prices a VPS or dedicated server in your own cloud account or data center that meets the Mautic requirements, which the project says must not run on shared hosting. Include a production server, a staging copy for upgrades, backups, monitoring, and the database service Mautic supports (MySQL 5.7 or higher with InnoDB, or MariaDB 10.2 or higher). Price the items against your existing cloud rates rather than public list prices, and note which items are one-time setup and which recur monthly. The step is done when you have a recurring hosting line and a one-time setup line, each with the rate card it came from.
List every cron job and queue consumer
A platform engineer inventories the background work Mautic needs: cron jobs for segment updates, campaign updates and campaign triggers, which the documentation says should be staggered, the broadcasts command for segment emails, and a messenger consumer for queued email. Decide where each job runs, how it is restarted after a failure, and who receives alerts when it stops. Add the scheduled import job if you plan large CSV loads. The step is done when every job and consumer appears on one list with an owner and a monitoring check, because each one is ongoing operational work you will carry.
Estimate migration effort per program and prospect set
A marketing operations lead and a Salesforce developer split the migration into workstreams: prospect and activity export, contact import through the Mautic interface or the background import command, rebuilding each Engagement Studio program as a Mautic campaign, mapping scoring and grading, and connecting the Salesforce plugin. Count the programs, the custom fields and the prospect sets by type, then estimate effort for each item in hours by role. Use your own team's past delivery as the baseline, and ask any implementation partner to price the same list in a written scope. The step is done when every workstream has an effort estimate, a named owner and a one-time cost line.
Add support and upgrade time
Your team estimates recurring operational effort across the Mautic release cadence: monthly patch releases, minor releases about every three months and major releases every two years. Check the current support windows on the Mautic releases page, since each release has its own end-of-support date, and plan for the upgrade and regression test cycle each time. Add time for PHP and database version changes, plugin updates, backup tests and incident response, and decide whether a retainer with an external provider covers any of it. The step is done when you have a recurring hours figure per month and a note on which release line you will run.
Compare three-year totals
Finance and the marketing operations lead build one three-year model with two columns: the current Account Engagement contract, with its expected renewal uplift, and the Mautic option with hosting, sending, plugin upkeep, support, upgrades and the one-time migration. Show the illustrative example first with invented numbers so the structure is clear, then replace every value with your own figures and sources. Test the result against a range of contact growth rates, because the Account Engagement bill and some sending costs scale with volume. The step is done when the model shows each line's source, and the difference between the two totals can be explained line by line to the budget owner.
Where self-hosting can cost more than staying
Self-hosting Mautic does not always lower total cost, and for some Account Engagement customers staying on the commercial product is the cheaper and simpler choice. The clearest cases are small contact counts, where the fixed cost of a server, database, mail infrastructure and staff time can outweigh the license savings, and teams with no spare engineering capacity to patch, upgrade and monitor a PHP application on a schedule. Mautic's own requirements page says it should not run on shared hosting and recommends a VPS or dedicated server, so even the hosting line is a real decision. Before you decide, ask your Salesforce partner or Account Engagement contact for your current edition, contact limit and any add-on fees in writing, then compare that quote with a written estimate for your own hosting and staff hours.
Several Account Engagement features carry hidden value that is hard to price. If your team relies on the native Salesforce sync, custom Account Engagement reports and built-in deliverability handling, a plugin-based setup means you must test, own and repair that connection yourself. Deliverability is the hardest item to staff. Sending from your own servers means you manage sender reputation, bounce and complaint handling, and authentication records for each sending domain, and a weak setup can hurt both your marketing and your sales email. Confirm internally who will own those tasks before you move. Also check whether your legal or security reviewers require vendor-issued evidence, such as third-party attestation reports. DeployOpen can prepare your own controls and evidence, but it cannot issue audit reports, so a hosted vendor may be simpler when those documents are a hard requirement.
Cost, effort and skills questions buyers ask before hiring help
How much does migrating from Account Engagement to Mautic cost?
The migration cost depends on the scope agreed in writing, not on a fixed price. DeployOpen does not publish a price list, and a quote follows from a written scope that covers the number of prospects and activity records to move, how many Engagement Studio programs need rebuilding as Mautic campaigns, how the Salesforce plugin is configured, and the hosting and integration work. Ask for the cost split into one-time work (export, import, campaign rebuild, testing, cutover) and recurring items (hosting, email sending, support). Ask which items the quote excludes, such as Salesforce admin time on your side.
How long does a Mautic migration take?
Timeline follows the scope, so the main drivers are the size of the prospect database, the number and complexity of Engagement Studio programs, the scoring and grading rules to map, and how many Salesforce integration points must be tested. Account Engagement's Export API produces files asynchronously, so export planning and data validation add steps before any import begins. Ask for a timeline with named milestones and the client dependencies behind each one, including access to the Salesforce org and approval of the cutover window.
Can an internal team migrate to Mautic without outside help?
Yes, if the team has the skills to install and operate a PHP application on Symfony, configure a database, schedule cron jobs, and work with the Salesforce plugin and its authentication. Mautic's requirements page calls for a VPS or dedicated server rather than shared hosting, and the documented installation paths include the web installer, the command-line installer and Composer. Teams with limited spare capacity often weigh the work against a fixed-scope engagement. Ask whether your team has run a PHP application in production before and who will own patching.
What does the work need from our Salesforce admin and IT team?
The Salesforce admin owns the org-side tasks: connected app or OAuth setup for the Mautic Salesforce plugin, field mapping between Mautic and Salesforce objects, lead and contact matching rules, and validation of records after sync. IT owns the server, database, DNS, TLS certificates, email sending domains, backups and network access between Mautic and Salesforce. Agree the access model and change window in writing before work starts. Ask the implementation partner which tasks they perform and which they expect your staff to perform.
What recurring costs remain after a self-hosted Mautic launch?
Recurring costs are the infrastructure to run Mautic, the database and backups, the email sending service that delivers your messages, staff time for patching and upgrades, and any support or retainer you buy. Mautic itself is free to self-host under the GPL-3.0 license, so the software line item is not the main cost. Mautic's release model includes monthly patch releases, minor releases every three months and major releases every two years, and each version has its own support end date, so plan upgrade effort on that cycle. Ask for the recurring items listed separately in the quote.
How does the self-hosted total compare for a small versus a large contact base?
Mautic's software cost does not scale with contacts, but the components around it do. A small database can run on modest hosting, while a large contact base increases database size, cron and segment processing load, email volume and the time needed for imports and upgrades. Account Engagement pricing is tied to contact limits and edition, so the crossover point depends on your current edition and the contact count. Build the comparison with your own edition invoice, contact counts and sending volume, and ask a partner to model both sizes in the quote.
How do we request a quote for a Mautic migration?
Send a written description of your current Account Engagement setup, the Salesforce org details your team can share, the approximate number of prospects and programs, your sending volume, and any compliance or data residency requirements. DeployOpen plans, implements and supports self-hosted platforms in your own cloud accounts, data centers or air-gapped networks, and most engagements are fixed-scope with scope, deliverables and timelines agreed in writing before work starts. A quote follows from that written scope. Ask for the assumptions, exclusions and acceptance criteria in the quote before you sign.
One-time migration costs for prospects and programs
The one-time cost of leaving Account Engagement is mostly labor and parallel running, not software. The main work items are exporting prospects and activity, loading them into Mautic, rebuilding Engagement Studio programs as Mautic campaigns, re-creating scoring and grading logic, reconnecting the CRM, and running both systems side by side until cutover. Each item has a driver you can size before you ask for a quote: the number of prospect records, the volume of historical activity you need to keep, the count of active programs, and how many scoring rules and grading thresholds exist. Ask the implementation partner to scope each item separately so you can see which ones scale with data volume and which scale with design complexity.
For contacts, Mautic's CSV import maps columns to fields automatically in the user interface, but the project recommends background imports through the mautic:import console command run by cron for large files, which processes rows in batches of 100 by default. Plan for a test import on a copy of a representative file, then check duplicate handling, opt-in and do-not-contact fields, and custom field types before the full load. Confirm the exact export format and field names your Account Engagement org produces, since mismatches here cause most rework.
Engagement Studio programs and scoring rules need manual redesign, and this is usually the largest human effort. Expect to rebuild each program as a Mautic campaign with its own triggers, decisions and emails, and to translate point values and grade criteria into Mautic's own points and segment logic. Parallel running is the cost that most often gets underestimated: keep Account Engagement live while Mautic sends test sends, reconciles engagement data and confirms the Salesforce sync for at least one full sales cycle. Ask any partner to put that overlap, and the subscription you keep paying during it, into the written scope.
How DeployOpen scopes a fixed-price Mautic implementation
DeployOpen is a Chainscore Labs company that plans, implements, integrates, hardens, backs up, upgrades and documents self-hosted open-source platforms inside your own infrastructure. For a move off Account Engagement, we turn the cost comparison into a written scope covering hosting, Salesforce integration, email sending and the one-time migration of prospects and programs.
How we scope
- Inventory your Account Engagement edition, contact count, active programs and Salesforce objects before any quote is written
- Agree in writing which prospects, activity history and custom fields move to Mautic and which stay in Salesforce
- Define hosting location, database, email sending path and cron schedule so recurring costs are visible up front
- Confirm the Salesforce plugin scope and any data you need to keep for reporting and audit trails
How we build
- Install Mautic on a VPS or dedicated server in your cloud account or data center, not on shared hosting
- Configure the Salesforce plugin, staggered cron jobs, the broadcasts command and the messenger consumer for queued email
- Import contacts through background imports with mautic:import rather than a single browser upload for large files
- Rebuild priority programs as Mautic campaigns and test scoring, grading and suppression logic against sample records
How we hand over
- Document the deployed architecture, cost components and the cron and queue jobs your team must monitor
- Provide a migration record showing record counts exported, imported and reconciled against the source
- Train your marketing operations and Salesforce administrators on campaign building and plugin sync checks
- Deliver backup and restore runbooks so your team can rebuild the instance from documented steps
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Plan Mautic upgrades against the project's published release and security support windows for your version
- Schedule periodic security testing of the Mautic instance and its Salesforce connection when your risk policy requires it
- Ask for the retainer scope in writing, including who applies upgrades and how security patches are handled
