Data Handling
Data Migrayt Reads (from ADO)
During a migration, Migrayt reads the following data from your Azure DevOps project:
| Data | Purpose |
|---|---|
| Work item fields (title, description, state, assignee, etc.) | Transformation and writing to Jira |
| Work item relations | Recreating links in Jira |
| Iteration paths and area paths | Sprint and component mapping |
| Attachment metadata and file content | Re-uploading to Jira |
| Comments | Recreating in Jira with attribution |
| User identities (display names, email addresses) | User mapping and ghost account creation |
Data Migrayt Writes (to Jira)
Migrayt writes:
- Jira issues (all mapped fields)
- Jira issue links
- Jira Sprint assignments
- Jira Component assignments
- Jira attachments
- Jira comments (attributed to the migration service account)
- Jira worklogs (7pace add-on)
- Xray test steps (Xray add-on)
Data Migrayt Retains
| Data | Retention | Purpose |
|---|---|---|
| ADO/Jira OAuth tokens | Until disconnected | Reconnecting for incremental migrations |
| Mapping configuration | Indefinite | Re-running or auditing migrations |
| Per-item migration state (ADO ID → Jira key) | Indefinite | Idempotency for incremental runs |
| Migration run statistics | Indefinite | Audit trail, billing verification |
| Post-migration report text | Indefinite | Reference |
| S3 attachment staging files | 30 days | Not retained permanently |
Data Migrayt Does NOT Retain
- Work item content (titles, descriptions, comments) — passes through memory only
- Attachment file content — downloaded and immediately re-uploaded; not stored
- ADO user passwords or SSO tokens
- Any data from ADO projects not selected for migration
Right to Erasure
To delete all your Migrayt data (credentials, migration history, mapping configuration):
- Disconnect all platforms from Account Settings
- Delete all projects from the Projects screen
- Contact support@migrayt.ai requesting full account deletion
Account deletion is completed within 30 days. ADO and Jira OAuth tokens are revoked immediately.
Subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| AWS (Amazon Web Services) | Compute, storage, secrets management | EU-West-1 (Ireland) |
| Anthropic | AI mapping suggestions | US (zero retention) |
| Stripe | Payment processing | EU |
| SendGrid (AWS SES) | Transactional email | EU |
All subprocessors are bound by Data Processing Agreements. No data is sold to or shared with third parties for marketing or advertising purposes.