What the readiness workflow provides
Use the workflow to:- assess migration readiness
- identify source projects, issue types, fields, users, statuses, and dependencies
- review risks or unsupported mappings
- prepare CSV templates for a governed import
- prepare communication and cutover guidance
Before you begin
Make sure:- your organization has permission to plan or manage imports
- you are in the correct organization and team context
- you know the Jira sites and projects in scope
- an authorized Jira administrator can provide approved metadata or exports
- sensitive Jira data is removed from planning attachments unless required
Run a readiness assessment
- Open
Import / Exportand choose the Jira migration readiness workflow when it is available. - Enter the source scope requested by the page.
- Review detected project, field, issue-type, workflow, user, and dependency information.
- Resolve blockers and unsupported mappings before preparing data.
- Download or generate the approved CSV templates.
- Review the communication and cutover checklist with Jira and LoopIQ administrators.
- Use the normal LoopIQ import workflow for the prepared files.
- Validate record counts, organization and team ownership, assignees, statuses, links, and a sample of migrated records.
Handle users and mappings safely
- Map assignees only to members available in the target LoopIQ team.
- Decide how inactive or unknown Jira users should be represented.
- Preserve Jira keys and source URLs in approved source-reference fields where supported.
- Treat proposed status or field mappings as review items until an administrator approves them.
- Never use a successful readiness score as authorization to import another organization’s data.