Amazon Pinpoint migration
Move your Amazon Pinpoint email templates to Amazon SES.
Last updated 2 November 2026
Amazon Pinpoint support ended on October 30, 2026, and AWS recommends Amazon SES for email. Here’s how to get your email templates out of Pinpoint and into SES, with a visual editor for the part that usually hurts.
Try it with one template
Upload your exported Pinpoint templates in bulk, preview them with sample data, and publish them to SES.
Open the editorWhat changed
AWS ended support for Amazon Pinpoint on October 30, 2026. This is Pinpoint’s end of life. The service had been deprecated since May 20, 2025, when it stopped accepting new customers. The Pinpoint console and Pinpoint resources (endpoints, segments, campaigns, journeys, and analytics) are no longer available.
AWS’s guidance splits by what you use Pinpoint for:
- Email: migrate to Amazon SES. Pinpoint’s deliverability dashboard is replaced by SES Virtual Deliverability Manager.
- Campaigns, journeys, segments: Amazon Connect outbound campaigns and Customer Profiles.
- SMS, voice, push, OTP: these APIs continue under AWS End User Messaging.
Export your templates now. The console is gone, but AWS still lists the email template APIs as supported, without saying for how long. Use the AWS CLI steps below.
Source: Amazon Pinpoint end of support (AWS documentation). Still choosing where email goes next? See Amazon Pinpoint alternatives for email.
Short on time? Our services team can move your email templates for you, starting the next day. Quoted per project from $500. See the migration service.
What carries over to SES
The good news for email: Pinpoint message templates and SES stored templates both render with Handlebars. Your HTML, {{#if}} conditions, and {{#each}} loops carry over. SES also supports nested attribute paths and inline partials (SES advanced personalization).
Three things change:
- Placeholder data. Pinpoint filled placeholders like
{{User.UserAttributes.FirstName}}from its own endpoint records. SES fills them from theTemplateDataJSON your code sends. - Template fields. Pinpoint uses
Subject,HtmlPart, andTextPart. SES v2 usesTemplateContentwithSubject,Html, andText. - Who sends. Pinpoint campaigns and journeys sent for you. With SES, your application calls
SendEmailorSendBulkEmailwith a template name.
Export your Pinpoint templates
Use the AWS CLI with credentials for the account and Region your Pinpoint project lives in:
# List every email template in the account and Region
aws pinpoint list-templates --template-type EMAIL
# Save one template's HTML body to a file
aws pinpoint get-email-template \
--template-name welcome \
--query 'EmailTemplateResponse.HtmlPart' \
--output text > welcome.html
# Keep the full response too: Subject, TextPart, and DefaultSubstitutions
aws pinpoint get-email-template --template-name welcome > welcome.jsonRepeat for each template, or script it over the list-templates output. Keep the full JSON: DefaultSubstitutions holds the default values Pinpoint used for placeholders, which make good sample data later.
If you’d rather automate the conversion, AWS publishes a sample Pinpoint to SES v2 template migrator that rewrites placeholders and template fields. Run it first, then connect that AWS account to Huskar Templates, which copies the converted templates in once, to preview them with sample data, fix what the script couldn’t, and maintain them from then on.
Map Pinpoint placeholders
You have two options. Pick one convention and use it across all your templates.
| Pinpoint placeholder | Keep the path in SES | Or flatten it |
|---|---|---|
{{User.UserAttributes.FirstName}} | {{User.UserAttributes.FirstName}} | {{firstName}} |
{{Attributes.PlanName}} | {{Attributes.PlanName}} | {{planName}} |
{{User.UserId}} | {{User.UserId}} | {{userId}} |
- Keep the path if you want the smallest template diff. Your sending code then builds
TemplateDatawith the same nesting, for example{"User":{"UserAttributes":{"FirstName":"Ada"}}}. - Flatten if you’re rewriting the sending code anyway. Short names are easier to read in the editor and in
TemplateData.
Pinpoint stored endpoint attributes as lists of values. In SES you pass TemplateData yourself, so send plain values, or arrays only where the template loops over them with {{#each}}.
Import, fix, and preview
This is where most migrations stall: raw HTML with dozens of placeholders, no way to see what it looks like with real data, and a JSON file to hand-edit. In Huskar Templates:
- Open the editor and upload the HTML files you exported, one at a time or all at once. Uploaded HTML becomes a code template with a live preview. Already deployed them to SES? Connect that AWS account and they are copied in once, as code templates.
- Rename placeholders to your chosen convention.
- Add a sample data profile using the values from
DefaultSubstitutions, then preview in Gmail, Apple Mail, and Outlook frames on desktop and mobile. - Want blocks instead of raw HTML? Start from a starter and rebuild the email visually, keeping conditions and loops as real Handlebars.
Publish to Amazon SES
Two ways to get the template into SES:
- Publish from Huskar Templates. Sign in, connect your AWS account through an IAM role you create with our CloudFormation template, and publish. Publish creates or updates the SES template. See how connecting works and the security model.
- Export and deploy yourself. Export SES template JSON (this works as a guest too) and create the template with the AWS CLI:
{
"TemplateName": "welcome",
"TemplateContent": {
"Subject": "Welcome aboard, {{firstName}}",
"Html": "<h1>Welcome aboard, {{firstName}}</h1> ...",
"Text": "Welcome aboard, {{firstName}} ..."
}
}aws sesv2 create-email-template --cli-input-json file://welcome-ses.jsonUpdate your sending code
Where Pinpoint campaigns or SendMessages calls used to send, call SES with the template name and the data for its placeholders:
{
"FromEmailAddress": "Northwind <hello@northwind.example>",
"Destination": { "ToAddresses": ["ada@example.com"] },
"Content": {
"Template": {
"TemplateName": "welcome",
"TemplateData": "{ \"firstName\": \"Ada\", \"planName\": \"Team\" }"
}
},
"ConfigurationSetName": "transactional"
}aws sesv2 send-email --cli-input-json file://send.jsonAWS recommends a configuration set that publishes Rendering Failure events to Amazon SNS: SES can accept a message whose template data doesn’t render and then fail to deliver it, and those events tell you which one (SES templates guide). Note that SES doesn’t HTML-escape values when rendering the HTML part, so escape user-entered data before sending.
Migration checklist
- List every Pinpoint email template and export it, including
DefaultSubstitutions. - Choose a placeholder convention: keep Pinpoint paths or flatten.
- Check each template is under SES’s 500 KB limit (HTML and text combined). SES allows up to 20,000 stored templates per Region.
- Verify your sending domain and identities in SES, and request production access if the account is still in the SES sandbox.
- Set up a configuration set for click and open tracking and Rendering Failure events.
- Preview every template with realistic data, including empty and missing values.
- Publish the templates to SES and switch your sending code to
SendEmailorSendBulkEmail. - Send test messages to Gmail, Apple Mail, and Outlook before cutting over.
FAQ
When did Amazon Pinpoint support end?
AWS ended support for Amazon Pinpoint on October 30, 2026. Since then you can no longer access the Pinpoint console or Pinpoint resources such as endpoints, segments, campaigns, journeys, and analytics. Pinpoint stopped accepting new customers on May 20, 2025.
What happened to my Pinpoint email templates after October 30, 2026?
The Pinpoint console is gone, but AWS’s end-of-support page still lists the email template APIs as supported, without saying for how long. Use the AWS CLI to export the subject, HTML, text, and default substitutions for every email template now, then recreate them as Amazon SES templates.
What does AWS recommend for email after Pinpoint?
If you use Amazon Pinpoint to send email, AWS recommends migrating to Amazon Simple Email Service (SES). Engagement features such as campaigns and journeys map to Amazon Connect outbound campaigns, and SMS, voice, and push continue under AWS End User Messaging.
Do Amazon Pinpoint email templates work in Amazon SES?
Mostly. Both use Handlebars, so conditions, loops, and most markup carry over. What changes is the placeholder data (Pinpoint paths such as User.UserAttributes.FirstName) and the template fields: Pinpoint uses Subject, HtmlPart, and TextPart, while SES v2 uses TemplateContent with Subject, Html, and Text.
What is the difference between Amazon SES and Amazon Pinpoint for email?
Pinpoint added endpoints, segments, campaigns, and journeys on top of email sending. Amazon SES is the sending service on its own: you store templates in SES and your application sends with a template name and the data for its placeholders.
Should I use the AWS migrator script or Huskar Templates?
They do different jobs, and many teams use both. The AWS sample script converts templates in bulk from the command line: it rewrites placeholders and fields and can deploy to SES. Huskar Templates is where you check the result: preview each template with sample data in mail-client frames, fix layout and Handlebars visually, and keep editing and publishing the templates after the migration.
Can Huskar Templates import templates directly from Pinpoint?
Not from Pinpoint itself. Export the HTML with the AWS CLI and upload all the files to Huskar Templates at once. If you have already moved templates into SES, for example with the AWS sample migrator, connect that AWS account and they are copied in once, as code templates. Then fix placeholders, preview with sample data, and publish.
Does Huskar Templates replace Pinpoint campaigns and journeys?
No. Huskar Templates designs and publishes Amazon SES email templates. It does not send email, manage lists, or run campaigns. Your application or another tool sends through SES using the templates you publish.
What are the Amazon SES template limits?
You can create up to 20,000 stored email templates in each AWS Region, and each template can be up to 500 KB including both the HTML and text parts.