AWS ends Amazon Pinpoint support on October 30, 2026. The console and engagement resources will become inaccessible. This is not the retirement of Amazon SES or every messaging API. Identify the features your team uses, export the records you need, and choose a replacement for each workload before cutover.

Updated September 16, 2026.

What ends, and what continues

According to AWS’s end-of-support notice, Pinpoint stopped accepting new customers on May 20, 2025. After October 30, 2026, customers cannot access its console or resources: endpoints, segments, campaigns, journeys and analytics. AWS recommends Amazon Connect engagement solutions for applicable engagement workloads, Kinesis for event collection and mobile analytics, and Amazon SES for email.

AWS says the communication channels were renamed AWS End User Messaging in 2024. APIs for SMS, voice, mobile push, OTP and phone-number validation are not affected by this retirement. Continuing delivery APIs do not preserve the Pinpoint journeys or audiences that invoke them. Map those dependencies separately.

Set a cutover plan, not a last-day deadline

October 30 is the AWS deadline, not a sensible date to begin testing. Assign a marketing owner and a technical owner now. Agree a cutover date with enough room to reconcile data, repair missing events and pause a rollout if essential checks fail. The time required depends on workload complexity; a universal “minutes” or “weeks” estimate would be misleading.

• Inventory every project and Region, endpoint attribute, segment rule, campaign, journey, template and upstream event source. Include transactional paths that marketing may not own.
• Record what each workflow sends, why a recipient qualifies, how they leave it, and where unsubscribe, bounce and complaint decisions are stored.
• Export records before access ends. Restrict export access and set retention requirements with your security team. An endpoint export is not a runnable copy of your automation.
• Allocate a replacement and an accountable operator to each capability. Agree who maintains preferences and prevents duplicate sends during the transition.

Choose a destination by the work you need to preserve

Retaining Amazon SES can preserve an existing sending setup where AWS supports that path, but it does not guarantee unchanged inbox placement. Verify the account, Region, identities, configuration sets and IP arrangements. Use the Pinpoint-to-SES technical guide for the implementation checks.

For marketer-owned audiences and journeys, compare Pinpoint replacements. An AWS-native architecture and a managed platform have different operating responsibilities. Evaluate both against a real workflow, not a generic feature grid. Our Mailchimp alternatives guide is a separate email-platform shortlist, not proof of Pinpoint migration compatibility.

CampaignHQ is a customer retention automation platform for email and WhatsApp, and a Meta Tech Partner. AWS supports its infrastructure. For teams retaining SES, assess CampaignHQ as the marketing workflow layer. Confirm data mapping, event integrations, security requirements and support responsibilities during discovery. Agree the migration scope, channel support, timetable and cutover responsibilities before committing.

Checks that must pass before switching traffic

• Reconcile the exported endpoint count and important attributes against the source. Account for duplicate contacts and distinct endpoints; do not merge them merely because addresses look similar.
• Demonstrate that unsubscribed, bounced and complained addresses receive the intended treatment in the destination. Address validity is not marketing permission.
• Check template substitutions, links, event triggers, delay rules and exits using an approved test plan. Do not send duplicate production messages from both platforms.
• Record a rollback owner, stop conditions, monitoring and final sign-off. Keep necessary exports after cutover according to the agreed retention policy.

SES has an account-level suppression list. It is not a substitute for all your marketing consent and preference records. Carry those records into the workflow that will make send decisions.

Use the retention platform migration checklist to coordinate consent, workflow ownership, pilot acceptance and handover across email and WhatsApp.

Keep commercial assumptions separate from migration facts

Review SES pricing, AWS email service costs and historical Pinpoint pricing as budgeting inputs, not a guarantee of migration savings. An AI subject-line tool does not remove template QA or establish migration readiness.

For background, see our Amazon Pinpoint overview. KumoHQ is the team behind CampaignHQ.

Frequently asked questions

Can existing customers keep using Pinpoint until the deadline?

AWS says existing customers signed up before May 20, 2025 can continue to use Pinpoint features before end of support. Plan your transition earlier rather than relying on last-day access.

Does this shut down SES?

No. AWS recommends SES as the destination for Pinpoint email sending. Check the existing account and Region before changing resources.

Will my SMS and push APIs stop working?

The AWS notice says the relevant messaging APIs continue under AWS End User Messaging. Pinpoint campaign and journey dependencies still need replacement.

Is an endpoint export enough?

No. It captures endpoint records, not a working replacement for segments, journeys, templates, events and reporting. Inventory and validate those separately.

How should we plan for migration downtime?

Agree the supported scope, test plan, cutover conditions and rollback responsibilities with the migration team. Set an acceptable interruption window and decide what would trigger a rollback.

Check AWS’s complete offboarding guidance before approving the final migration design.

Written by CampaignHQ Team