Confirm Migration
POST /integrations/migrations/{migration_id}/confirm
Accept the discovery and START IMPORTING. Records begin landing.
A migration cannot be un-run - only cancelled part-way, leaving whatever
already arrived. Read the status first: its warnings are the things
discovery could not resolve on its own.
An empty body accepts the discovery as proposed, which is the point of previewing it. Org admin, matching the app.
Authorizations
Parameters
Path Parameters
Migration id from discovery.
Migration id from discovery.
Header Parameters
Request Body
Accept a discovery and START IMPORTING.
This is the irreversible half: records begin landing in graph8 and a migration cannot be un-run, only cancelled part-way.
Both fields are OPTIONAL and omitting them accepts the discovery as
proposed - which is the point of previewing it first. Send
field_mappings_override to change where a CRM field lands, or
selected_list_ids to import only some lists.
object
Responses
202
Successful Response
object
An open envelope for a connection, a token or a migration report.
Open because the migration STATUS payload carries a per-entity progress map, a discovered-field map and a pipeline list that all grow with the providers - and because a dropped warning on a migration report reads as “nothing went wrong”.
object
422
Validation Error