List migration sending for newsletters
PhantomFox runs the list migration system for newsletter operators. A list exported on Monday can be published to on Monday, because the sending capacity here is already warm and asks for no domain, no records and no approval before the first issue goes out.
On this page
Every newsletter operator eventually leaves a platform, and the leaving is where readers are lost. The export is easy. What follows is a verification queue, a domain check and a cautious ramp that costs three or four issues, which is exactly how long a reader takes to forget a habit.
Why does moving a list cost you readers?
Because the new platform treats an imported list as a risk and releases it slowly. The operator who published weekly for two years suddenly publishes once a month while the ramp runs, and opens fall because the rhythm broke rather than because the writing changed.
Some readers never come back from a gap that long. The list survived the move; the habit did not.
How does list migration sending keep the rhythm?
It removes the ramp. Capacity here is warmed before you arrive, so a list imported in the morning receives the normal issue in the afternoon at the normal size, with volume available to ten thousand, a hundred thousand or a million messages by plan.
Nothing is configured, nothing is verified and nobody reviews your subject line first. The steps are written out on how it works.
What does it cost per issue?
Sending is priced per message from a prepaid wallet, so an issue costs what the list size says it costs and there is no monthly seat fee waiting for you between issues. A single send package suits an operator publishing occasionally.
Replies can be pointed at your own inbox, which for a newsletter is usually the most valuable thing the issue produces. Read pricing and the bulk sending page before you export.
| Moving a newsletter | To a normal platform | To warm capacity here |
|---|---|---|
| Export from the old tool | one afternoon | one afternoon |
| Import and verification | queued, then reviewed | immediate |
| First issue after the move | two to three weeks later | the same day |
| Issues missed | three or four | none |
| Reader habit | broken, partly rebuilt | unbroken |
Operators who also sell a product to the list read promotion sending for online stores, and those announcing a live session read invitation sending for event organisers. Export the list and publish the next issue on schedule.