Migrate from Project Risk Manager to Trello

Project Risk Manager Risk records map to Trello Cards. Risk title becomes Card name, Risk description becomes Card description, Probability and Impact scores migrate to Trello Custom Fields (number or select type) on the Card. Risk Status (Open, Mitigated, Closed, Accepted) maps to the Card's List position within the Board, or to a Label color if the customer prefers to preserve status as a label. We create a Custom Field schema per Board if risk types vary by project. If Trello Standard plan ($5/user) is not active, Custom Fields are not available and probability/impact scores are stored in the Card description instead.

Project Risk Manager Mitigation Actions linked to a parent Risk map to Checklist items on the corresponding Trello Card. Action title becomes the Checklist item text. Action due date migrates to the Checklist item if Trello Premium plan is active; otherwise the due date is noted in the Card description. Action owner cannot be assigned as a Member on a Checklist item in Trello (owner assignment is Card-level only), so we flag the owner in the Checklist item text prefix and deliver a list of owner-to-Member mappings for manual reassignment post-migration. Action status (Pending, In Progress, Complete) is preserved as a Checklist item state (unchecked, checked) or as a separate Label if the customer requires granular status tracking.

Project Risk Manager Project records map to Trello Boards. If the customer's Project Risk Manager instance has fewer than 10 active projects and Trello Standard plan or above is active, we create one Board per Project with lists representing risk status columns (e.g., Open, Under Review, Mitigated, Closed). If Trello Free plan is active (10 boards maximum), we consolidate into one Board with Lists for each Project and use Card Labels to distinguish project membership. Board description carries the Project name and key identifiers. Board URL is stored for cross-reference.

Project Risk Manager Risk Categories (e.g., Technical, Financial, Operational, Compliance, Strategic) map to Trello Labels. We preserve the full category taxonomy as Labels on each Card, using a consistent naming convention (e.g., 'Cat: Technical') and the customer's existing color scheme if available. Labels are scoped to the Workspace by default; we advise the customer if they prefer Board-level Labels for project-specific taxonomies. If the customer uses sub-categories, we flatten them into label names separated by a forward slash (e.g., 'Cat: Technical / Schedule') or create a separate label series per parent category.

Project Risk Manager Risk Owners (assigned by name on each risk record) map to Trello Members on the Card. We extract distinct owner names from all Risk and Mitigation Action records, match them to Trello workspace Members by email address if the customer provides an email cross-reference, and assign Members to Cards during migration. Unmatched owners are flagged in a reconciliation report with the Card name and owner name, and the customer assigns the Member in Trello post-migration. If the destination Trello workspace has no existing Members (fresh workspace), we deliver the owner list as a provisioning request for the customer to invite users before or after migration.

Project Risk Manager Risk Status values (Open, Mitigated, Closed, Accepted, Escalated) map to Trello List positions within a Board if the customer prefers board-native status tracking, or to a Label color if the customer prefers to use Labels for status. We confirm the preferred strategy during scoping. If Lists are used, each status value becomes a List and Cards are placed in the appropriate List. If Labels are used, each status becomes a Label with a distinct color and the Card stays in its project List. We flag any Project Risk Manager status values that do not map cleanly to Trello's available structural elements.

File attachments linked to Project Risk Manager Risk records are extracted and uploaded to the corresponding Trello Card as Attachments. Trello Free plan limits attachments to 10MB per file; Trello Standard raises this to 250MB. We check file sizes during extraction and flag any files exceeding the destination plan limit, recommending either an upgrade or an alternative document management approach (shared drive link in Card description). Attachment type (PDF, image, spreadsheet) is preserved. We re-link attachments to the correct Card by matching the parent Risk ID.

Project Risk Manager Risk-level comments and discussion threads migrate to Trello Card Comments. Each comment preserves the original author name, timestamp, and comment body. Chronological order is maintained by setting the comment timestamp on import. If the comment author does not match a Trello workspace Member, the comment displays under the author's name without a Member avatar, which is expected behavior in Trello. Very long comment threads are imported in full; Trello does not impose a comment length limit.

Project Risk Manager Probability field (typically a numeric percentage or 1-5 scale) migrates to a Trello Custom Field on the Card if Trello Standard plan or above is active. We define the Custom Field as a number type with a display format matching the source (percentage or integer). If Trello Free plan is active, Probability is stored as text in the Card description in a structured prefix (e.g., 'Probability: 75%') and we document the rebuild recommendation for Custom Field activation.

Project Risk Manager Impact field (typically a numeric scale or severity label such as Low, Medium, High, Critical) migrates to a Trello Custom Field on the Card. If the source uses a numeric scale, we create a number Custom Field. If the source uses a severity label set, we create a select Custom Field with the available options. Trello Premium or Standard is required for Custom Fields; we flag this at scoping and do not charge extra for the plan recommendation.

Project Risk Manager Risk Due Date (response due date or target resolution date) migrates to the Trello Card Due Date field. If a time component is present in the source, we preserve it in the Card Due Date with time. Card Start Date is set from the Risk creation date if the customer requests it. We flag any risks without due dates as not having a date constraint in the migration record.

Project Risk Manager Project-level metadata fields (Project name, description, start date, target date) are captured as Board description fields in Trello. If the customer's Project Risk Manager uses custom project-level fields beyond name and description, we include those in a Board-level Label or in a dedicated metadata Card (titled 'Project Overview') with the information in the Card description. We confirm the preferred approach during scoping.