Migration guide
Amazon Pinpoint shuts down October 30, 2026. You don't have to leave AWS.
You chose Pinpoint because you wanted email marketing on AWS infrastructure you own. SendOps keeps you there: a full email marketing and analytics platform provisioned inside your AWS account via CloudFormation, sending through the same SES that delivered your Pinpoint email all along.
The 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, your endpoints, segments, campaigns, journeys, and analytics are gone. There is no grace period on the engagement features.
Unaffected
Amazon SES continues
SES — the service Pinpoint actually used to deliver your email — is not going anywhere. Your verified domains, sending reputation, and delivery pricing all stay exactly as they are.
AWS's recommended migration path for Pinpoint campaigns and journeys is Amazon Connect — a contact-center product built around agent queues and customer service conversations. If your Pinpoint workload is email marketing — segments, campaigns, drip journeys — that's a mismatch: you'd be adopting a call-center platform to send newsletters.
The better starting point is what survives: Amazon SES, the service Pinpoint used for delivery, continues unaffected. Your domains, reputation, and delivery pricing are already in place. What you need to replace is the marketing layer on top — and that layer can stay on AWS.
Concept mapping
Every Pinpoint concept has a home in SendOps
The model translates cleanly. Here's where each piece of your Pinpoint setup lands.
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
SendQL 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
SendFlow workflows
Notes
Drip workflows defined in a text DSL with a visual canvas — event, activity, and segment triggers, frequency caps, approval gates.
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
Six honest steps — no magic importer
There is no one-click Pinpoint importer, from us or anyone. What there is: a clean mapping, a fast contact import, and a workflow format designed to be rebuilt quickly. Here's the whole path.
- 1
Connect SendOps to the same AWS account
Run a CloudFormation template that provisions SendOps inside your AWS account — the same account Pinpoint has been sending from. It takes about two minutes, and SendOps never holds your AWS keys: access works through STS and a scoped IAM role you control.
- 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
Rebuild segments in SendQL
Pinpoint segments don't transfer automatically — you rewrite each one as a SendQL segment over your contacts' attributes, events, and activities. Most segments translate line for line.
- 4
Rebuild journeys in SendFlow
Journeys are rebuilt, not imported. SendFlow's text DSL makes this mostly transcription: each Pinpoint journey step maps to a workflow step you can write out and review. A coding agent can draft the SendFlow definitions from your journey descriptions, and the visual canvas lets you verify the result.
- 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
Pause Pinpoint journeys, activate the SendFlow equivalents, and point your event stream at the Activity API. Delivery keeps flowing through the same SES account throughout — recipients never see a seam.
Why stay on AWS
Why this beats moving to an off-AWS provider
Pinpoint shutting down doesn't mean the reasons you chose it stopped being true. You wanted email marketing that runs on infrastructure you own, delivers through SES, and doesn't meter your audience. Moving to a hosted email marketing SaaS gives all of that up. Staying on AWS with SendOps doesn't:
Same SES delivery: your verified domains, dedicated IPs, and sending reputation carry over untouched, because nothing about your sending path changes.
Same delivery pricing: SES bills you $0.10 per 1,000 emails, exactly as it did under Pinpoint.
No per-contact SaaS meter: SendOps plans are flat — Free at $0 with unlimited volume and no contact limits, Team at $29/mo, Business at $149/mo.
Your data stays in your AWS account: SendOps is provisioned inside it via CloudFormation and never holds your AWS keys.
No compliance re-review of a new delivery vendor: email still leaves from infrastructure you own.
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, endpoints, segments, campaigns, journeys, and analytics are no longer available.
Does Amazon SES shut down too?
No. SES is a separate service and is unaffected. Pinpoint used SES for email delivery, and SES continues as normal — your verified domains, sending reputation, and delivery pricing all remain in place.
Can I import my Pinpoint journeys automatically?
No — there is no automated journey importer, and we won't pretend otherwise. Journeys are rebuilt in SendFlow. The text DSL makes the rebuild mostly transcription rather than re-engineering, and a coding agent can draft the SendFlow definitions for you to review on the visual canvas.
What happens to my sending reputation?
Nothing. Pinpoint delivered email through SES, and SendOps sends through the same SES account. Your domains, IPs, and reputation history are untouched because the delivery layer never changes.
What does SendOps cost compared to Pinpoint?
Pinpoint billed per endpoint, per event, and per message on top of delivery. SendOps is flat: Free at $0 with unlimited volume and no contact limits, Team at $29/mo, Business at $149/mo — plus SES delivery at $0.10 per 1,000 emails, billed by AWS as before.
Why not migrate to Amazon Connect like AWS recommends?
Amazon Connect is AWS's recommended migration path for Pinpoint campaigns and journeys, but it's a contact-center product built around agent queues and customer service interactions. If what you run is email marketing — segments, broadcasts, drip workflows — it's a poor fit. SendOps is built for exactly that workload and keeps you on AWS.
October 30, 2026 is a hard deadline
The migration is easier now than it will be in October. Connect SendOps to your AWS account, import your contacts, and rebuild your journeys while Pinpoint is still there to check your work against.
Free plan available. Two-minute CloudFormation setup. Delivery stays in your SES account.