Migrate from Runrun.it to monday Work Management

Runrun.it Projects map directly to monday.com Boards. Project name, description, start/end dates, and team assignments migrate to Board name, description, and Workspace access settings. The destination Workspace is determined during scoping—typically one Workspace per team or department. We preserve the Project timeline as a Date column on the Board for initial reference and recommend converting to monday.com's Timeline column (Standard tier and above) post-migration.

Runrun.it Tasks map to monday.com Items. Task name, description, estimated hours, actual hours, priority, assignee, and due date migrate to Item name, description (via Text column), and native assignee and date columns. Subtasks in Runrun.it map to Subitems in monday.com (available from Standard tier). The parent-Project to Board relationship is resolved at migration time by matching Project name to Board name.

Runrun.it Kanban stages are configured per Project. Each unique stage name set across all Projects becomes a monday.com Status column with label values matching the Runrun.it stage names. Where multiple Runrun.it Projects share the same stage names (e.g., To Do, In Progress, Done), we configure a single Status column set; where Projects have divergent stage sets, we configure separate Board templates or Status groups per Board and flag the inconsistency during scoping.

Runrun.it Time Entries (date, duration in minutes, notes) migrate to monday.com Time Tracking column entries linked to the corresponding Item. We explicitly round durations to monday.com's decimal hour model (dividing by 60 and rounding to two decimal places) rather than allowing the destination to auto-convert, which can silently alter reported hours. Billable/non-billable flags migrate to a Label column if the monday.com plan supports it; otherwise they are noted for manual tagging post-migration.

Runrun.it documents require a two-step API flow: first POSTing to the document record endpoint with attachable_type and attachable_id, then uploading the file to an Amazon S3 presigned URL. We handle both steps during migration—creating the document record and pushing the file to S3—before associating the file with the migrated Item via the File column. We verify S3 bucket accessibility during scoping and flag any documents that fail S3 upload for manual re-upload post-migration. Document metadata (filename, upload date, uploader) migrates as Item column data.

Runrun.it team members map to monday.com Users. We resolve by email address match. Any Runrun.it User referenced on a Task without a matching monday.com User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and hourly rate fields from Runrun.it migrate to Text columns on the user's monday.com profile for reference.

Runrun.it custom field definitions (field_label, field_type in API) map to monday.com column types: text fields map to Text columns, numeric fields to Number columns, date fields to Date columns, and dropdown fields to Label columns. Not all Runrun.it field types have direct monday.com equivalents—complex conditional fields or third-party integration fields are flagged during scoping for manual column creation post-migration. Custom field values migrate as column values on the corresponding Items.

Runrun.it tags stored in tags_data arrays migrate to monday.com Tags. Tag names preserve exactly; tag color assignments do not carry over since monday.com manages tag colors independently. If the migrated tag count exceeds monday.com's practical display limit (approximately 50 tags per Board), we recommend consolidating low-frequency tags before migration.

Runrun.it comments attached to Tasks migrate as monday.com Updates on the corresponding Items. Comment body, author (resolved to monday.com User by email), and timestamp migrate. Threaded replies nest as replies to the parent Update. If the Runrun.it API returns comments as a nested structure, we preserve the parent-child relationship in the update tree. Note: Runrun.it's API documentation does not explicitly define a Comments endpoint, so we verify comment accessibility during discovery.

Runrun.it attachments (URL-based or file-based via attachable_type and attachable_id) migrate as File column entries on the corresponding Items. URL attachments migrate as Link column values; file attachments follow the same two-step S3 flow as Documents. We verify the attachable_id references resolve correctly to migrated Items before inserting attachment records.

Runrun.it automations and approval workflows do not migrate as code. We deliver a written inventory of every active Runrun.it automation with its trigger, conditions, actions, and a recommended monday.com Automation equivalent (e.g., when Status changes to Done, notify User X). The customer's admin rebuilds these in monday.com's Automations center post-migration. Approval workflows map to monday.com's WorkForms and Status-based routing.

Runrun.it's AI-enabled productivity reports and dashboards have no direct monday.com equivalent. We export Runrun.it report definitions and data snapshots as reference documents. monday.com Dashboards (available from Standard tier) rebuild as Widget boards with chart types matching the original report metrics. We document the source metric, the recommended monday.com Widget type, and the source column mapping for the customer's admin to implement.