A Woodpecker Alternative Guide to Limits That Follow the Mailbox
Some limits travel with your mailbox and some stay inside the software you leave. Provider caps, per-mailbox daily volume and domain reputation follow you. Sequence caps, warm-up rules and account tiers belong to the tool. Reconfigure mailbox health and sending volume first, then rebuild sequences.
Updated October 29, 2026
Which Limits Are Attached to the Mailbox Itself
Your sending provider sets the ceiling that no sequence tool can move. Daily volume per mailbox, hourly throttles and connection limits live at the SMTP endpoint. If you move to a new platform and point it at the same mailbox, those caps arrive with it unchanged. The software is a driver, not the engine, so the engine keeps its own rules.
Domain reputation also follows you. Authentication records, sending history and complaint behavior belong to the domain, not to the vendor you are leaving. A fresh tool will not reset any of that. Expect the first weeks on a new platform to look like the last weeks on the old one from the provider's point of view.
This is why a migration checklist starts with the mailbox. Confirm what your provider publishes about daily and hourly limits, then choose a plan that stays underneath them. Mail Pro at $149 includes warm-up on every account, which matters when the reputation history is the thing you are carrying across.
- List the daily and hourly caps your sending provider publishes for each mailbox
- Record current domain authentication records and keep them unchanged during the move
- Note which mailboxes are already warmed and which are new
- Decide whether you keep the same SMTP endpoint or switch providers
If the cap question is really about which tool to point at your mailboxes next,compare another sequence platformand check how it handles per-mailbox volume before you commit.
Which Limits Stay Inside the Software You Leave
Sequence caps, contact tiers, warm-up schedules and reply-detection rules are software behavior. They do not travel with the mailbox. A tool that capped you at a certain number of prospects or campaigns simply stops applying when you cancel it. That part of the migration is genuinely a reset.
The trap is rebuilding the same restrictions in the new platform out of habit. Many teams copy their old sending pattern exactly and wonder why nothing changes. If the old tool held you to a conservative daily number per mailbox, decide deliberately whether that number still serves you, rather than importing it by default.
Audit what you actually used. Export sequences, templates and suppression lists before the subscription ends. Anything you cannot export is a manual rebuild, so budget time for it. Then read the new vendor's published terms rather than assuming features carry over by name.
- Export sequences, templates and reply templates while access is still active
- Download suppression and unsubscribe lists in a portable format
- Write down the old daily sending pattern so you can decide on it consciously
- Check the new vendor's published limits page instead of assuming parity
Teams comparing several exits oftenreview a second alternativeto see how another platform structures its sending and contact limits.
Reconfigure Mailbox Health Before You Rebuild Sequences
Order matters. Point the new platform at your existing mailboxes, verify SMTP and IMAP settings, and confirm a test send arrives before you import a single prospect. A sequence that fires into a broken connection wastes the first days of a warmed mailbox.
Next, set volume per mailbox below the provider ceiling, not at it. Then rebuild warm-up if the new tool offers it, and only after that recreate sequences. Reply handling comes last, because it depends on the inbox connection already working.
LocalSMTP at $149 gives five verified SMTP accounts with SMTP and IMAP settings and lifetime access. For a small sending operation that is often the whole infrastructure layer, and it lets you test the connection independently of the sequence software.
- Verify SMTP and IMAP on every mailbox and send one live test message
- Set per-mailbox daily volume below the provider's published cap
- Enable warm-up before adding any new mailbox to a live sequence
- Reconnect the reply inbox and confirm a test reply is detected
Once the mailboxes are stable,choose the sending softwarewith attention to how each option handles per-mailbox volume and reply routing.
Reputation and Domain Settings You Carry Across
SPF, DKIM and DMARC records live in DNS, not in the old vendor's account. Leave them in place. Changing authentication during a platform migration gives receivers two changes to interpret at once, and you lose the ability to tell which one caused a problem.
If the old tool used its own tracking domain, decide whether to keep or drop it. Custom tracking domains add a second name to warm. Many teams simplify during a move and send without link tracking for the first weeks.
Bulletproof IP at $249 bundles a lifetime guide library, lifetime IP and geo tooling, and one month of Basic VPS. It is a reference and tooling layer rather than a sending platform, useful when you want the DNS and IP decisions documented before you commit.
- Leave SPF, DKIM and DMARC records unchanged through the migration
- Decide explicitly whether to keep a separate tracking domain
- Check whether the new platform sends through shared or dedicated infrastructure
- Document the IP and domain setup so the next move is faster
A Worked Example on Published Prices
Suppose you run three mailboxes and want a managed sequence tool plus SMTP infrastructure. On this site, Starter at $18/month covers 2,000 emails per month with one SMTP slot and AI assistance. That is one mailbox connected at a time, so three mailboxes need a plan with more slots or a staggered setup.
Pair that with LocalSMTP at $149 for five verified SMTP accounts on lifetime access, and the infrastructure question is settled independently of the monthly plan. Growth at $38/month raises the ceiling to 10,000 emails per month and adds a reply inbox plus API keys.
Run the arithmetic on your own volumes. If three mailboxes each send 40 messages on a working day, that is 120 sends daily, roughly 2,600 in a month of about 22 working days. Starter's 2,000 monthly emails would not cover it, while Growth's 10,000 would with room to spare.
- Multiply mailboxes by daily sends, then by working days, to get a monthly figure
- Compare that figure against the published monthly email allowance
- Check the SMTP slot count against the number of mailboxes you connect
- Decide whether lifetime SMTP infrastructure removes a recurring cost
Mailbox and SMTP options for rebuilding sending after a platform move
| Option | Price | What you get | Best for |
|---|---|---|---|
| LocalSMTP | $149 | Starter 5, five verified SMTP accounts, SMTP and IMAP settings, lifetime access | Teams that want the sending layer settled once and separately from sequence software |
| Mail Pro | $149 | Lifetime unlimited licence, unlimited contacts and mailboxes, warm-up on every account | Senders running several mailboxes who need warm-up built in |
| AI Sales Agent | $149 | Starter lifetime, 2,000 managed sends per month, one sender identity, AI-written sequences | A single sender who wants managed sequences without running infrastructure |
| Bulletproof IP | $249 | Platform lifetime, lifetime guide library, lifetime IP and geo tooling, one month Basic VPS | Teams documenting DNS and IP decisions before they commit |
| FindSend.Email | $199 | Starter lifetime, 300 finds per month, 300 sends per month, one workspace | Small operations that need prospect finding and sending in one place |
Each figure is the published one-time price for that lifetime deal, and code SALE20 takes 15% off lifetime deals at checkout.
What This Migration Approach Will Not Do
Moving platforms changes software limits, not provider policy or domain history. Be clear about what stays fixed so you plan around it rather than against it.
- It will not raise the daily or hourly caps your sending provider publishes for a mailbox
- It will not reset domain reputation, complaint history or authentication state
- It will not export sequences from a tool that offers no export, so some rebuilding is manual
- It will not protect deliverability if you set volume at the provider ceiling from day one
- It will not carry over reply threading if the old tool stored replies only in its own interface
Frequently asked questions
Do sending limits reset when I change sequence tools?
Only the software limits reset. Provider caps per mailbox, hourly throttles and domain reputation follow the mailbox and domain. Check what your provider publishes before you assume a fresh start.
What should I reconfigure first after moving?
Mailbox connections. Verify SMTP and IMAP, send a test message, then set volume below the provider cap. Sequences and reply handling come after the connection is proven.
Can I keep my existing mailboxes on a new platform?
Usually yes, if the platform accepts standard SMTP and IMAP settings. LocalSMTP at $149 provides five verified SMTP accounts with those settings on lifetime access, which keeps the mailbox layer independent of the sequence tool.
How do I work out which monthly plan fits?
Multiply mailboxes by daily sends, then by working days. Compare that to the published monthly allowance. Starter at $18/month covers 2,000 emails, Growth at $38/month covers 10,000.
Settle the Mailbox Layer, Then Rebuild Sequences
Start with a plan that matches your monthly volume, or take the lifetime SMTP route and keep infrastructure separate. Starter is $18/month and LocalSMTP is $149.
See the monthly plans