Migrate from Project Risk Manager to Asana

Each Project Risk Manager Risk record maps to an Asana Task within the appropriate Project. The risk title becomes the task name; risk description migrates as the task description. We map probability and impact scores to custom number fields prm_probability__c and prm_impact__c on the task. Risk status (Open, Mitigated, Closed, Accepted) maps to a custom dropdown field prm_risk_status__c. The task is created in the destination Project that corresponds to the risk's parent Project in Project Risk Manager.

Mitigation Actions linked to a parent Risk in Project Risk Manager map to Asana Subtasks of the migrated risk Task. The action text becomes the subtask name; owner email resolves to the assignee in Asana (unmatched owners flagged for manual reassignment); due date migrates to the subtask due date field; status maps to the subtask completed flag or a custom prm_action_status__c field if the source uses custom status values beyond open and closed.

Project Risk Manager Project records map directly to Asana Projects. The project name and description migrate as-is. We use the project name as the Asana Project name and create the project structure before any risk Task imports so that the parent relationship is satisfied at import time. If the source project has a start or end date, we set the corresponding Asana project dates.

Project Risk Manager risk categories (e.g., Technical, Financial, Operational, Compliance) are stored as picklist values. We recreate the full category taxonomy as a global custom dropdown field prm_risk_category__c on the Task object in Asana and map the source picklist values directly. If the destination Asana workspace already has a comparable field, we map to the existing field to avoid duplication.

Risk owners in Project Risk Manager are extracted by email address. We attempt to match each owner email to an Asana User in the destination workspace via the Asana Users API. Owners with no matching Asana User are flagged in a reconciliation report for the customer's admin to provision before the migration proceeds. Owner assignment is set on the migrated Task at import time.

Project Risk Manager status values (Open, Mitigated, Closed, Accepted) migrate as a custom dropdown field prm_risk_status__c on the Task. If the customer prefers a section-based approach, we alternatively map status to Asana Sections within the Project and move tasks between sections during migration. The customer chooses the strategy during scoping. Migrations using sections require additional section management in the import script.

Project Risk Manager probability scores (numeric or percentage) map to a custom number field prm_probability__c on the Task. We preserve the original scale (e.g., 1-5 or 0-100) as specified by the customer during scoping. If the source uses descriptive probability labels (Low, Medium, High), we map them to numeric equivalents agreed upon during field mapping.

Project Risk Manager impact scores map to a custom number field prm_impact__c on the Task using the same scale logic as probability. Some customers use a combined Risk Score (Probability x Impact) in Project Risk Manager; we calculate this as a formula field prm_risk_score__c in Asana using the two migrated values if the Advanced plan is in use, or document the calculation for manual use.

File attachments linked to Project Risk Manager risk records are extracted and uploaded to the corresponding Asana Task via the Asana Attachments API. Asana's API does not support attachments larger than 100 MB per the official documentation; attachments exceeding this are flagged for the customer to host externally and link as a URL instead. We re-link all successfully migrated attachments to the correct target task after upload.

Risk-level comments and discussion threads are exported with a timestamp and author from Project Risk Manager. We import them as Asana Task stories (comments) on the migrated Task, preserving the author name and timestamp. If the author email does not match an Asana workspace member, the comment is posted under the migration account with a note indicating the original author.

Any custom metadata fields on Risk records (e.g., Risk ID, Root Cause, Contingency Plan, Escalation Flag) are mapped to additional custom fields on the Task. We pre-create all required custom fields in Asana before migration begins and validate that the field types match (text, number, date, dropdown) to avoid API errors during insert.

Project Risk Manager created date, modified date, and any last-assessed date on Risk records are preserved in Asana using the created_at and modified_at task properties. We set these at insert time via the Asana API to preserve the original historical record of when each risk was identified and last updated.