Migrate from Planio to Asana

Planio Projects map directly to Asana Projects. We export project name, description, status (active/archived), creation date, and custom field values via the Redmine API. Planio project-level custom fields migrate to Asana custom fields on the Project object. We preserve the project identifier for internal reference and remap any project-level permissions to Asana Teams membership during migration.

Planio Issues map to Asana Tasks within the corresponding Project. We map Issue subject to Task name, Issue description to Task notes (HTML preserved as plain text), status to Task completion (Open=incomplete, Closed=completed), priority to a priority custom field or tag, and the Issue ID retained as a reference field for reconciliation. Due dates map from Planio due_date to Asana due_on.

Planio's full parent-child sub-issue graph flattens to Asana Subtasks at the Task level. Asana supports only one level of subtasking, so multi-level Planio hierarchies (grandchild issues) are reconstructed by nesting the deepest child under its direct parent, which then becomes a Subtask of the root Task. We export the full relations table (relations table from Redmine API: blocks, duplicated by, related to, blocked) and reconstruct parent-child links by matching the Planio parent_issue_id to the migrated task GID after bulk import.

Planio custom field definitions (field name, type, possible values) must be pre-created in Asana before any Issue or Task bulk import. We map Planio field types to Asana equivalents: Planio text/date/float/string becomes Asana text; Planio boolean becomes Asana checkbox; Planio list (single-select) becomes Asana dropdown; Planio list (multi-select) becomes Asana multi-select; Planio user-type fields require the assignee custom field in Asana. We flag any Planio version-type fields as text fields in Asana since Asana has no version object equivalent.

Time tracking in Planio is native across all paid tiers. Asana's time tracking is a Premium feature. During scoping, we confirm whether the destination Asana workspace is on Premium; if not, we store time entry hours, activity type, and comments as a structured custom field group on the migrated Task (time_hours__c, time_activity__c, time_notes__c). If Premium is active, we create a time entry linked to the migrated Task. Time entry date maps to the log date, hours to duration.

Planio Wiki pages store rich text with internal Issue and Project cross-references. We export wiki content as structured HTML, remap internal Planio wiki-links to Asana task links where possible, and flag any wiki content that cannot be meaningfully migrated as a link-only reference in the Asana Project Brief. True wiki migration requires the customer to choose a documentation replacement (Asana Docs, Confluence, Google Docs) and import the HTML manually; we do not auto-create wiki-equivalent structures in Asana because Asana has no native wiki object.

Documents and file attachments under Planio Projects and Issues migrate as Asana Attachments linked to the corresponding Task or Project. We export file metadata (filename, size, upload date, uploader) and the binary content, preserving the Planio folder hierarchy as a naming convention. Large attachment sets require chunked transfer with retry on timeout. We do not migrate Planio Documents object (which is a file-container in Redmine) as a distinct object in Asana since Asana has no equivalent document-library concept.

Planio Git and SVN repositories with commit-to-Issue linkages have no equivalent in Asana. We do not migrate repository data. We export the commit-to-issue reference table (commit hash, linked Issue ID, commit message, author, timestamp) as a CSV for the customer's admin to re-establish in their chosen VCS hosting platform (GitHub, GitLab, Bitbucket) and link to Asana tasks via the native GitHub or GitLab integration post-migration. The repository bare content must be transferred separately using git clone --mirror or svn admin dump.

Planio News posts (project announcements with author, timestamp, and body) have no direct Asana equivalent. We export News as structured text records with metadata and note that they are low-priority migration objects. If the customer requires preservation, we can import them as a pinned Task in the Asana Project named 'Project History' or skip them entirely with customer approval.

Planio Forums (threaded discussion boards) have no Asana equivalent. We export forum threads as structured text records with thread hierarchy, author, timestamp, and body. The customer chooses whether to import forum threads as tasks in a 'Forum Archive' project or skip them. We flag Forum as a non-core migration object and note that Asana's task comments are the nearest equivalent for ongoing discussions.

Planio Help Desk Customers are a distinct role that can submit tickets via email without a full user account. Asana has no native help desk role. We export Customer email, name, and ticket submission history and map them to Asana as Guest members of the relevant Project if customer-facing visibility is required. Help Desk ticket submissions migrate as Tasks under a 'Support' or 'Customer Requests' Project, with the original Customer email stored in a custom field.

Planio Users (login, email, name, admin flag) map to Asana Users by email match. We export all active Planio users and provision Asana user invitations during migration. Planio group memberships and project-level role assignments are preserved as a CSV for the customer's admin to re-enter in Asana's Team and member settings, since Asana's role model (organization-level member/guest/admin with project-level team membership) differs structurally from Planio's per-project custom role system.

Planio Kanban boards are a Pro-tier feature derived from Issue status and assignee data, not stored as a separate object. We reconstruct the board state in Asana by mapping Planio Issue status values to Asana Section names and enabling Asana's Board view. The board columns in Asana are driven by a custom field or section; we use the most recent Planio board configuration to define the Section layout in the migrated Project.

Planio's custom roles with granular per-project permissions have no direct Asana equivalent. We export the full role definition matrix (role name, Project association, permission set) as a written inventory document and deliver it to the customer's admin for manual rebuild in Asana's Team and member permission settings. Asana's permission model uses organization roles (Member, Guest, Admin) combined with project-level team membership rather than per-project custom roles.