Skip to main content
The Migration History screen records every migration you have run through Vortex Staging. It is the audit log for compliance, the troubleshooting surface for failures, and the dashboard for in-flight runs.

​
What is captured per row

Each row in the Migration History grid includes:
  • Request ID. Unique identifier for the migration run; quote this when raising a support ticket.
  • Source environment. The store and storefront the migration read from.
  • Destination environment. The store and storefront the migration wrote to.
  • Start time. When the run started.
  • Status. Current state (In Progress, Completed, Failed, Cancelled).
  • Completion time. When the run finished (blank if still in progress).
  • Actions. Available controls.
Migration history grid

​
Action buttons

For completed migrations you will see a Details button. For migrations that are still running, you will typically see both Details and Cancel.
  • Details. Click to view the per-entity migration status and any errors that occurred. This is where you go first when something has gone wrong.
  • Cancel. Available only on in-progress runs. Stops the migration after the current entity finishes; partially-migrated data remains in the destination.

​
Drilling into Details

Selecting Details shows the status of each migrated entity and any errors that occurred. You can also filter results by date range or by Request ID to find a specific migration. Migration details with per-entity status The Details screen shows:
  • Per-entity row for every entity type included in the run (Products, Collections, Customers, etc.).
  • Total count migrated.
  • Skipped count (records that already existed in the destination).
  • Failed count.
  • Downloadable log file for error investigation when failures occur.

​
Filtering and finding a specific run

Two filters are available on the Migration History grid:
  • Date range. Narrow the grid to a specific window (yesterday, last week, last month, custom range).
  • Request ID. If you have a Request ID from a support ticket, paste it here to jump straight to that run.

​
Downloading logs

For any failed entity row, click the Download Log button to pull the JSON-formatted error log for that entity. The log includes the Shopify API response, the source record ID, the destination handle (or matching key), and the error type. This is the primary artefact to attach when raising a support ticket.

​
Common reasons for partial failure

Most migrations complete with at least some skipped or partially-failed records. The most common causes are:
  • Inaccessible source image URLs. Expired CDN links cause image upload failures.
  • Validation errors. A source record with data that fails Shopify validation rules in the destination (for example, a discount code that references a customer segment that does not exist in the destination).
  • Rate limiting. Shopify’s GraphQL Admin API rate limits cause transient failures that retry automatically; persistent rate limiting is logged.
  • Missing dependencies. A discount code referencing a product handle that has not been migrated yet.

​
FAQ

​
How long is migration history retained?

Migration History is retained for the lifetime of your Vortex Staging tenant. There is no automatic purge; old runs remain visible for audit and debugging.

​
Can I export Migration History?

Per-run logs are downloadable as JSON. A bulk export of the full history grid is on the roadmap; for now, the in-app filter and Details drilldown cover most needs.

​
What is a Request ID for?

The Request ID uniquely identifies a migration run end-to-end. Quote it when raising a support ticket so the Vortex IQ Helpdesk can locate the run instantly.

​
Can I retry just the failed entities?

Yes. Re-run the migration with the same source and destination. Already-migrated records are skipped (Ignore mode), so only the previously-failed records will be retried.