Skip to content
Sendora Cloud
Create account
Migrate from AWS Pinpoint

Move from AWS Pinpoint to Sendora.

Move push + SMS + email + journeys off AWS Pinpoint to Sendora Notifications + Automation.

Total effort: 1-2 weeks depending on Pinpoint Journey complexity.

Step-by-step

  1. 1

    1. Export endpoints + segments + journeys

    Pinpoint REST API exports endpoints (users + push tokens), segments, and journey definitions. Pull last 90 days of event metrics.

    Half a day
  2. 2

    2. Migrate user identity + push tokens

    Endpoint export maps to Sendora Customers profiles + Push module. push_token + platform per-row port directly. Custom attributes become Customer traits.

    Half a day
  3. 3

    3. Configure Sendora Push providers

    APNs (.p8 + key_id + team_id) + FCM service-account JSON upload via Sendora dashboard. Web Push VAPID keys generated automatically.

    1 hour
  4. 4

    4. Migrate BYOD email (if using Pinpoint Email)

    Reuse your SES-verified domain — Sendora BYOD via Resend Domains accepts the same DKIM + SPF + DMARC records.

    1 hour + DNS propagation
  5. 5

    5. Replace Pinpoint SDK / API calls

    AWS Amplify Pinpoint SDK → Sendora SDK. Modern ergonomics: `analytics.record(...)` → `sendora.track(...)`. SDK ships on Web / SSR / RN / iOS / Android.

    1-2 days per platform
  6. 6

    6. Rebuild Journeys in Sendora Automation

    Pinpoint Journeys port to Sendora Automation. Branching, waits, multi-step holdouts, audience-triggers all port directly. Visual canvas + run history + per-step A/B all standard.

    1-2 days
  7. 7

    7. Cut over + sunset Pinpoint resources

    Parallel-run for 1-2 weeks. Once parity holds, sunset Pinpoint Project + IAM roles. SES domain can stay (Sendora BYOD uses it).

    1-2 weeks observation

Watch-outs

  • Pinpoint integrates tightly with other AWS services (Lambda triggers, CloudWatch metrics, Cognito hooks) — review each integration for Sendora equivalents (webhooks + Health module + Authentication).
  • If you're on AWS GovCloud or have strict data-residency requirements, verify Sendora's residency offering covers them.
  • Pinpoint SMS routing via SNS — Sendora uses BYOP (Twilio / MessageBird / Sinch); plan carrier-routing equivalence.
Lands you on

Ops Alerts

Slack + webhook routing for platform events — define rules, get pinged when they fire. Same taxonomy as the rest of Sendora.

PagerDuty + Opsgenie + custom Slack webhooks split this between three vendors with separate event sources. Sendora's Ops Alerts router fires on the same event stream that Analytics + Automation + Webhooks already see — rule-match on event type, route to Slack channels or arbitrary HTTPS webhooks, retry on transient failure, log every dispatch attempt. One taxonomy, one log of every alert, the same audit surface ops teams already use for everything else.

Read full Ops Alerts page

Stuck on the migration? We'll help.

Launch partners get white-glove migration help direct from the engineering team. Free plan covers real product use during the parallel-run period.

Create free accountBecome a launch partnerSide-by-side vs AWS Pinpoint