Amazon Pinpoint migration
Replace Pinpoint. Keep your email on AWS.
Amazon Pinpoint ends support October 30, 2026.
Bring your email campaigns and journeys to SendOps. Build welcome, onboarding, and win-back workflows, manage your audience, and send through your own Amazon SES. No per-contact charges as you grow.
Free plan available. No credit card required. Your own AWS account.
Your next email journey
Welcome them. Help them activate. Bring them back.
Turn customer activity into relevant follow-ups. Explore a journey, open an email step, and see how your team can build the next campaign visually or in code.
Journey explorer
Select any step
Meet them at their first milestone.
Wait for a first project, not just the clock. Celebrate progress, or offer help when the deadline passes. Finish with the right contact context.
Behavioral wait · Timeout path · Contact updates
Exit if the account closesChecked throughout the journey.
Project created
2 days, no project
The project-created signal comes from your app. A timed wait resumes when the condition is met or its deadline expires.
Welcome them aboard
A personalized template sent through your Amazon SES. Marketing topic preferences and your email frequency cap are checked before sending.
Your first small win starts here
lily@yourcompany.com
to Marcus
Hi, Marcus. Let’s get your first project up and running. Start with one thing, and we’ll help with the rest.
Create your first projectThe timeline
What's ending, when — and what survives
May 20, 2025
Pinpoint closed to new customers
Amazon Pinpoint stopped accepting new customers. Existing customers can keep using it, but the product is in wind-down.
October 30, 2026
End of support
AWS ends support for Amazon Pinpoint. After this date, its console, endpoints, segments, campaigns, journeys, and analytics will no longer be accessible.
Unaffected
Amazon SES continues
Amazon SES is unaffected by the Pinpoint shutdown. Keep email delivery in your AWS account while you move your campaigns and journeys to SendOps.
The deadline affects Pinpoint engagement features. SMS, voice, and mobile push APIs continue under AWS End User Messaging. This guide focuses on moving your email campaigns and journeys to SendOps.
Read AWS’s shutdown guidanceConcept mapping
From Pinpoint campaigns to SendOps workflows
Familiar building blocks for your next campaign. Here’s how the email capabilities you use in Pinpoint map to SendOps.
Amazon Pinpoint
SendOps
Notes
Amazon Pinpoint
Endpoints & user attributes
SendOps
Contacts with typed attributes
Notes
Import via CSV or API. Attributes carry over as typed fields on each contact.
Amazon Pinpoint
Segments
SendOps
Audience segments
Notes
Dynamic segments queried over attributes, events, and activities — re-evaluated at send time.
Amazon Pinpoint
Campaigns
SendOps
Broadcasts
Notes
One-off sends with consent filtering, test sends, and per-broadcast results.
Amazon Pinpoint
Journeys
SendOps
Email workflows
Notes
Build journeys visually or in code, with activity triggers, timed follow-ups, conditions, and frequency caps.
Amazon Pinpoint
Events
SendOps
Activity API
Notes
Send user events to SendOps and use them in segments and workflow triggers.
Amazon Pinpoint
Analytics
SendOps
Deliverability & campaign analytics
Notes
Delivery, bounce, complaint, and engagement metrics per broadcast and workflow.
The migration path
Your path from Pinpoint to SendOps
Start with one important journey. Bring over your contacts, recreate the flow, and test it before switching. Then work through the rest of your campaigns with a clear plan.
- 1
Connect your AWS account
Connect SendOps securely to your AWS account. Set up the SES identities and sending configuration you will use for your campaigns.
- 2
Export your endpoints, import your contacts
Export endpoint data from Pinpoint, then import it into SendOps as contacts via CSV or the API. Pinpoint user attributes become typed attributes on each contact.
- 3
Recreate your audiences
Use contact attributes and product activity to recreate your targeting in SendOps. Check each audience against your existing Pinpoint segments.
- 4
Build your journeys in SendOps
Start with your most important welcome, onboarding, or win-back journey. Recreate its emails, timing, and conditions on the visual canvas or in code, then review the full flow with your team.
- 5
Validate with test sends
Use test sends on each broadcast and workflow to confirm content, segment membership, and timing before anything goes to real contacts.
- 6
Cut over before October 30, 2026
Coordinate the switch for each journey: pause its Pinpoint version, connect the relevant events to SendOps, and activate the tested workflow. Monitor the first sends and avoid enrolling contacts twice.
Why stay on AWS
Keep the infrastructure. Upgrade the everyday work.
Move to a platform built for the people running your email. Give marketers visual tools, developers code and APIs, and the whole team a shared view of results. Your sending stays in AWS.
Your own SES delivery: send from your AWS account and your domains, with control over your email infrastructure.
Direct AWS billing: pay AWS for SES delivery, with no SendOps markup on each email.
No per-contact charges: grow your audience without growing a contact-based subscription. Start with the Free plan.
Your sending stays in your AWS account: SendOps connects to it via CloudFormation and never holds your AWS keys. Contacts and campaign history are stored in SendOps, scoped to your workspace and exportable.
One place for your team: manage audiences, broadcasts, workflows, templates, and reporting together.
Domain-wide DMARC monitoring: identify every service sending as your domain, diagnose alignment failures, and measure policy readiness alongside your SES delivery data.
Coding-agent operation: move from campaign state trapped in a vendor UI to readable definitions and native tools. Agents can draft SendQL audiences, workflows, and templates, then use scoped MCP access for permitted live operations.
Common questions
When exactly does Amazon Pinpoint shut down?
Amazon Pinpoint stopped accepting new customers on May 20, 2025. AWS ends support on October 30, 2026. After that date, the Pinpoint console, endpoints, segments, campaigns, journeys, and analytics will no longer be accessible.
Does Amazon SES shut down too?
No. Amazon SES is unaffected by the Pinpoint shutdown. SendOps connects to your AWS account so you can run email campaigns and workflows with SES handling delivery.
Are SMS and push messaging shutting down?
The SMS, voice, mobile push, OTP, and phone number validation APIs continue under AWS End User Messaging. This migration guide focuses on Pinpoint email campaigns and journeys.
Can I import my Pinpoint journeys automatically?
SendOps does not currently import Pinpoint journey definitions automatically. Recreate your journeys on the visual canvas or in code, then test their emails, timing, and conditions before switching. Contacts can be imported via CSV or API.
What happens to my sending reputation?
SendOps uses your own Amazon SES account for delivery. Review your sending identities and configuration as part of the move, and monitor delivery, bounces, and complaints during testing and cutover. Reputation depends on your sending practices as well as your infrastructure.
What does SendOps cost compared to Pinpoint?
SendOps has a Free plan and paid plans for teams, with no per-contact charges. AWS bills separately for SES delivery and any other AWS resources you use. See our pricing page for current plans.
Why choose SendOps instead of Amazon Connect?
AWS recommends Amazon Connect for migrating Pinpoint engagement capabilities. SendOps is an alternative for teams focused on email campaigns and lifecycle workflows on their own SES account, with visual editing, code-based workflows, and no per-contact charges.
October 30, 2026 is a hard deadline
Give your team time to test before the deadline. Connect your AWS account, bring over your contacts, and build your first SendOps workflow while you can still refer to your Pinpoint setup.
Free plan available. No credit card required. Send through your own SES.