Migrate from Runrun.it to Microsoft Project

Runrun.it Projects map to Microsoft Project (.mpp) files or Project Online project sites. We preserve project name, description, planned start date, and planned end date as Project Summary fields. If the Runrun.it project uses multiple Kanban stages, we create a summary task per stage in the destination to preserve the workflow structure as an outline grouping rather than a visual board.

Runrun.it Tasks map to Microsoft Project tasks with Name, Start, Finish, Duration, and Priority preserved. Task status (Open, Completed) maps to Percent Complete (0% vs 100%). Due dates become Finish dates. We flag any Runrun.it tasks that have multiple assignees and generate multiple task rows in Microsoft Project, one per assignee, because MSP assigns a single resource per assignment row. Tasks without start or finish dates are set to Manually Scheduled with a note for the PM to establish the timeline post-migration.

Runrun.it time entries are separate records linked to a Task by attachable_id. We aggregate all time entries per Task and map the sum to the Microsoft Project Work field if the task has no actual progress, or to Actual Work if the task is marked complete. Duration is recalculated from Work divided by the assigned resource's Max Units and Hours Per Day setting. We handle decimal-to-minute rounding explicitly rather than allowing the destination to auto-convert, which can silently change reported hours. Time-entry currency fields in Runrun.it do not map to any native Microsoft Project field and are flagged for the PM to record in a custom field.

Runrun.it Kanban stages are configurable per Project. We map each distinct stage name to a Microsoft Project summary task that acts as a section header in the outline view. Tasks within the summary inherit the grouping for filtering and reporting in Microsoft Project. If the destination is Project Online or Project for the Web, stages become custom field values (Text1 or Flag fields) applied to each task for board-view grouping.

Runrun.it team members map to Microsoft Project Resources with Name, Initials, Type (Material or Work), and Max Units. Hourly rates from Runrun.it transfer to Standard Rate on the Resource sheet. Resources are created before any task assignment so that the Owner-to-Resource lookup is satisfied at the moment of assignment migration. If a Runrun.it user has a @runrun.it email with no equivalent in the destination Microsoft 365 tenant, the resource is created with a placeholder email and flagged for the admin to update post-migration.

Runrun.it documents are uploaded via a two-step flow: POSTing to /api/v1.0/tasks/:task_id/documents creates a record, then the file is pushed to an Amazon S3 presigned URL. We execute both steps and preserve the S3 URL as a hyperlink attached to the corresponding Microsoft Project task. If the S3 bucket is no longer accessible, we flag the document as a broken link in the migration report and note which tasks are affected. Native file attachments to Microsoft Project tasks are not supported via the web API; hyperlinks are the standard approach for this migration path.

Runrun.it Attachments with external URLs (attachable_type = Task) migrate as hyperlinks to the Microsoft Project task's Hyperlink fields (Hyperlink, Hyperlink Address, Hyperlink SubAddress). The attachment description becomes the hyperlink label.

Runrun.it tags stored in tags_data as an array of label strings migrate to a Microsoft Project custom Text field (Text1 or Text2 depending on field availability in the destination tier). We join multiple tags with commas as the delimiter. Tag limits in Microsoft Project are set by the field type; Text fields support up to 512 characters which covers most multi-tag scenarios.

Runrun.it custom fields with field_label and field_type map to equivalent Microsoft Project custom fields by type. Text labels become Text fields; numeric values become Number fields; date values become Date fields. We pre-create the custom field definitions in the destination before record migration begins. Note that Project Plan 1 supports limited custom field types compared to Project Plan 3 and Project Online; we verify the destination tier during scoping and flag any unsupported field types for manual handling.

Runrun.it Comments attached to Tasks migrate to the Microsoft Project task Notes field as plain text. We preserve the comment body, author name (from the User mapping), and timestamp as a formatted header line. Threaded replies are appended sequentially. The Notes field in Microsoft Project supports up to 32,000 characters which covers most comment migration scenarios.