Migrate your raidlog.com data

Projects are the top-level container for all RAID records in RAIDLOG. We export the full project hierarchy including metadata, dates, and owner assignment via the Projects API and recreate them 1:1 at the destination.

Risks has a dedicated API endpoint with standard fields: ID, title, description, probability, impact, status, owner, and due date. We map these directly to the destination's risk object or a custom equivalent.

Action Items use a dedicated API and include standard fields for assignee, due date, priority, and status. We preserve the action-to-risk or action-to-project linkage as a reference property during migration.

Issues have their own API endpoint and track description, severity, status, owner, and resolution date. We map these to the destination's issue object or equivalent ticket-like structure.

Decisions are tracked as distinct records with owner, date made, date due, status, and rationale fields via the Decisions API. We preserve decision context including linked project and any related dependencies.

Lessons Learned are a separate log type in RAIDLOG but are commonly implemented as tags or custom fields in other PM tools. We extract Lessons Learned as a tagged property on the relevant project or risk record and flag them for explicit review during import scoping.

Dependencies log inter-item relationships (e.g., Risk A blocks Action B). We reconstruct these as linked-record references in the destination, noting that most general-purpose PM tools do not have a native dependency registry and require a custom field or tag to preserve the relationship.

Change Log entries capture project change requests with requester, date, status, and description. We treat each change log row as a discrete record and map it to the destination's change management object or as a tagged task/note on the affected project.

Tags are managed via a dedicated Tags API in RAIDLOG and can be applied to any RAID record. We extract the full tag taxonomy and apply explicit value mapping during import since tag naming conventions differ between platforms.

Users are referenced by ID across Risks, Actions, Issues, and Decisions as the assigned Owner. We map RAIDLOG user IDs to destination user records and flag any orphaned assignments where the owner account does not exist at the destination.

Free and Core plans have a single workspace; Enterprise plans support Private Workspaces for team isolation. We map workspace structure into the destination's workspace, project-group, or org-level hierarchy and flag any Private Workspace access rules that need translation.

RAIDLOG's grid UI supports linking to external files but does not expose a native file attachment API. We do not migrate binary attachments directly; instead we export the file reference URL and flag it for manual relinking at the destination.

The Contact and Stakeholder List is a supplementary RAID log component. We export it as a distinct record set and map it to the destination's contact, team, or stakeholder object.