Pause & Resume
Migrayt migrations can be paused at any point during execution and resumed from exactly where they stopped. You will never need to restart a migration from the beginning due to an interruption.
How Pausing Works
Every work item that Migrayt successfully creates in Jira is immediately recorded in a persistent state store. When a migration is paused or interrupted, this record is used to determine which items have already been created.
When the migration resumes:
- Items already in Jira are skipped (identified by their
ado-id-{N}label) - The migration continues from the next unprocessed item
- No duplicates are created
This is guaranteed. You can pause, restart the server, lose network connectivity, or have the migration task interrupted by your cloud provider — the migration will pick up exactly where it left off.
Pausing a Running Migration
Via the UI
Click the ⏸ Pause button in the top-right corner of the migration progress screen. The button triggers a pause signal that is polled by the migration engine every 50 items.
The migration will stop cleanly at the next checkpoint (within seconds on a running migration) rather than stopping immediately mid-item.
Via the API
curl -X POST https://api.migrayt.ai/api/migrations/{runId}/pause \
-H "Authorization: Bearer {token}"The migration status transitions from RUNNING → PAUSED.
Resuming a Paused Migration
Via the UI
Return to the migration progress screen. Click ▶ Resume to restart the migration from where it stopped.
Via the API
curl -X POST https://api.migrayt.ai/api/migrations/{runId}/resume \
-H "Authorization: Bearer {token}"The migration status transitions from PAUSED → RUNNING.
What Happens to Items Already Created
Nothing. Items already in Jira are untouched when you resume. The migration engine checks each ADO item against the persistent state store before attempting to create it in Jira.
If an item is already in Jira, the engine:
- Records the existing Jira key in the ID map (so links work correctly)
- Increments the "skipped" counter
- Moves to the next item
Phase-Level Checkpointing
In addition to per-item checkpointing, Migrayt also checkpoints completed phases. If a migration is paused in Phase 5 (Transitions), it will not re-run Phases 1–4 on resume. It will continue from the next item in Phase 5.
| Phase | Description | Checkpointed? |
|---|---|---|
| 1 — Preflight | User/sprint/component setup | At start of run |
| 2 — Create items | Work item creation | Per-item |
| 3 — Hierarchy | Epic/parent linking | Per-item |
| 4 — Links | Issue links | After all links |
| 5 — Attachments | File uploads | Per-item |
| 6 — Transitions | Status transitions | After all transitions |
| 7 — Comments | Comment migration | Per-item |
| 8+ — Plugins | 7pace / Xray | Per-plugin |
Interruptions vs Pauses
An intentional pause (button click or API call) checkpoints cleanly before stopping.
An unintentional interruption (server restart, network failure, cloud spot instance termination) stops immediately. The migration resumes from the last checkpointed item — at most 50 items before the point of interruption.
In both cases, resuming is safe. No duplicates will be created.
Cancelling a Migration
Cancelling is permanent. The migration cannot be resumed after cancellation — a new run must be started.
Items already migrated to Jira are not removed when a migration is cancelled. If you cancel partway through, you will have a partial Jira project. You can either:
- Start a new migration run (already-created items will be skipped automatically)
- Manually delete the partial items in Jira and start fresh
To cancel:
curl -X POST https://api.migrayt.ai/api/migrations/{runId}/cancel \
-H "Authorization: Bearer {token}"