Before your first send from a new email platform, verify that mail sent through the new platform passes authentication, confirm whether you’ll use a shared or dedicated IP, and carry over your unsubscribe and suppression lists. Start with a small group of recently engaged, opted-in contacts. Review bounces, deferrals, complaints, and any available reputation data before increasing volume. If the migration gives you a new dedicated IP, build a gradual warm-up into the launch plan. Gmail’s email sender guidelines and Adobe’s Marketo Engage dedicated IP guidance explain the platform-specific considerations.
A migration can go smoothly in the project tracker and still leave your first campaign in trouble. The templates are in, the segments match, and everyone expects the launch to go out Tuesday. Then you find out the new platform is sending from a different IP or signing mail with a domain you didn’t expect. Make those checks while you still have room to change the launch plan.
Do you need to warm up your IP after a migration?
| What changed | How to plan the first sends |
|---|---|
| You’re moving to a new dedicated IP | Confirm the warm-up approach with your provider. Begin with a smaller, engaged audience and increase volume gradually as delivery signals allow. |
| You’re moving onto your provider’s shared IP pool | Ask how the provider handles the shared pool and any limits for new senders. Verify authentication and phase in your sending volume, especially if you’re also changing the sending domain or cadence. |
| You’re keeping the same sending domain | Check the IP setup and authentication on the new platform anyway. A familiar From address can sit on top of a different sending configuration. |
What should you check before the first send?
- Send a test message through the new platform. Check the headers to confirm SPF and DKIM results and DMARC alignment for the visible From domain. Verify the actual sending path as well as the DNS records.
- Reconcile your suppression lists. Confirm that unsubscribed contacts, prior hard bounces, and other suppressed addresses stay excluded. Test the unsubscribe flow from a message sent by the new platform.
- Agree on who goes first. Start with opted-in contacts who have engaged recently. Decide which send can move if the first segment needs more time before you add volume.
- Set a baseline and assign an owner. Record what bounces, deferrals, and complaints typically look like before migration. Assign someone to review the new platform’s reports and any available mailbox-provider data after each early send. See Gmail’s guidance on increasing sending volume.
When should you pause the ramp-up?
Hold the next increase if authentication fails, complaints rise meaningfully, or bounces or deferrals climb compared with your baseline. Look at the affected mailbox provider, error codes, and audience segment before deciding whether to adjust volume or fix a configuration issue. That distinction matters because sending more slowly can help with throttling, while an authentication failure needs a configuration fix. See Gmail’s guidance on sender issues and server responses.
How Revenue Pulse planned sending continuity during a Marketo consolidation
After an acquisition, Revenue Pulse (RP) helped move 300,000 people and more than 150 programs into one Marketo instance. The two teams shared some audiences, so the migration had to account for overlapping records, communication limits, and how to reconcile subscriptions and unsubscribes.
RP planned the overlap between the two Marketo instances and included IP warming in the migration plan. The team also tied the migration schedule to key campaigns and events while the Salesforce consolidation followed a separate timeline.
The operating decision was to plan sending continuity before retiring the old instance. If your teams share subscribers, agree on who can send to each audience and how opt-outs will be carried over before both teams start sending from the consolidated setup.
Get a second set of eyes before cutover
If you have a migration date and are unsure what’s safe to send on day one, Revenue Pulse can review your sending setup, identify what to fix before cutover, and help you sequence the first sends. Talk to Revenue Pulse about a deliverability audit.
For troubleshooting beyond migrations, see Email Deliverability and IP Warming Best Practices.