Can I migrate from phpList to AcelleMail without losing subscriber data?
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.
phpList is free and open-source — why would I pay for AcelleMail?
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.
How does AcelleMail's automation compare to phpList?
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.
Does AcelleMail support more sending services than phpList?
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.
What does phpList's AGPLv3 licence mean for me versus AcelleMail's commercial licence?
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.
Can I run client accounts and resell with AcelleMail? phpList is single-tenant.
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.
What stack and resources does AcelleMail need compared with phpList?
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.
Is AcelleMail's source code editable, given phpList is fully open?
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.
Which is the right choice for a simple newsletter with no automation needs?
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.
