Your SaaS may have sent 2,000 password resets and receipts a day through its old ESP; a large campaign on the new provider is a different traffic pattern, even when the From domain stays put. That distinction determines whether you need to warm up domain after migration—or verify the new sending path and ramp changed traffic carefully.
A provider-only change does not erase the domain’s sending history, so you do not automatically need to restart domain warm-up. A new domain or IP, or a sharp shift in volume or recipient mix, calls for a deliberate ramp. Domain and IP reputation are separate; use prior delivery results to set the pace.
This guide gives you a migration-specific decision path, preflight checks for SPF, DKIM, and DMARC, and a staged plan for transactional email and campaigns. It also covers what changes when you move to Volanea, which sends on shared Amazon SES infrastructure, and includes an example ramp table.
Do you need to warm up your domain after an email migration?
Usually, no: if you keep the same sending domain and move only to a new email service provider, you do not automatically need to treat the domain as new. The answer changes if you also switch the domain, introduce a new sending IP, or sharply change your volume or recipient mix. Those are separate changes with different reputation effects; domain reputation and IP reputation are related, but one does not guarantee the other.
For a provider-only move, the domain’s sending history does not disappear just because the underlying service changes. But the receiving providers will see a new sending path, and authentication or configuration differences can affect how the new mail is evaluated. So “warm up domain after migration” is not a universal instruction: first identify what actually changed in your email service migration.
A new domain has little or no established sending history, so it needs a cautious introduction. A new IP has its own reputation to establish, even if the domain is familiar. Amazon SES says new accounts send by default from IP addresses shared with other SES users; AWS manages traffic on those shared IPs, which suit sending patterns that are not predictable. SES also offers dedicated IPs, whose warm-up requirements are about the IP—not a reset of the domain’s history. AWS explains the distinction between shared and dedicated IP sending.
A major change in sending pattern can also justify a more careful transition. For example, a SaaS team that previously sent 2,000 password resets and receipts each day should not assume that launching a large campaign on the new provider is equivalent to moving those transactional messages. The domain may be unchanged, but message volume, recipient engagement, and traffic type have shifted.
The practical answer is to avoid restarting at zero solely because you changed providers, but don’t assume the old setup’s history makes every new configuration safe at full volume. Keep the domain and sending pattern stable where possible, and treat a new domain or IP as a distinct reputation change. The sections below separate those cases and explain how to make the cutover based on the specific change—not a generic warm-up calendar.
What changed in the migration—and what reputation follows it?
Treat the migration as a change to one or more separate pieces of the sending identity: the domain, the IP address, the provider’s sending account, or the volume and type of mail. Keeping the same domain does not mean every part of your sending history moves with you. Likewise, changing providers alone does not automatically mean you have a new domain to establish.
| Migration change | What may carry over | What needs to be established or checked anew |
|---|---|---|
| Same domain, new ESP | The domain’s existing history with mailbox providers can remain relevant when you continue using that domain. | The new provider’s sending IPs and account history are different; assess the sending path and confirm the new provider can send as your domain. |
| Same ESP, new IP | The domain and provider account stay the same. | The new IP has its own sending history to establish. Amazon SES describes IP reputation as based largely on historical sending patterns and volume. |
| New sending domain | Your existing domain’s history does not automatically belong to the replacement domain. | The new domain must build its own history with the mail you send from it. |
| Changed sending pattern | The domain may be unchanged. | A substantial shift in volume or message mix changes the pattern mailbox providers observe, so assess it separately from a provider-only move. |
Domain reputation and IP reputation are related signals, not interchangeable records. Amazon SES specifically describes IP reputation in terms of sending patterns and volume; it does not publish a rule that domain reputation transfers to a new IP or account. In practice, keep the established domain where possible, but treat a new IP or a major traffic shift as a distinct change rather than assuming the old setup’s history covers it.
The provider’s own account-level records are also not the same thing as the domain’s history at mailbox providers. Exportable engagement and suppression data can help you preserve useful operational context, but that does not make the new provider’s IP or account identical to the old one. The broader email service migration involves moving those operational pieces as well as changing the sending route.
For an Amazon SES move, identify whether the new setup sends through SES shared IPs or a dedicated IP. AWS says new SES accounts use shared IPs by default, while dedicated IPs are a separate sending path with their own warm-up considerations. That distinction matters even when the visible sender domain stays the same: the domain may retain relevant history, while the new IP still needs a sending history of its own. The next step is to pin down exactly which of these variables changed before deciding how to ramp.
Check these items before sending from the new setup
Before increasing volume, confirm the new sending path can authenticate messages, identify failures, and avoid retrying addresses that should no longer receive mail. Treat this as a preflight for the sending configuration—not as a warm-up schedule.
- SPF: Update the existing SPF TXT record to authorize the new provider while keeping the old provider valid during the transition, as RFC 7208 recommends. Publish one SPF record per owner name; multiple records cause
permerror. Also check the record’s DNS-lookup terms: SPF evaluation is limited to 10 terms that cause DNS queries, includinginclude,a, andmx. - DKIM: Publish the new provider’s public key at the selector and signing domain it specifies. Send a test and confirm that the signature verifies. A valid DKIM signature is not enough by itself: check that its
d=signing domain aligns with the visibleFromdomain under your DMARC policy. - DMARC alignment: Verify that either the SPF-authenticated
MAIL FROMdomain or a valid DKIM signing domain aligns with the visibleFromdomain. One aligned mechanism can pass DMARC. Review aggregate reports for the new sending path; they show authentication results, sending IPs, message counts, and receiver dispositions. - DNS propagation: Query the relevant TXT records from more than one resolver before cutover. A record visible in your DNS dashboard is not proof that every recipient system is seeing the updated value. Send another test after the records resolve.
- Bounce handling and suppressions: Confirm that hard bounces and complaints are captured and that unsubscribed, bounced, or otherwise suppressed addresses are excluded from sends. Carry forward suppression data from the previous provider; do not assume the new account has it. Volanea’s sending pipeline checks suppressions as part of processing a send, but you still need to bring the correct suppression data into the new setup.
- Sending identity and baseline: Check the visible
Fromaddress, reply-to address, return-path behavior, and the message types using each identity. Record recent bounce rate, complaint rate, deferrals, and inbox placement from the old provider so you have a comparison point for the new path.
Send sample messages to test inboxes at several mailbox providers before ramping. Inspect the received message headers for SPF, DKIM, and DMARC results—not just whether the message arrived. Our email provider migration checklist covers the wider email service migration alongside mailbox and app-email changes; for Volanea sends, the API and sending pipeline handles suppression checks, contact upserts, template rendering, tracking, and delivery.
Build a migration warm-up plan from your previous sending history
Start with your sending history, not a generic calendar. For a warm up domain after migration plan, compare the new setup with the volume you sent before, who received those messages, and how recipients responded. Amazon SES recommends sending to your most active users when warming a dedicated IP; that is a useful starting point for a migration ramp, but SES does not publish a numeric warm-up schedule for migrated domains.
Use a recent, representative period of sending history to set your baseline. Separate routine daily volume from occasional spikes, and distinguish messages recipients expect from mail they rarely engage with. Then ramp in stages:
- Start with an expected, engaged audience. Send the first batch to recipients who recently opened, clicked, or otherwise acted on your mail. Keep the batch to a modest share of your normal volume, rather than sending the full list immediately.
- Compare with your baseline. Check the new provider’s results against the same type of mail and audience from your previous setup. Look at whether delivery, bounces, complaints, and deferrals are broadly consistent with your established pattern.
- Expand in controlled steps. If results remain healthy, add more of your usual audience or increase the next send. Change one major volume step at a time so you can connect any deterioration to a specific send.
- Reassess before each increase. If a stage produces more delivery problems or weaker engagement than your baseline, hold at that level rather than increasing automatically. Resume with a smaller audience or volume after investigating.
For example, if your normal campaign reaches 5,000 recipients, do not treat 5,000 as the required first send after cutover. Begin with a smaller, recently engaged portion of that audience, review its results, and expand only when those results support it. The example is a way to apply your own history—not a universal percentage or a fixed day-by-day schedule.
Keep the ramp tied to the actual change. A move to another ESP with the same domain and a comparable sending pattern gives you a useful historical baseline; a new domain or a sharp increase in volume offers less certainty, so take smaller steps. If you are also moving mailbox hosting, use the email provider migration checklist to keep that work distinct from your application’s sending ramp.
If you are moving to Volanea: no IP to warm, ramp the domain
Volanea sends from shared Amazon SES infrastructure and does not offer dedicated IPs, so there is no IP of your own to warm. What you ramp is your domain's traffic on the new sending path. Volanea's reputation guard also steps in on risky sending (it warns, then throttles, then pauses) before a bad list can hurt your domain.
Before any real send, run the whole flow with a project key that starts with sk_test_. Test-key sends render and log exactly like real ones but are never delivered, so you can check templates, variables, and events without touching your reputation.
Here is an example ramp for a 5,000-recipient campaign on the same domain you used with your old ESP. Treat it as a starting point and adjust it to your own history:
| Day | Who to send to | Volume |
|---|---|---|
| Day 1 | Contacts who opened or clicked in the last 30 days | 500 |
| Day 2 | Recently engaged contacts | 1,000 |
| Day 3 | Engaged contacts plus your regular audience | 2,000 |
| Day 4–5 | Full list | 5,000 |
Hold at the current step if hard bounces go above about 2% or spam complaints go above 0.1% (Google asks bulk senders to stay below 0.1% and never reach 0.3%). Fix the cause, then resume with a smaller step. Transactional email such as password resets and receipts can run at its normal volume from day one, because those messages follow user actions and your recipients expect them.
If you are moving to raw Amazon SES instead, check whether you will use SES shared IPs or a dedicated IP. A dedicated IP needs its own warm-up, which AWS handles for Standard and Managed dedicated IPs (AWS dedicated IP warm-up guidance). That IP warm-up is separate from your domain's history.
Migrate transactional email and campaigns differently
A migration affects different kinds of email in different ways. Keep essential transactional messages reliable through the cutover, and avoid pairing that change with an unusually large campaign. If both streams shift at once, a delivery problem is harder to trace: you may not know whether it comes from the new sending setup, campaign engagement, or the volume spike.
Transactional email is tied to actions a person just took: password resets, receipts, account verification, and service alerts. These messages are time-sensitive, so plan the sending-path change around them first. For example, test a password reset and receipt through the new provider before routing production traffic there, then confirm that the application still sends the expected messages after cutover. Keep the old route available during the transition if your setup supports it, so a problem with the new route does not leave users without critical messages.
Campaigns have different stakes. A promotional message can usually wait; a sudden high-volume send to a broad or less-engaged audience adds a second variable just as the new provider is handling your mail. Low opens, bounces, or complaints from that send can muddy the evidence you need to judge the migration and may weaken engagement signals. Move campaigns deliberately: start with the audience most likely to recognize and want the message, and postpone a large send until the new path has handled routine traffic predictably.
Use separate operational checks for each stream:
- Transactional: exercise the application’s critical email flows on the new route, including the messages users need to access or continue using the service. Check that retries or provider errors do not silently drop those messages.
- Campaigns: keep the first sends narrow and relevant. Avoid combining the provider cutover with a major list expansion, a new campaign format, or a sudden increase in frequency.
- Shared infrastructure: if both streams use the same sending identity, treat a campaign spike as a change to the overall traffic profile—not as an isolated marketing decision. Separate streams where your provider and configuration allow it, so you can identify which traffic is responsible for a change in results.
This distinction matters whether you are moving to Amazon SES or another ESP. Volanea combines transactional email, campaigns, and automations on one API, but a unified sending interface does not make a password reset and a bulk campaign interchangeable. Keep critical user-triggered mail steady while campaign volume remains controlled; then expand campaigns as their own results support it.
Monitor delivery and know when to pause or slow down
Treat the first sends from the new setup as a monitored change, not a pass-or-fail test. Compare results with your pre-migration baseline by recipient provider and message type: a rise in Gmail bounces can be hidden by healthy delivery to other providers, while campaign complaints can be obscured by transactional volume. Record the volume sent alongside each signal so you can tell whether a change followed a volume increase or a configuration change.
Track these signals after each send:
- Bounces: Separate permanent failures from temporary ones. A sudden increase in hard bounces can indicate stale or invalid addresses; repeated temporary failures may point to throttling or blocking.
- Spam complaints: Watch complaint counts and rates by provider where available. If complaints rise after a campaign, hold further campaign volume while you review the audience and message.
- Deferrals: Look for repeated temporary rejections or rate limiting in SMTP responses. A growing pattern at one provider is a reason not to increase volume to that provider yet.
- Inbox placement: Use seed tests or mailbox-provider reporting where available, and compare inbox, spam, and missing-message results over time. A successful SMTP acceptance alone does not show where a message landed.
- Provider feedback: Review bounce details, postmaster dashboards, and feedback-loop data where the provider makes them available. Amazon SES recommends examining bounce messages and sending less when providers are blocking or throttling mail during dedicated-IP warm-up; its guidance says IP warm-up can take around two weeks for some providers and up to six weeks for others. Those figures describe IP warm-up, not a fixed schedule for a migrated domain. (Amazon SES guidance)
If a signal deteriorates, stop increasing volume to the affected provider or segment. Investigate the SMTP response and bounce categories first, then check whether authentication is passing and aligned, whether the recipient segment contains invalid or unengaged addresses, and whether a content or tracking change coincided with the decline. Keep unaffected traffic separate where possible so you do not mistake a provider-specific problem for a system-wide one.
Resume with a smaller increase only after the cause is addressed and the next monitored send is stable. Volanea provides send records, delivery, open, click, bounce, and unsubscribe statistics, plus event logs, which can help teams compare individual sends with the signals they are watching.
Common migration warm-up mistakes
The most costly mistakes after a mail-provider migration come from treating every change as the same kind of warm-up. A new ESP, a new sending IP, a new domain, and a sudden shift in traffic affect different parts of your sending history. A plan based only on the word “migration” can push too much mail through a path that has no established record—or slow normal sending without a clear reason.
- Sending full volume immediately because the domain is familiar. A domain’s prior sending history does not establish the history of a new IP address. Amazon SES says IP reputation depends largely on historical sending patterns and volume; it automatically warms Standard dedicated IPs by increasing their share of traffic over 45 days. Keep the reputation signals separate when deciding whether a cutover is ready for full volume.
- Changing too many variables at once. Moving providers while also changing the From domain, message format, audience mix, and daily volume makes a delivery change difficult to diagnose. Hold the other variables steady where possible, then compare the new provider’s results with your previous baseline. If you must change several things, record which changed and when so a bounce or filtering shift has a traceable cause.
- Assuming domain reputation guarantees IP reputation. The domain and IP are not interchangeable identifiers. A move to Amazon SES may use shared IPs by default, while dedicated IPs have their own warm-up process. Amazon SES says the time to establish positive reputation on a Standard dedicated IP varies by receiving provider: around two weeks for some and up to six weeks for others. Those figures describe IP warm-up—not a universal schedule for a migrated domain.
- Copying cold-email warm-up schedules for permission-based mail. Cold-outbound advice often assumes a sender is starting from no meaningful engagement history and must manufacture a gradual increase in replies. That is not a sound default for established transactional mail or opted-in campaigns. Use your own prior sending history and recipient engagement to shape the transition; a new domain or IP may need a ramp, but that does not make every legitimate message a cold prospecting email.
A practical migration review should ask which specific element changed, then match the response to that change. Amazon SES’s dedicated-IP guidance is explicit about warming new IPs; it does not publish a numeric warm-up schedule for a migrated sending domain. Treating those as separate questions avoids both unnecessary delays and an abrupt traffic spike on a new sending path.
FAQ
Can I keep my old ESP active during the cutover?
Yes, if your setup supports parallel routing. Keeping the old route available can protect essential transactional messages while you test the new route. Keep the old provider authorized in SPF during the transition, and remove that authorization only after legitimate mail can reasonably be expected to have been checked through the old path. Test messages and DNS records before increasing volume.
Does a recently purchased sending domain need a slower first send?
Yes. A new sending domain has little or no established history, so don’t assume the reputation of a previous domain carries over. Authenticate the new domain, test sample messages, then begin with expected, engaged recipients at a modest share of normal volume. Increase only when delivery signals remain healthy; there is no single ramp that fits every sender.
Does successful SMTP acceptance confirm inbox placement?
No. SMTP acceptance alone does not show whether a message landed in the inbox or spam folder. Use seed tests or mailbox-provider reporting where available, and compare results over time. Track bounces, complaints, and deferrals by recipient provider before deciding whether to increase volume.
If you’re evaluating a new sending setup, start free with 1,000 emails a month.