Budget for three layers: final Pinpoint engagement charges, ongoing channel delivery, and replacement software plus migration work. AWS ended Pinpoint support on October 30, 2026, but specified messaging APIs continue. Calculate your current workload first, then price the workflows your marketing team must preserve, not just the messages it sends.

Last reviewed: October 5, 2026. Rates below are in US dollars unless stated otherwise.

If you own customer journeys, the useful question is not simply “What does Pinpoint cost?” It is “What will it cost to keep our campaigns running after Pinpoint?” A sending-rate comparison cannot answer that on its own.

AWS stopped accepting new Pinpoint customers on May 20, 2025. Support for the engagement service ended on October 30, 2026, and its console and resources such as endpoints, segments, campaigns, journeys and analytics are no longer accessible. AWS distinguishes these from the SMS, voice, mobile push, OTP and phone-number-validation APIs supported by AWS End User Messaging. See the official migration notice.

Use our deadline guide for the retirement scope and the Pinpoint to SES migration guide for export and cutover work. To scope the business transition, discuss a CampaignHQ migration.

What goes into an Amazon Pinpoint estimate?

Keep the bill in separate lines so finance and marketing can see what changes at migration:

• Legacy engagement: targeted endpoints, collected application events and in-app requests up to the end of support.
• Channel delivery: email through Amazon SES and relevant messaging channels through AWS End User Messaging.
• Selected extras: dedicated IPs, deliverability tools, numbers, storage, compute or other services your setup actually uses.
• Replacement and transition: engagement software, data mapping, journey rebuilds, testing, training and any overlap between systems.

An endpoint is one contact destination, such as an email address or a push token. It is not necessarily one person. Under the Pinpoint audience allowance, the first 5,000 endpoints targeted each month are free, then the charge is $0.0012 per endpoint. The Monthly Targeted Audience charge applies once per unique endpoint per calendar month when targeted by a campaign, journey or in-app request. AWS excludes sends through the SendMessages API or Pinpoint SMS and Voice API from this charge.

That distinction matters: a team with the same customer count can have a different bill depending on its endpoints and sending method. Use the actual billing and usage records, not a contact-list export alone.

Calculate the remaining Pinpoint bill

Start with targeted destinations. Count unique endpoints targeted during the billing month. Do not multiply that count by campaign frequency. AWS bills repeated targeting differently from additional destinations: the monthly endpoint allowance and rate apply to the unique endpoint count.

For illustration, suppose a campaign-based workload targets 50,000 unique endpoints in one month. Its audience charge is (50,000 − 5,000) × $0.0012 = $54. This is a hypothetical audience charge, not the total bill or a migration quote.

Add channel delivery. For push, the AWS End User Messaging rate card lists the first 1,000,000 notifications per month at no charge, followed by $0.000001 each. SMS and voice costs vary by destination and configuration. Obtain the rate for your actual route, message units and numbers rather than using one global SMS price.

Email needs a separate check. Amazon SES is the email delivery service AWS recommends for Pinpoint email migration. The current SES rate card offers both pricing plans and à-la-carte billing:

• À la carte: outbound email is $0.10 per 1,000 emails, with data and selected features charged separately.
• Essentials: the first volume tier, up to 10 million emails per month, is $0.16 per 1,000 emails and includes a different feature package.
• Pro and Enterprise: their per-email rates, fixed account/region fees and included features differ. Compare the complete configuration, not just one rate.

Check the plan in each AWS account and Region. The SES pricing-plan documentation explains how to view, change or cancel it. Do not assume every migrated account uses à-la-carte pricing, or subtract an old “62,000 EC2 emails” allowance from a current estimate.

In a hypothetical month with 200,000 outbound emails, sending alone is $20 at the stated à-la-carte rate or $32 at the stated Essentials tier. Neither figure includes data, other selected services, taxes or the engagement platform. The plans include different capabilities, so this is not a like-for-like platform comparison.

Add events and in-app requests. The Pinpoint rate card lists the first 100 million application events collected each month at no charge, then $0.000001 per event. In-app requests have a separate allowance: the first 15,000 per month at no charge, then $0.00011 per request. These are legacy engagement charges, not a promise that the same allowances transfer to your replacement.

Check optional services. Existing Pinpoint subscriptions may include its $1,250-per-month Deliverability Dashboard or $24.95-per-month dedicated IP addresses. Confirm what is enabled and its cancellation terms. For the destination system, price the chosen SES configuration rather than carrying every old charge forward or assuming it disappears.

Build a migration budget, not just a sending estimate

A low delivery bill does not tell you how much work it takes to preserve a renewal reminder, abandoned-cart follow-up or customer onboarding journey. Ask each proposed provider to separate these costs:

1. Recurring platform: campaigns, segmentation, workflows, reporting, users and support. Identify which plan includes your required operating controls.
2. Delivery: channel usage, numbers and any provider-specific charges. Specify whose account pays each provider.
3. One-time implementation: data export, attribute mapping, templates, integrations, consent and suppression checks, journey rebuilding and acceptance tests.
4. Transition overlap: any period when both systems remain active, plus the people responsible for preventing duplicate sends.

Give every vendor the same workload: monthly sends by channel, largest campaign, peak sending window, active journeys, event sources, destination countries and required reporting. A quote for email delivery only should not be compared with a quote that includes campaign operations and migration support.

Use the retention-platform migration checklist to define acceptance criteria. For different replacement models, use the Pinpoint alternatives guide. This pricing worksheet helps prepare those decisions; it does not replace the technical migration plan.

Budget mistakes that can delay the cutover

Treating access as purchased capacity. A paid sending plan does not remove account restrictions. AWS documents an SES sandbox limit of 200 messages per 24 hours and one message per second, with recipient restrictions. Sandbox status is Region-specific. Check AWS production-access requirements and our production-access guide before committing a launch date.

Counting customers instead of destinations. An email address and a push token can represent the same customer but different endpoints. Reconcile billing units before comparing old and new platforms. A replacement may use contacts, profiles, credits or another unit.

Ignoring peak workload. A monthly allowance is not permission to send it all in one hour. Ask for daily and hourly capacity, warm-up requirements and the process for handling campaign spikes.

Assuming an export preserves a journey. Include the work to reproduce conditions, delays, templates and exit rules, then test consent and suppression behavior. Agree who signs off the rebuilt journey before its first customer send.

Use the AWS Pricing Calculator for the infrastructure portion

Keep account preparation separate from estimating: our SES account setup guide covers the former. The public AWS Pricing Calculator lets you configure estimates without signing in.

Add the destination services, Region and usage inputs that match your proposed architecture. Check the result against the current rate card and the pricing plan selected in your account. Save a dated estimate with its assumptions so procurement can compare revisions.

The calculator estimates AWS charges, not your entire transition. Add the engagement-platform quote and implementation scope separately. Our SES pricing guide provides additional email-cost context; the current AWS rate card and account configuration should control the final estimate.

Where CampaignHQ fits

CampaignHQ runs email, WhatsApp and SMS on one contact database, for teams that need to run campaigns, segments and automated journeys. Explore its current product page. CampaignHQ is a Meta Business Partner. AWS supports the delivery setup; it is not a substitute for choosing the right marketing workflow.

Separate CampaignHQ’s platform and sending model from your AWS bill. Its Email pricing page distinguishes included CampaignHQ email credits from customer-owned AWS sending, where provider charges apply directly. Included monthly credits reset each billing cycle; purchased top-ups remain valid for six months. Throughput and fair-use limits still apply.

Bring your current bill and one critical journey to the discussion. Confirm data mapping, integrations, delivery ownership, migration support and acceptance tests before agreeing a price or timeline. Do not assume a drop-in replacement for every Pinpoint API or automatic preservation of every journey.

Can we buy CampaignHQ through AWS Marketplace?

Yes. CampaignHQ is listed on AWS Marketplace as a SaaS product, so teams that buy software through AWS can subscribe from their AWS account and see the charges on their AWS bill. You can also sign up directly on campaignhq.co.

Frequently asked questions

Does the Pinpoint shutdown end all AWS messaging APIs?

No. AWS distinguishes the retiring engagement service from SMS, voice, mobile push, OTP and phone-number-validation APIs supported by AWS End User Messaging. It recommends SES for Pinpoint email migration. Confirm which resources and APIs your application actually uses before budgeting the change.

Is Pinpoint pricing based on contacts or messages?

Both audience and channel usage can matter. For eligible campaign, journey and in-app activity, Monthly Targeted Audience counts unique targeted endpoints, not necessarily unique people. Message delivery, application events and selected extras are separate lines. API-only sends can have different audience-charge treatment.

Can I budget every SES email at $0.10 per 1,000?

No. That is the published à-la-carte outbound rate, not a universal all-in rate. SES also offers Essentials, Pro and Enterprise plans. Check the plan in your account and Region, then add applicable data and optional-service charges.

Does moving to SES recreate Pinpoint campaigns and journeys?

No. SES provides email delivery. Your budget must also cover the engagement capabilities and operating workflow you need, whether through another platform or a separately built solution. Include data mapping, journey rebuilding and testing rather than treating a sending-service change as the whole migration.

What should an Indian team include in its migration quote?

Request separate platform, delivery, implementation and transition-overlap costs. State currencies, taxes, billing periods, channel destinations, monthly volume and peak capacity. Define the workflows to preserve and the acceptance tests. This makes quotes comparable without assuming every provider offers the same scope.

Written by CampaignHQ Team