Updated - October 3, 2026
Original Publication Date - July 1, 2024
Standard-volume platform events are legacy custom events that were deprecated in Spring '19 and are no longer supported. After Spring '19, you can’t define new standard-volume platform events; instead, you can only define high-volume platform events. You can continue to publish and subscribe to existing standard-volume events, but if you encounter issues, Salesforce won't address them and cases will be rejected as not supported. There are no troubleshooting steps or bug fixes for Standard-Volume Platform Events.
Standard-Volume Platform Events are now scheduled for retirement and end of life on December 15, 2026. On that date, users will no longer be able to publish or subscribe to Standard-Volume Platform Events. You have two ways to migrate your standard-volume platform events to high-volume platform events:
Option 1 — Self-service migration (recommended): In Setup, on the Platform Events page, use the migration button to convert all of your standard-volume platform events to high-volume platform events in one step. This option is available in the Winter '27 release.
Option 2 — Metadata API: Use the PlatformEventMigration metadata type to script the migration. See PlatformEventMigration in the Metadata API Developer Guide for the steps to migrate a standard-volume platform event to a high-volume platform event. This option requires you to migrate each event separately and is available as of Summer ‘26.
If you prefer to migrate manually and not use one of the two tools mentioned above, we recommend the following steps.
Replace all existing standard-volume platform events with high-volume platform events. To do this you can either migrate your existing standard-volume platform events to high-volume platform events or you can recreate your platform events from scratch.
To migrate your existing standard-volume platform events, ensure all publish activity has stopped and all subscribers, including triggers and flows, are done processing. Then go to Setup —> Platform Events and click the migrate button. This will migrate all of your standard-volume platform events to high-volume platform events and should take about 15 minutes, although the migration can take longer, up to 24 hours. You will receive an email when each event has been migrated. While the migration is running, publishes won’t work and you’ll be unable to create new triggers or flows until the migration finishes.
When you create a platform event, it is high-volume by default. To create a platform event from scratch, follow these steps.
From Setup, enter Platform Events in the Quick Find box, then select Platform Events.
On the Platform Events page, click New Platform Event.
Complete the standard fields. See Platform Event Fields in the Platform Events Developer Guide for more information.
Add the event fields.
Update all the automation and integration apps, such as flows, processes, Apex triggers, and Streaming API clients, that reference the standard-volume platform events with the new high-volume platform events.
To prevent any event loss, complete processing your standard-volume platform events before transitioning to high-volume platform events by following these steps.
Create an equivalent high-volume platform event in your org.
Stop the publishing process for all standard-volume events.
Process all remaining standard-volume events. (If this isn't possible via your business logic, you will have to wait 72 hours after stopping your event publishing to let all standard-volume events expire.)
Deactivate your standard-volume event subscriptions and delete all related artifacts (triggers, event definitions, etc.)
Start your high-volume platform event publish process and subscriptions.
If you have any questions or need assistance, refer to Salesforce Help or contact your Salesforce account team. For more information about Salesforce’s approach to retiring products and features, read our Product & Feature Retirement Philosophy.
002280033

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.