Migrate from raidlog.com to Jira

Each raidlog.com Project becomes a Jira Project. We extract project metadata including name, description, start and due dates, and owner assignment via the Projects API and create Jira Projects using the Jira REST API. If the source has multiple Enterprise Private Workspaces, each workspace becomes a separate Jira project or a Jira project-group depending on the customer's preference for workspace isolation in Jira.

Raidlog.com Risks map to Jira issues with a custom Issue Type named Risk. We map probability to a Jira custom number field, impact to a Jira custom picklist (Low/Medium/High/Critical), and status (Open, Mitigated, Closed) to a Jira status in the project's workflow. Owner migrates as Jira Assignee via email matching. We add a custom text field raidlog_type__c set to 'Risk' so the origin context is preserved in Jira.

Raidlog.com Actions map to Jira Task issues. Assignee, due date, priority (from raidlog.com priority field), and status map to Jira Assignee, Due Date, Priority, and Status. The action-to-risk linkage migrates as a Jira Issue Link (blocks/blocked by) after both issues exist in Jira.

Raidlog.com Issues map to Jira Bug or Task issues depending on the customer's naming convention preference during scoping. Severity (Low, Medium, High, Critical) maps to a Jira custom picklist; status maps to Jira status. Resolution date maps to Jira Resolution Date field. Owner maps to Jira Assignee.

Raidlog.com Decisions map to Jira issues with a custom Issue Type named Decision. We map owner to Jira Assignee, date made to a custom date field decision_date__c, status to Jira status, and rationale to the Jira issue description. The linked project context migrates as the Jira project parent reference.

Raidlog.com Dependencies (inter-log relationships where, for example, Risk A blocks Action B) do not have a native Jira equivalent as discrete records. We reconstruct each dependency as a Jira Issue Link of type 'Blocks' or 'Blocked by' after both the source and target issues exist in Jira. The complete dependency graph is extracted from the All RAID endpoint during scoping and resolved during the link-creation phase. Customers receive a written dependency matrix listing every reconstructed link.

Lessons Learned records in raidlog.com have no direct Jira issue type. We create Jira issues with a custom Issue Type named Lesson and add a custom field lesson_type__c to distinguish Lessons Learned from other records. The lesson content migrates to the Jira issue description. Lessons Learned attached to a specific project in raidlog.com link to the equivalent Jira project.

Change Log entries (requester, date, status, description) migrate as Jira issues with a custom Issue Type named Change Request. Requester becomes Jira Reporter, date becomes Created, status maps to Jira status, and description maps to issue description. We add a custom field change_status__c to carry the original raidlog.com change request status through the migration.

Raidlog.com tags apply to any RAID record. We extract the full tag taxonomy and apply it as Jira Labels (if the customer uses labels for cross-project classification) or Jira Components (if the customer prefers per-project categorization). The choice is made during scoping. Tag value mapping preserves the full original tag name; Jira label syntax conventions are applied during import.

Raidlog.com Users referenced as Owners across all log types are extracted and matched to Jira Users by email address. Owner assignments on Risks, Actions, Issues, and Decisions migrate as Jira Assignee. Any raidlog.com Owner without a matching Jira User email goes to a reconciliation queue for the customer's Jira admin to provision before record import resumes.

The Stakeholder List is a supplementary component of the RAID log. We export it as a distinct record set and create Jira Project Components or add the stakeholders as Jira Users with explicit project-level role assignments (e.g., Observer, Stakeholder). The customer's Jira admin selects the preferred approach during scoping.