Migrate from raidlog.com to Microsoft Project

Each raidlog.com Project becomes a Microsoft Project plan file (.mpp) or a Project for the web / Planner Premium plan. The project name, start date, finish date, and owner map directly. If the customer uses Enterprise Private Workspaces in raidlog.com, each workspace maps to a separate Project plan file and the workspace hierarchy is preserved as a folder or SharePoint document library structure in the destination.

raidlog.com Risk records map to Microsoft Project tasks with custom fields capturing probability, impact, status, owner, and due date. We create a Risk custom text field (or use the built-in Flag1 and Text1 fields) for probability, impact rating, and risk category. The Risk title becomes the Task Name; description migrates to the Task Notes field. Dependencies where this Risk blocks an Action map to predecessor links in the project schedule.

raidlog.com Action Items map directly to Microsoft Project tasks. Assignee maps to the Resource Names field; due date maps to Finish; priority maps to Priority or a custom Priority field; status (Open, In Progress, Closed) maps to the % Complete or custom Status field. Action-to-Risk and Action-to-Issue linkages are reconstructed as predecessor-successor relationships or as cross-project links if the Action and Risk live in different plans.

raidlog.com Issue records map to Microsoft Project tasks with a custom Issue field set for severity, resolution date, and owner. The Issue title becomes the Task Name; description becomes Task Notes. Status migrates as a custom field (Open, Investigating, Resolved, Closed). Issues that block Actions reconstruct as predecessor links in the schedule.

raidlog.com Decision records map to Microsoft Project milestones (zero-duration tasks) if the Decision is a gating event, or to summary tasks if the Decision encompasses multiple downstream Actions. The Decision owner maps to Resource Names; date made and date due map to Start and Finish. We flag Decision records in the task name with a [DECISION] prefix for visibility in the Gantt view.

raidlog.com Dependency records link two RAID items (e.g., Risk A blocks Action B, Issue C delays Decision D). We reconstruct these as Microsoft Project predecessor-successor relationships (FS, SS, SF, FF) on the task level. Cross-type dependencies (Risk-to-Action, Issue-to-Decision) map to the appropriate predecessor type. We deliver a Dependency Map document listing every reconstructed predecessor link for the customer's PMO to validate against the original RAID log.

raidlog.com Lessons Learned records have no native Microsoft Project equivalent. We extract Lessons Learned as a tagged property on the relevant project task and append the Lessons Learned text to the Task Notes field with a [LESSONS LEARNED] prefix. For comprehensive Lessons Learned archives, we deliver a separate structured CSV export (project, category, lesson, date, owner) for the customer to host in SharePoint, a wiki, or a knowledge base tool.

raidlog.com Change Log entries (change requester, date, status, description, impact) map to Microsoft Project tasks with a Change Request custom field set. However, because Microsoft Project does not have a native change management workflow, we also deliver a separate structured CSV export of all Change Log records for the customer's change control register. Status values (Requested, Approved, Rejected, Implemented) migrate to the custom Status field.

raidlog.com Tags are a taxonomy applied across all RAID record types. We extract the full tag set and map each tag to a Microsoft Project custom text field (e.g., Custom Text1). We apply explicit value mapping during import and deliver a Tag Taxonomy document listing the source tag name and the destination field value for the customer's PMO to reconcile.

raidlog.com Users referenced as Owners on Risks, Actions, Issues, and Decisions map to Microsoft Project Resources. We resolve by email match. Resources without a match go to a reconciliation queue for the customer's admin to provision before record import. Max units and resource calendar availability do not migrate from raidlog.com; these are configured in Microsoft Project during project initialization.

raidlog.com Stakeholder List records have no native Microsoft Project object. We append stakeholder names and roles to the project Resource Notes field and deliver a separate structured CSV export of stakeholder name, role, email, and project for the customer to incorporate into their stakeholder register or SharePoint-based RACI matrix.

raidlog.com has no binary attachment API. We export file reference URLs from the grid UI and flag each reference with the associated RAID record ID. The customer manually re-links supporting documents in Microsoft Project via Insert > Hyperlink or by attaching files to task notes after migration.