Migrate your Runrun.it data
Time-tracking-first project and task management tool for service companies, with Kanban workflows, AI reports, and an emphasis on managing hours worked per project.
In its favor
Why people choose Runrun.it
The signal that keeps Runrun.it on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Runrun.it's task and project organization features are its most cited strength, with 20 mentions across G2 reviews highlighting improved workflow management and tracking efficiency.
The platform is praised for its ease of use, with 19 reviewers describing it as practical for organizing work hours and managing team tasks efficiently.
Kanban-based task management streamlines work once teams adapt to the model, with users noting processes become more fluid after the initial learning curve.
Built-in time tracking integrated directly into tasks and projects appeals to service companies that bill by the hour or need to monitor project costs closely.
AI-enabled reports and dashboards give managers visibility into team productivity and project costs without exporting data to separate BI tools.
Users report glitches including unresponsive features and visual bugs that disrupt daily efficiency, appearing across multiple review platforms.
The lack of a native mobile application makes it difficult for remote workers to access and update tasks outside of desktop browsers.
Creating tasks and marking them complete requires excessive clicking, with users noting the overhead consumes time better spent on actual work.
Structural flexibility is limited once the platform is configured, with users unable to keep part of a team on a free plan while others upgrade.
Time tracking features have known issues including accuracy problems that frustrate teams relying on Runrun.it for billable hour reporting.
Reasons to switch
Why people leave Runrun.it
The recurring reasons buyers give for replacing Runrun.it. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Runrun.it fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Runrun.it pricing overview
Runrun.it offers a free tier for small teams with core task and time tracking features. Paid tiers unlock AI reports, advanced integrations, and enterprise support, though specific pricing is not publicly disclosed and requires direct inquiry.
Free
Tier 1 of 3
Free
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Runrun.it's schedule — see our quote-based pricing →
What gets migrated
Runrun.it object support
Object-by-object support for Runrun.it migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in Runrun.it, grouping related Tasks with shared timelines, budgets, and team assignments. We migrate Projects with their name, description, start/end dates, and status intact.
Tasks
Fully supportedTasks are the core work unit, assigned to Users with estimated hours, actual hours tracked, priority, and due dates. We preserve task status, assignee, and the relationship to parent Projects during migration.
Time Entries
Mapping requiredTime entries track hours logged against Tasks with date, duration, and optional descriptions. Some platforms store time entries as a separate object while others embed them in Tasks—we map accordingly and flag currency mismatches.
Documents
Mapping requiredDocuments are uploaded via a two-step API flow: first creating a record, then pushing the file to Amazon S3. We preserve the attachable_type and attachable_id linking documents back to their parent Tasks. Large file handling and S3 bucket configuration must be coordinated.
Users/Members
Fully supportedUsers are team members with roles, email addresses, and hourly rates. We map Users to the destination platform's equivalent user object, preserving assignments on Tasks and access permissions where applicable.
Kanban Stages
Mapping requiredRunrun.it uses Kanban-style workflow stages for Tasks. Stage names are configurable per Project. We map stage names to the destination's pipeline or workflow statuses, flagging any mismatches in stage count or naming conventions.
Tags
Mapping requiredTags are used to label Tasks with metadata. The API exposes tags_data as an array. We migrate tags as label or tag objects, noting that destination platforms vary in how many tags per record they support.
Custom Fields
Mapping requiredRunrun.it supports custom fields on Tasks with field_label stored in the API. We migrate custom field definitions and values, noting that not all destination platforms support the same field types or validation rules.
Comments
Mapping requiredIf Comments are present in the Runrun.it instance, we migrate them as threaded notes attached to their parent Tasks. The API documentation does not explicitly define a Comments endpoint, so we verify availability during discovery.
Attachments
Mapping requiredAttachments link external files or URLs to Tasks. The attachable_type field indicates what object the attachment belongs to. We migrate attachment URLs and metadata, preserving the relationship to parent Tasks.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in Runrun.it, grouping related Tasks with shared timelines, budgets, and team assignments. We migrate Projects with their name, description, start/end dates, and status intact. |
| Tasks | Fully supported | Tasks are the core work unit, assigned to Users with estimated hours, actual hours tracked, priority, and due dates. We preserve task status, assignee, and the relationship to parent Projects during migration. |
| Time Entries | Mapping required | Time entries track hours logged against Tasks with date, duration, and optional descriptions. Some platforms store time entries as a separate object while others embed them in Tasks—we map accordingly and flag currency mismatches. |
| Documents | Mapping required | Documents are uploaded via a two-step API flow: first creating a record, then pushing the file to Amazon S3. We preserve the attachable_type and attachable_id linking documents back to their parent Tasks. Large file handling and S3 bucket configuration must be coordinated. |
| Users/Members | Fully supported | Users are team members with roles, email addresses, and hourly rates. We map Users to the destination platform's equivalent user object, preserving assignments on Tasks and access permissions where applicable. |
| Kanban Stages | Mapping required | Runrun.it uses Kanban-style workflow stages for Tasks. Stage names are configurable per Project. We map stage names to the destination's pipeline or workflow statuses, flagging any mismatches in stage count or naming conventions. |
| Tags | Mapping required | Tags are used to label Tasks with metadata. The API exposes tags_data as an array. We migrate tags as label or tag objects, noting that destination platforms vary in how many tags per record they support. |
| Custom Fields | Mapping required | Runrun.it supports custom fields on Tasks with field_label stored in the API. We migrate custom field definitions and values, noting that not all destination platforms support the same field types or validation rules. |
| Comments | Mapping required | If Comments are present in the Runrun.it instance, we migrate them as threaded notes attached to their parent Tasks. The API documentation does not explicitly define a Comments endpoint, so we verify availability during discovery. |
| Attachments | Mapping required | Attachments link external files or URLs to Tasks. The attachable_type field indicates what object the attachment belongs to. We migrate attachment URLs and metadata, preserving the relationship to parent Tasks. |
Gotchas
What to watch for in Runrun.it migrations
Issues we've hit on past Runrun.it migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Two-step document upload requires S3 coordination
No documented API rate limits
No mobile app means no mobile-only data
Time tracking data requires currency and rounding alignment
| Severity | Issue |
|---|---|
| High | Two-step document upload requires S3 coordination |
| Medium | No documented API rate limits |
| Medium | No mobile app means no mobile-only data |
| Low | Time tracking data requires currency and rounding alignment |
Leaving Runrun.it?
Where Runrun.it customers move next
5 destinations Runrun.it can migrate to.
How a Runrun.it migration works
Four steps, Runrun.it-specific
Connect
Not publicly documented in available API docs into Runrun.it. Scopes limited to read-only on the data we move.
Map
We translate Runrun.it-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Runrun.it quirks before production.
Migrate
Full migration with Runrun.it rate-limit handling. Rollback available throughout.
FAQ
Runrun.it migration FAQ
Answers to the questions buyers ask most during Runrun.it migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Runrun.it migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate Runrun.it.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Runrun.it setup and destination — written quote back within a business day.