Migrate from Redbooth to Asana

Redbooth Workspaces map to Asana Teams (Organizational tier) or Projects (Business+ tier). The Workspace name, description, and creation date migrate directly. Member access lists migrate as Asana Team members or Project members. If the customer uses multiple workspaces to simulate departments, we map each to a separate Asana Team. Workspace settings (notification preferences, default views) do not migrate and are reconfigured by the customer post-migration.

Redbooth Task Lists inside a Workspace map to Asana Sections (Business+ tier) or Lists (Standard and below). The task-list ordering within the workspace is preserved via Section or List weight/sort-position fields. If the customer uses task lists to simulate Kanban lanes, we map each list to a separate Section or suggest converting to a Kanban board view at the destination.

Redbooth Tasks map directly to Asana Tasks with title, description (rich text preserved), status (open/completed), due date, start date, priority, and assignee. The task creation timestamp and last-modified timestamp migrate as custom fields if the customer requires historical ordering. Multi-assignee on Redbooth Pro resolves to the primary assignee in Asana, with additional assignees added as collaborators.

Subtask handling depends on the source Redbooth plan tier. On Business plan, Advanced Subtasks migrate as Asana Subtasks with title, assignee, due date, and status preserved. On Pro plan, subtask-like items are flattened into Asana Checklist items within the parent task. We identify the plan tier during discovery and apply the correct transformation. Subtask depth beyond one level is flattened to a single level at the destination because Asana supports only one level of nesting.

Redbooth task-level Comments migrate to Asana Comments on the corresponding task. Author name, timestamp, and comment body transfer directly. Redbooth workspace-level Conversations migrate as Comments on the first task in the conversation thread or as a standalone note if no linked task exists. Rich text formatting in comments is preserved where the destination supports it.

Redbooth standalone Notes (rich-text objects within a workspace not attached to a specific task) map to the Project description or to a dedicated placeholder task with the note content in the description field. We create a placeholder task if the note references multiple tasks or has no clear task linkage, keeping the content accessible and searchable in Asana.

Redbooth Users and Workspace Members map to Asana Users by email address match. The user's display name, email, and role (Admin, External, Participant) migrate. We extract the full member list and flag which workspaces each user has access to so that Asana Team membership can be configured accordingly. Inactive Redbooth users are added to Asana as guests if historical attribution is required on past comments.

Redbooth Tags are workspace-scoped labels applied to tasks. They migrate to Asana Tags at the organization level. Tag names and task-to-tag associations preserve as a lookup table so that tags can be recreated in Asana and re-associated with migrated tasks. If the customer uses tags for categorization across multiple workspaces, we recommend a tag merge strategy during scoping.

Redbooth exports file metadata and URLs only, not actual binary files. We extract every attachment reference (URL, filename, file type, uploaded-by, upload date) and map it to an Asana Attachment record. The Asana Attachment in this case stores the original Redbooth URL as an external link. The customer must re-upload the actual source files post-migration; we deliver a complete attachment inventory listing every file to re-attach with its target task.

Time Tracking entries (Pro+ feature in Redbooth) migrate as duration plus user, task, and date. If the destination Asana plan includes native time tracking, entries map directly to Asana time tracking records. If not, we export a CSV file (task_gid, user_email, duration_seconds, date) for manual import or integration with a third-party time-tracking tool. We preserve the time-entry author and the linked task for audit purposes.

Redbooth's Timeline View stores task start/end dates and dependency links. We extract start_date, due_date, and dependency task IDs from the Redbooth export. Dependencies map to Asana Dependencies (predecessor/successor relationships) if the destination plan supports them (Business+). For complex dependency chains with multiple predecessors or lag time, we flag for manual review at the destination because Redbooth dependency semantics may not map 1:1 to Asana's dependency model.

Redbooth Workspace Templates are not migrated as executable templates. We extract the template structure (workspace name, task list names, task templates with placeholder fields) and document it as a written template specification that the customer's admin uses to recreate the template in Asana. Template cloning is a manual process at the destination.