Migrate from Runrun.it to Asana

Runrun.it Projects map to Asana Projects with name, description, start date, and end date preserved. We create each Project in Asana before any Tasks are imported so that the Project membership and section structure are in place. If Runrun.it Projects have shared budgets or custom cost fields, these become Asana custom fields (number or currency type). Multi-workspace Runrun.it instances map to multiple Asana Teams or a single Asana Organization with Projects distributed by department.

Runrun.it Tasks map to Asana Tasks with title, description, assignee, due date, start date (requires Asana Premium), priority, and estimated hours preserved. Subtasks in Runrun.it map to Asana Subtasks nested under the parent Task. We map task priority (low, medium, high, urgent) to Asana custom field dropdown or Notes prefix so the priority context is visible without opening the task detail.

If the destination Asana workspace is on Premium or above, we push Runrun.it time entries to Asana's native time tracking fields (start time, end time, duration). On Standard tier, time entries migrate as Asana custom fields (text or number) holding the duration value in decimal hours. Runrun.it's billable hour flag becomes an Asana checkbox custom field. We round durations explicitly to avoid silent conversion drift between minute-based and decimal-based tracking.

Runrun.it Kanban stages (To Do, In Progress, Review, Done, or custom names) map to Asana Sections within each Project. We extract the stage names from Runrun.it's per-Project stage configuration, create matching Sections in Asana, and assign Tasks to their corresponding Section during import. If multiple Runrun.it Projects share stage names, we preserve the per-Project stage configuration in an Asana custom field for audit.

Runrun.it documents require a two-step migration: first creating the task attachment record via POST /api/v1.0/tasks/:task_id/documents, then pushing the file to the Amazon S3 presigned URL before associating it with the Task. We handle both steps and verify the S3 bucket is accessible during scoping. Asana enforces a 100MB per-file ceiling during API import; any file exceeding this threshold is flagged and excluded from the import with a record in the reconciliation report.

Runrun.it team members (email, name, role, hourly rate) map to Asana Users by email address match. We create a user mapping table during discovery. Any Runrun.it Member without a matching Asana User goes to a reconciliation queue for the customer's admin to provision the account before record import resumes. Hourly rate becomes an Asana number custom field on the User profile.

Runrun.it tags_data arrays migrate to Asana Labels. We preserve the tag name and note that Asana Labels are scoped per Project by default but can be made organization-wide. The customer chooses label scope during scoping. If Runrun.it has more tags per Task than Asana supports in a single field (16 labels per Task), we prioritize the most-used tags and flag the remainder.

Runrun.it custom fields on Tasks (field_label and field_value) map to Asana custom fields of the closest matching type: text to text, number to number, date to date, dropdown to enum. Some Runrun.it custom field types (e.g., formula fields, relational fields) have no direct Asana equivalent and are skipped with a note in the migration inventory. We pre-create the Asana custom field definitions before any Task data is imported.

Runrun.it comments attached to Tasks migrate as Asana Task comments. The comment body, author (resolved to Asana User by email), and timestamp preserve. If Runrun.it comments include @mentions, we convert the mention format to Asana's @mention syntax. Threaded comments in Runrun.it become flat comments in Asana with a visual indicator noting the original thread depth.

External URL attachments in Runrun.it (attachable_type = external link) migrate to Asana URL attachments on the corresponding Task. We preserve the attachment title and URL. If the URL points to a resource that requires authentication or is a Runrun.it-internal link, we flag it for the customer to update post-migration.

Runrun.it custom templates define pre-populated Task structures and Kanban stage configurations per Project type. We document every custom template with its Task structure, stage names, default custom field values, and assignee rules in a written inventory. Asana does not have a direct template migration path; the customer uses the inventory to rebuild templates in Asana via the Project-from-Template feature.

Runrun.it workflow rules (auto-assignment, status changes, notification triggers) do not migrate as code. We deliver a written inventory of every active Runrun.it workflow with its trigger conditions, actions, and the recommended Asana Rules or Workflow Builder equivalent. The customer's admin rebuilds automations post-migration using the inventory as a checklist.