Quick Start
This guide walks through completing a full migration using the Migrayt wizard. You'll need admin access to both your ADO project and your Jira project.
Prerequisites
- Azure DevOps project with work items to migrate
- Jira Cloud project (must already exist)
- Admin access to both platforms
- 10 minutes
Step 1 — Create an account
Go to app.migrayt.ai (opens in a new tab) and sign in with your Microsoft account (recommended) or register with email and password.
Step 2 — Create a migration project
From the dashboard, click New Project and select:
- Source: Azure DevOps
- Destination: Jira Cloud
- Name: Something descriptive (e.g.
Acme Corp ADO → Jira)
Step 3 — Connect Azure DevOps
Click Connect with Microsoft account (recommended) or enter your ADO Personal Access Token manually.
For PAT, the minimum required permissions are:
- Work Items — Read
- Project and Team — Read
- Analytics — Read
After connecting, select your ADO Organisation and Project from the dropdowns.
Step 4 — Connect Jira Cloud
Click Connect with Atlassian account or enter your Jira API token.
After connecting, select your Jira Site, Project Key, and Board (for sprint mapping).
Step 5 — Review the scan results
Migrayt scans your ADO project. The scan takes 1–5 minutes depending on project size.
Review the summary:
- Item counts per type
- Iteration path tree
- Area path tree
- Attachment total size
- Calculated price
Step 6 — Review and confirm mappings
Work through the three mapping screens:
- Type mapping — Review how ADO types map to Jira types. Accept the AI suggestions or override as needed.
- Field mapping — Review field-by-field mappings. Check any low-confidence mappings (shown in amber/red).
- Iteration & area mapping — Review sprint and component mappings. Decide which iterations to create as new sprints.
Step 7 — Pay
Review the price breakdown and complete payment via Stripe Checkout. Test migrations using dry run mode are free.
Step 8 — Run the dry run
The dry run migrates 10 representative items to show you exactly how they will appear in Jira. Review them carefully. If anything looks wrong, go back to the mapping screens to adjust.
Confirm the dry run to proceed.
Step 9 — Execute the migration
Click Start Migration. Progress is shown live. You can close the tab and return later — the migration continues in the background.
For a 5,000-item project with no attachments, expect ~10 minutes. For 80,000 items with attachments, expect several hours.
Step 10 — Review the report
When complete, the AI-generated report summarises:
- Items migrated successfully
- Items that failed (with reasons)
- Fields that were not migrated
- Users that required ghost assignment
- Recommended next steps in Jira
Download the full ID mapping CSV from the report to keep a permanent record of ADO ID → Jira key mappings.