Get migration
Full run detail: status, per-phase progress, counters, and the forecast.
A finished run is served from the durable snapshot (so it survives engine teardown); a live run is read straight from the engine for real-time state. Either way the response shape is the same.
API-token callers: the live-run (engine) read is not available with bearer authentication — while a run is queued, in_progress, or paused (including a True Replica run’s verification window), this endpoint returns 403 not_available. Follow live runs with GET /migrations/{id}/stream instead; detail becomes readable here once the run reaches a terminal status.
Authorizations
A bearer token from Login, sent as Authorization: Bearer <token>. Valid for 10 days by default; scoped to the user and organisation it was issued for. Rotating or disabling the organisation's API credential immediately invalidates all outstanding tokens. Browser calls from a signed-in app.vortexiq.ai page are also accepted via session cookie — see Authentication.
Path Parameters
The migration request id returned by Create migration.
Response
Run detail.
BC completed, failed, and cancelled are terminal.
queued, in_progress, paused, completed, failed, cancelled, partial_completed The engine's run mode. A True Replica run reports full here — its true-replica marker lives on the History row's mode, and its pipeline state in the replica block below.
full, dry-run, verify, counts The run's data-treatment strategy (skip = Add New Only, update = Update Existing, replace = Make Exact Copy) — this is the authoritative field for how existing destination data was handled.
skip, update, replace Items still needing review.
Present on selective page-template runs only: what was picked and how the channel-wide global content fared.
Sizing and ETA estimate.
Sizing and ETA are priced from different bases deliberately: the ETA follows the run's real scope (picks, strategy, order statuses), while memory is pinned to store scale — the engine's working set does not shrink with a small pick, so sizing on picked counts alone would under-provision the run.
The entity keys the run was created with.
True Replica runs only: the verification pipeline's step tracker. null or absent on other runs.
True Replica runs only: true once the store-owner report is durably stored. The report itself is viewed from the StagingPro UI's run detail page.