AcelleMail vs phpList — self-hosted email marketing, compared

Le playbook en 7 étapes ci-dessus, chaque action étant détaillée pour l'opérateur. Temps total : environ une demi-journée de mise en place technique, puis 1 à 5 jours pour reconstruire les modèles & les automatisations selon la complexité des listes.

1. 1. Export from phpList. phpList stores subscribers, lists, and campaigns in its own MySQL database. Export subscribers to CSV from the phpList admin (Subscribers → Export), or query the phplist_user_user and list tables directly for very large sets. Note your custom attributes and which lists each subscriber belongs to so you can recreate the structure. (Still weighing open-source options? See our open-source email marketing roundup.)
2. 2. Get AcelleMail. Buy the Regular Licence — $80 on CodeCanyon. Upload the ZIP and run the 5-minute web installer (DB, admin user, cron). PHP 8.1+, MySQL ≥ 5.7 or MariaDB ≥ 10.3, ~512 MB RAM minimum. The installation guide covers cPanel, DigitalOcean, AWS, and Docker.
3. 3. Connect your sending service. If phpList was sending through SMTP or Amazon SES, add the same provider in Sending Servers → Add and paste your credentials — your SES domain/identity carries over. AcelleMail also adds SendGrid, SparkPost, Mailgun, Elastic Email, Blastengine, Gmail relay, generic SMTP, and a plugin SDK if you want to broaden later. AcelleMail generates the SPF/DKIM records and signs DKIM at the app layer; run the test-send to confirm.
4. 4. Import subscribers + attributes. In Lists → Create List, recreate each phpList list (and its custom attributes as AcelleMail custom fields). Use Import → Upload CSV and map columns one-to-one. For lists over 100k, use the chunked import or seed via the REST API. Subscriber confirmation/opt-in status maps to AcelleMail subscriber states.
5. 5. Recreate templates + campaigns. Paste your phpList HTML templates into AcelleMail's template editor, or rebuild in the drag-and-drop builder. Scheduled phpList newsletters become AcelleMail campaigns; if you want to evolve beyond broadcasts, lay out a workflow in Automation → New Workflow (trigger → wait → send, plus condition/branch nodes for behavior-driven journeys).
6. 6. Configure tracking + DKIM. Open/click tracking is on per campaign by default (open pixel + link wrapping). DKIM signing is configured at the Sending Server level — publish the DNS records AcelleMail generates. If you keep the same sending domain and vendor as your phpList install, existing DKIM keys can usually be reused; otherwise publish new records and let DNS propagate before cutover.
7. 7. Test deliverability + cut over. Send a test to GlockApps or Mail-Tester (free) and aim for 9.5/10. Run your next live campaign from AcelleMail in parallel for one cycle, compare open/click rates to your phpList baseline, then retire the phpList install. Most teams cut over inside a week.

Le tableau de comparaison ci-dessus montre la parité des fonctionnalités ; voici le contexte supplémentaire pour chaque ligne assortie d'une note non triviale — utile lorsque l'une des plateformes est « partielle » et qu'il vous faut le contournement.

Email creation

• Drag-and-drop email builder: AcelleMail ships a drag-and-drop editor with mobile preview + a starter template gallery. phpList centers on a WYSIWYG editor and reusable templates; a full block-style drag-and-drop builder is not its headline feature.
• A/B testing: AcelleMail supports subject-line and content split tests in core. In phpList, A/B-style testing is not a core built-in; confirm current plugin availability for your version.
• Spintax / per-subscriber merge fields: AcelleMail includes spintax + per-subscriber merge tags. phpList supports personalization/placeholders; spintax-style randomization is not advertised.

Lists & segmentation

• Visual segment builder (any-condition): AcelleMail provides a visual segment builder over fields, behavior, tags, and date logic. phpList supports segmentation by attributes/list membership; a visual any-condition builder is not its primary UI.

Automation

• Visual multi-step workflow builder: AcelleMail ships Automation2 — a visual canvas with trigger / wait / condition / branch / segment-move nodes. phpList's core is newsletter sending rather than a branching visual journey builder.
• Conditional branching: AcelleMail branches a journey on engagement, tags, or field logic in the UI. In phpList, multi-branch journeys are not a built-in core feature.
• Behavioral triggers (clicks / opens): AcelleMail exposes engagement events as automation triggers. phpList records opens/clicks for reporting; using them to branch a journey is not a built-in workflow feature.

Deliverability

• Multiple sending services: AcelleMail ships 8 built-in drivers + generic SMTP + a plugin SDK. phpList sends via SMTP/mail transport by default; SES and other providers are reachable via SMTP or plugins.
• Click maps + spam scoring: AcelleMail provides click heatmaps and SpamAssassin-style scoring per campaign. phpList provides open/click reporting; bundled spam-score scanning is not a headline feature.

Integrations

• WordPress / WooCommerce: AcelleMail ships an official WordPress/WooCommerce plugin. phpList integrates with WordPress via community plugins + its API.
• Zapier / Make / n8n: AcelleMail is pre-listed on Zapier / Make / n8n. phpList is reachable from these via its REST API.

SaaS / multi-tenancy

• White-label client accounts: AcelleMail Extended provides per-customer accounts for reselling. phpList is a single-tenant admin tool; running it for many billed clients means separate installs or building a tenancy layer yourself.
• Subscription plans + payment gateways: AcelleMail Extended bundles subscription plans + 6 payment gateways (Stripe, PayPal, Braintree, Razorpay, Paystack, Offline). phpList has no bundled recurring-billing layer.
• Prorated upgrades + dunning: AcelleMail's Cashier package covers prorated upgrades + failed-payment dunning. Not a phpList feature.

Cost & ownership

• License cost: phpList self-hosted is <strong>free</strong> (AGPLv3) — the clearest cost advantage. AcelleMail Regular is $80 one-time; Extended is $199 (adds the SaaS layer + 6 months support).

La carte TCO ci-dessus présente les chiffres d'entrée de gamme ; cette vue empile les trois profils d'acheteurs côte à côte afin que vous puissiez retenir celui qui colle au mieux à votre volume de contacts et à votre fréquence d'envoi.

Nonprofit / community newsletter — 5,000 subscribers

• Situation : Monthly newsletter to members, strong need for clean lists + bounce handling, tight budget.
• Coût phpList : phpList free + $5/mo VPS + ~$0.30/mo SES. Excellent fit — mature list management and bounce processing at zero licence cost.
• Coût AcelleMail : $80 once + $5/mo VPS + ~$0.30/mo SES. Worth it only if you want a drag-and-drop builder, A/B testing, or room to add automation later.

SaaS team — product newsletter + onboarding journey

• Situation : 8,000 trial signups + 2,000 paid, weekly newsletter, a 4-step onboarding that branches on whether the user activated.
• Coût phpList : phpList free + $10/mo VPS + ~$2/mo SES. The newsletter is a great fit; the branching activation journey would need custom work against the API or a different tool.
• Coût AcelleMail : $80 once + $10/mo VPS + ~$2/mo SES. The onboarding is one visual workflow — trigger on signup → wait → check activation → branch — built in the UI without external code.

Agency — 50 client accounts, billed monthly

• Situation : Email service for 50 small-business clients, ~2,000 subscribers each, monthly newsletters, recurring billing.
• Coût phpList : phpList free, but single-tenant: you would run separate installs or build a tenancy + billing layer yourself + ~$40/mo VPS + ~$30/mo SES. Free licence, but real build/ops cost.
• Coût AcelleMail : $199 Extended once + ~$40/mo VPS + ~$30/mo SES across all clients on one install. Built-in SaaS: per-client login, subscription plans, 6 payment gateways, prorated upgrades, dunning.

Utilisez le calculateur d'économies pour obtenir un chiffre personnalisé en fonction de votre nombre exact d'abonnés et de votre fréquence d'envoi.

Quatre objections que tout opérateur soupèse avant de migrer depuis phpList ou tout autre SaaS. Réponses sans détour — ce sont de véritables arbitrages, et le bon choix dépend de votre équipe.

1. « Le changement coûte plus cher qu'il ne rapporte. »

Évaluation honnête : pour des listes inférieures à ~500 contacts, l'offre gratuite ou l'entrée de gamme de phpList peut être plus économique qu'un VPS à 5–10 $/mois plus la licence AcelleMail — avant même de compter le temps de l'opérateur. Le point d'équilibre se situe en règle générale entre 1 000 et 5 000 contacts. Faites vos propres calculs via le calculateur de coût avant de trancher.

2. « La délivrabilité va s'effondrer en auto-hébergement. »

Vrai si vous opérez un MTA auto-géré sans warmup. FAUX lorsque AcelleMail relaie via un service d'envoi managé (Amazon SES, SendGrid, Mailgun, Postmark) — ces prestataires gèrent la réputation IP ; AcelleMail n'orchestre que les campagnes et le tracking. Atteindre une parité de placement en boîte de réception avec phpList est la norme, non l'exception, avec cette configuration.

3. « Mon équipe n'a pas le temps d'apprendre un nouvel outil. »

Préoccupation légitime. L'interface de AcelleMail reprend les schémas usuels (constructeur de campagnes, listes d'audience, flux d'automatisation), si bien que la plupart des utilisateurs de phpList sont productifs dès le premier jour. Le véritable poste de temps est la reconstruction des automatisations multi-étapes et des bibliothèques de modèles — comptez 1 à 5 jours selon la complexité, pas des semaines.

4. « Et si AcelleMail cessait d'être maintenu ? »

L'auto-hébergement inverse le risque : vous possédez une copie perpétuelle du code source. Aucune évolution tarifaire, dépréciation ou acquisition d'un éditeur ne peut vous priver de la plateforme. Si les mises à jour cessent, votre installation existante continue de fonctionner. À comparer avec un SaaS où les décisions de l'éditeur sur le prix, les fonctionnalités ou l'arrêt du service sont unilatérales.

Yes. phpList keeps subscribers, lists, and campaigns in its own MySQL database — export subscribers to CSV from the admin (Subscribers → Export) or query the tables directly for very large sets. AcelleMail's import accepts CSV with custom-field mapping (plus XLSX or direct DB seed). phpList list membership and custom attributes map to AcelleMail lists and subscriber fields one-to-one, and opt-in status carries over. Plan a half-day for a list under 5,000; 2–3 days if you also rebuild sequences as workflows.

You often would not. phpList self-hosted is genuinely free under AGPLv3 and is excellent at newsletters, list management, double opt-in, and bounce handling. AcelleMail is a paid one-time licence ($80 Regular) whose value is the bundle, not a lower price: a visual branching automation builder, 8 built-in sending drivers + a plugin SDK, a drag-and-drop editor, A/B testing, and the Extended path ($199) to a multi-tenant SaaS layer with subscription plans, 6 payment gateways, prorated upgrades, and dunning. If you only need broadcast newsletters, phpList's free licence is the rational choice; AcelleMail earns its price when you need automation, multi-provider sending, or a reseller layer.

phpList is built around newsletters and scheduled campaigns with list logic; multi-step branching journeys are not its core. AcelleMail ships Automation2 — a visual workflow builder with trigger / wait / condition / branch / send / segment-move nodes — so you can build a behavior-driven journey (e.g. signup → wait → check activation → branch) in the UI without external code. If your sends are broadcasts and simple sequences, phpList is fine; if you want branching automation, that is the AcelleMail difference.

AcelleMail ships 8 built-in drivers — Amazon SES, SendGrid, SparkPost, Mailgun, Elastic Email, Blastengine, Gmail relay, and generic SMTP — plus a plugin SDK for more. phpList sends through the server's SMTP/mail transport by default, and SES or other providers are reachable via SMTP or phpList plugins. If you want to add or mix several providers from a built-in UI, AcelleMail covers that out of the box; with phpList you configure SMTP or add the relevant plugin.

AGPLv3 makes phpList fully open and free to use, modify, and self-host — with a copyleft condition: if you distribute a modified version (including offering it as a network service in some readings), you must make your source available under the same licence. That is ideal for openness. AcelleMail ships full unencrypted PHP source under a commercial CodeCanyon licence, which lets you modify it privately and resell under your own brand with no copyleft obligation. Choose AGPL-open if maximum openness fits your use; choose AcelleMail's commercial terms if you need private modifications or a closed reseller product.

Yes. phpList is a single-tenant administration tool, so serving many billed clients means separate installs or building a tenancy + billing layer yourself. AcelleMail's Extended Licence ($199) ships customer accounts plus a billing layer: subscription plans, 6 payment gateways (Stripe, PayPal, Braintree, Razorpay, Paystack, Offline), prorated upgrades, and dunning — all on one install. See the For Developers page for the architecture.

Both are PHP + MySQL apps you self-host. phpList has a small, long-stable footprint and runs on modest/shared hosting. AcelleMail needs PHP 8.1+, MySQL ≥ 5.7 or MariaDB ≥ 10.3, ~512 MB RAM minimum, and a cron entry for campaign workers; an optional Redis cache and queue workers support higher volume and the automation engine. AcelleMail is a Laravel application, so it has more moving parts than a focused newsletter tool — the trade-off for bundled automation, multi-tenancy, and a plugin runtime.

Both let you read and change the code. phpList is fully open under AGPLv3 — maximum inspectability, with copyleft when you distribute changes. AcelleMail ships full, unencrypted PHP source under its commercial licence; you can modify it, and private modifications carry no copyleft obligation. AcelleMail also exposes a four-pattern Hook plugin SDK (REGISTRY, EVENT, FILTER, BEHAVIOR) so you can add sending drivers, payment gateways, and UI panels without forking core.

phpList. For broadcast newsletters with strong list management, double opt-in, and bounce handling — and no need for branching automation, multi-provider sending from a UI, or a reseller billing layer — phpList does the job maturely and for free. Choose AcelleMail when you expect to grow into visual automation, more sending drivers, a drag-and-drop builder, or multi-tenant reselling, and want those bundled in one tool you can also modify privately.