Hey Trailblazers 👋
Heads up: Standard-Volume Platform Events (SVPE) will be retired in Winter '27. If you've been
waiting for an easier path onto High-Volume Platform Events (HVPE), the new SVPE→HVPE migration
tool is now available in preview sandboxes — and your migration clock has officially started.
The tool automates the heavy lifting of migrating your event definitions, Trigger and Flow
subscribers, and downstream integrations from SVPE to HVPE — minimizing rework for both customers
and AppExchange partners.
⏰ This tool is the supported path off SVPE before retirement.
Why HVPE?
- Longer event retention
- More generous daily allocations and better scaling headroom
- The forward path for event-driven architecture on the platform
Where things stand:
- ✅ Available now in your Preview (Pre-release) Sandbox
- 🚀 Generally Available with the Summer '26 release (production rollout starts ~June 15, 2026)
- 🛑 SVPE retires in Winter '27 — plan your migration accordingly
What I'm asking of you:
1. Try it now in your preview sandbox — don't wait for GA.
2. Tell us what worked and what didn't — especially edge cases, weird subscribers, or anything
else. All feedback is wanted.
3. ISV/Partner builders — Once you run it, your events will be updated, so you'll need to publish
a new package version for your downstream customers. Please run it against your managed packages
and share what you find, partner feedback is especially valuable here.
💬 Reply in this thread with questions, findings, or issues — I'll be watching and responding
personally.
Hi all. Finally have some timelines for you on Custom Standard-Volume Platform Events (SVPE) retirement.
The "easy" button will be available as of
Winter '27. Because of this we've pushed the retirement date to Dec 15th. Dec 15th is the hard date for everyone — so once Winter '27 reaches your org, you'll have roughly two months to complete the migration. I'll be updating all formal documentation to reflect the new date.
Thanks for all your cooperation as we look to close this out. Please let me know if you have any questions or concerns.
@Javier Coca@John Dagsa@Phil W@Anthony Heber@Charles Troster
