Migrate from Runrun.it to Trello

Runrun.it Projects map to Trello Boards. Project name becomes Board name; Project description migrates to the Board description field. Start and end dates have no native Trello Board equivalent and are noted as requiring Custom Fields Power-Up configuration post-migration. Team assignments on Projects map to Workspace Members with Board-level invite.

Runrun.it Tasks map to Trello Cards within the target Board. Task name becomes Card title; description migrates to Card description. Estimated hours, actual hours, priority, and due date map to Card fields, though due dates require Trello's native Due Date feature and the hour fields require Custom Fields Power-Up. Assignee resolves to a Workspace Member by email match.

Runrun.it Time Entries present the primary structural gap. Trello has no native time-tracking object. We migrate time entries as Number-type Custom Fields (hours or decimal duration) on the parent Card, or as structured Checklist items with duration in the item name. The customer chooses the strategy during scoping. Decimal vs minute rounding is handled explicitly to prevent silent precision loss. Hourly rates from Runrun.it do not migrate; a separate billing integration plan is recommended.

Runrun.it's configurable Kanban stages per Project map directly to Trello Lists within each Board. Stage names are preserved verbatim. If Runrun.it has more stages than the destination Board will reasonably support, we flag stage consolidation options and let the customer decide before migration begins.

Runrun.it uses a two-step document upload: first POSTing to the Tasks documents endpoint to create the record, then pushing the file to an Amazon S3 presigned URL. We handle both steps during migration: retrieve the file from S3 and re-upload it directly to the Trello Card as a native attachment. This ensures attachments arrive as working links rather than broken reference records. We verify S3 bucket accessibility during discovery.

Runrun.it tags stored in tags_data array map to Trello Labels. Label names migrate verbatim. Trello limits label color to one of ten preset colors; Runrun.it does not enforce color on tags, so we assign colors sequentially. Some Runrun.it instances use tags for multi-dimensional classification (status plus category plus priority); we flatten these into label sets and note where multiple tag purposes may need to split into separate label groups.

Runrun.it custom fields on Tasks map to Trello Custom Fields via the Custom Fields Power-Up. Text, number, date, and dropdown types map directly. Trello Custom Fields supports fewer types than Runrun.it; unsupported types (such as complex formula fields or user-reference fields) are flagged and either mapped to Text or noted as requiring post-migration redesign. Custom Fields Power-Up must be installed on each Board before migration.

Runrun.it Users map to Trello Workspace Members. We match by email address. Any Runrun.it User without a matching Trello Workspace Member is held in a reconciliation queue for the customer's admin to provision before Card import resumes. Roles and hourly rates from Runrun.it do not map to Trello equivalents; these require manual configuration post-migration.

Runrun.it Comments attached to Tasks migrate as Card Comments in Trello. The API documentation does not explicitly define a Comments endpoint in Runrun.it, so we verify comment accessibility during discovery before committing this mapping. Comment timestamps and author attribution migrate. Rich text formatting converts to plain text if the original formatting is not compatible.

Runrun.it Attachments linked to Tasks via attachable_type and attachable_id migrate to Card Attachments. We download the referenced file and upload it to the target Card. External URL attachments migrate as link attachments. Attachment metadata (created by, created at, modified by, modified at) is preserved as Trello does not natively store this, but the customer may request a supplemental CSV export for audit.

If Runrun.it Tasks have a subtask or checklist structure, these map to Trello Card Checklists. Checklist item names migrate verbatim. Checklist completion status maps to the checked state in Trello. Runrun.it does not have native subtasks; if the customer has been using a workaround (e.g., related Tasks), we flag these during discovery and discuss whether to flatten or preserve hierarchy.

Runrun.it AI productivity reports and dashboards do not have a Trello equivalent. We export screenshots and PDFs of key reports during discovery as reference artifacts. The AI report data (team productivity metrics, project cost visibility, billable hour summaries) cannot be reconstructed in Trello without a dedicated BI Power-Up or external tool. We deliver a written report inventory noting which metrics the customer should plan to reproduce manually or via a connected analytics tool.