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.
Authorizations
Your signed-in Vortex IQ session (browser calls). Requests are scoped to your organisation, which must have Store Migration enabled. For server-to-server calls use a bearer token instead — 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 full, dry-run, verify, counts skip, update, replace Items still needing review.
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.