Migration

Move your transactional email infrastructure to ApexMail without disruption. This solution covers domain transition, IP warm-up, template migration, webhook compatibility, and parallel-send validation.

Audience

Engineering teams migrating from SendGrid, Postmark, Mailgun, Amazon SES, or Resend. Operations teams managing the cutover. Compliance teams verifying data residency requirements.

Business Context

Email provider migration is a high-risk operation. Dropped delivery during cutover means lost revenue. IP warm-up without automation risks blacklisting. Domain reputation must be preserved across providers. Without a structured migration plan, teams risk extended delivery degradation.

Core Problem

IP reputation is provider-specific and cannot be transferred.
Domain authentication records (SPF, DKIM, DMARC) require coordinated DNS changes.
Template syntax differs between providers.
Webhook payloads and event types are not standardized.
Parallel sending during validation requires dual-provider routing.

ApexMail Solution

Managed IP Warm-Up — Automated warm-up schedule for dedicated IPs, with throttling and reputation monitoring.
Domain Transition Guide — Step-by-step DNS configuration for SPF, DKIM, DMARC, and custom return-path.
Template Import — Map existing templates to ApexMail’s template format with variable and layout preservation.
Webhook Compatibility — Standardized event types with payload mapping documentation.
Parallel Send Validation — Route a configurable percentage of traffic through ApexMail while maintaining your existing provider.

Technical Implementation

Create an ApexMail account and verify your sending domain.
Configure DKIM with two selectors (am1, am2) alongside your existing provider’s selectors.
Add include:spf.apexmail.ee to your SPF record (do not remove existing provider’s SPF).
Set DMARC policy to p=none during transition to collect reports without enforcement.
Import templates using the Template API.
Configure webhook endpoints for event delivery.
Begin parallel sending at 10% volume, increasing incrementally while monitoring delivery metrics.
After validation period, route 100% through ApexMail and remove legacy provider configuration.

Relevant API Endpoints

Endpoint	Description
`POST /v1/emails`	Send an email
`POST /v1/emails/batch`	Batch send up to 1,000 emails
`POST /v1/templates`	Create a template
`GET /v1/templates`	List templates
`PUT /v1/templates/:id`	Update a template

Relevant Webhook Events

Event	Trigger
`email.delivered`	Receiving server accepted the message
`email.bounced`	Hard or soft bounce
`email.delayed`	Message deferred by receiving server

Required Plan

Plan	Dedicated IP	Support
Growth	1 managed dedicated IP (eligibility review)	8 business hours
Business	1 managed dedicated IP (eligibility review)	4 business hours
Enterprise	Up to 3 managed dedicated IPs	Negotiated

Security Considerations

DNS changes should be implemented during a maintenance window.
Monitor DMARC aggregate reports (RUA) throughout the transition period.
Keep both provider API keys active until full validation is complete.

Compliance Considerations

EU data residency applies upon cutover.
DPA execution required before migrating production data.
Customer retains responsibility for recipient consent continuity during migration.

Known Limitations

Parallel sending may result in duplicate delivery events during the validation window.
IP warm-up requires 2-4 weeks for dedicated IPs.
Template migration requires manual review for complex conditional logic.

Recommended Next Action

Contact sales for a migration assessment and dedicated IP eligibility review.