PlatformEventMigration | Tooling API

Supported SOAP API Calls

create(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()

Supported REST API Methods

DELETE, GET, PATCH, POST

Fields

Field	Details
DeveloperName	Type string Properties Create, Filter, Group, Sort, Update Description The unique name for the PlatformEventMigration object. This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. This field is automatically generated, but you can supply your own value if you create the record using the API. When creating large sets of data, always specify a unique DeveloperName for each record. If no DeveloperName is specified, performance can slow down while Salesforce generates one for each record. Note Only users with View DeveloperName OR View Setup and Configuration permission can view, group, sort, and filter this field. Note
EventObject	Type reference Properties Create, Filter, Group, Nillable, Sort, Update Description The ID of a standard volume platform event that needs to be migrated to a high volume platform event. You can find the ID by executing this Tooling API SOQL query in the developer console: `SELECT Id FROM CustomObject WHERE DeveloperName='YourStandardVolumePlatformEvent'` The name to use as the DeveloperName of your SVPE is labeled Object Name in the UI.
MasterLabel	Type string Properties Create, Filter, Group, Sort, Update Description Label for PlatformEventMigration.

Usage

All standard volume platform events must be migrated to high volume platform events before Winter ‘27. This API provides a means for migration. Standard volume platform events that aren’t migrated won’t work starting in Winter ‘27.

Before starting a migration, ensure that all publish activity has stopped and all subscribers, including triggers and flows, are done processing, then perform a POST request to this endpoint.

1/services/data/v67.0/tooling/sobjects/PlatformEventMigration

Provide the values in the request body. This example request starts migrating the standard volume platform event 01Ixx0000005aUJ to a high volume platform event.

1{
2          "DeveloperName":"svpeConfig",
3          "MasterLabel":"svpeConfig",
4          "EventObject": "01Ixx0000005aUJ"
5        }

A successful POST request returns a response that includes an ID.

1{
2          "id":"1hXxx00000000mPEAQ",
3          "Success":true,
4          "Errors":[],
5          "Warnings":[],
6          "infos":[]
7        }

To check the status of your migration, use the ID in a GET request to this endpoint.

1/services/data/v67.0/tooling/sobjects/PlatformEventMigration<ID>

All these requests use the endpoint with the PlatformEventMigration record ID appended.

Get the status of a specific migration with a GET request.
Delete a specific migration with a DELETE request. Deleting a migration may not work because the migration could finish processing before the DELETE request is received. Because migration is a one-way door, it can’t be undone after it’s already happened.
Update a specific migration with a PATCH request. For this request, include the PlatformEventMigration definition in the request body.

Once a migration has started, publishes won’t work and you’ll be unable to create new triggers or flows until the migration finishes. A migration usually takes 10–15 minutes, but can last as long as 24 hours in some cases. You will receive an email when the migration is complete.

Also, you can query and retrieve the configurations in your org with SOQL. If querying from the Developer Console Query Editor, ensure that you select Use Tooling API. This example query retrieves all configurations set up in your Salesforce org.

1SELECT Id, DeveloperName, MasterLabel, EventObject, MigrationStatus, StartDate, EndDate, HighVolumePosition FROM PlatformEventMigration