Migrate from Priority Matrix to Asana

Priority Matrix Projects map directly to Asana Projects. We extract project name, description, and creation date from the CSV export and create Asana Projects in the destination workspace. We flag any Priority Matrix project that was marked private because Asana Projects do not have a private flag at the object level; we instead recommend the customer use Asana's Guest access controls or a separate workspace for sensitive projects.

Priority Matrix Items are the central migration object and map to Asana Tasks. We extract title, description (body), creation date, modification date, due date, completion status, and assignee. The quadrant label (Do First, Schedule, Delegate, or Eliminate) maps to a custom single-select field that we create in Asana during schema setup. We clear completed status on Tasks during initial migration so the customer can validate before marking complete; a separate completed-task batch is run after sign-off.

Item due dates migrate as Asana Task due dates with the original timezone preserved where available. Items without due dates are flagged as undated during scoping so the destination does not receive null date fields that might break downstream automation. Calendar sync entries that produced duplicate date records in Priority Matrix are deduplicated by Item ID during extraction, keeping the native due date and flagging the calendar link as inactive post-migration.

Item assignees in Priority Matrix are matched by email address against the Asana workspace user directory. Orphaned assignees (email addresses with no corresponding Asana User) are placed in a reconciliation queue for the customer's admin to provision before record import resumes. Tasks without assignees are created in the Asana inbox for manual assignment post-migration.

Priority Matrix Tags migrate as Asana Tags. Tag names are extracted from Items and deduplicated. We create Tags in Asana before Task import so that Tags can be applied during the bulk insert. Tags with more than 100 unique values across the dataset are flagged for the customer to decide whether to collapse into a multi-select custom field or retain as Tags.

Priority Matrix custom fields exist on Items and Projects. We extract all field names and values, then map them to Asana custom fields using type inference (text fields to Asana text, number fields to Asana number, date fields to Asana date). Asana enforces a limit on single-select field options that we check during scoping; Priority Matrix custom fields with more than 50 unique values require the customer to choose between collapsing values or splitting across multiple fields.

File attachments on Priority Matrix Items are exported and re-uploaded to the corresponding Asana Task. We preserve the original filename and note the uploader in the Task description. Attachment counts exceeding 500 files per migration batch are flagged before migration begins because large file re-upload can extend timeline by one to two weeks depending on network throughput and Asana API throttling.

Priority Matrix comments migrate as Asana Task comments. We extract comment text, author email, and timestamp, then create Asana comments linked to the migrated Task. Comment ordering is preserved by posting in chronological sequence. Author emails that do not resolve to an Asana workspace member are replaced with a system note indicating the original author.

Priority Matrix Calendar Sync entries are not recreated as live calendar events in Asana. We convert the calendar-synced due date to a standard Task due date with a flag in the description indicating it was originally calendar-synced. Asana's native calendar integration or Google Calendar two-way sync is recommended as the post-migration replacement for live calendar linkage.

Priority Matrix Templates define pre-populated Item structures within a Project. We export the template schema as a set of draft Tasks in Asana Projects, preserving field structure (custom field names, quadrant label, assignee placeholder) but clearing due dates and completion status. The customer rebuilds the template as an Asana Project Template manually post-migration since template-as-code migration is outside standard scope.

The four quadrants (Do First, Schedule, Delegate, Eliminate) are exported as a custom field value on each migrated Task. During scoping we recommend the customer create a corresponding filtered view in Asana using the custom field as a grouping dimension, which restores the quadrant-portfolio visibility from Priority Matrix. This is a configuration recommendation, not a native Asana feature, and the customer may choose to adjust the field values or view structure post-migration.

Priority Matrix Users are extracted to build the assignee lookup table. We match Users by email against the Asana workspace. Users with no email match in the destination are flagged for manual provisioning. The customer's Asana admin provisions any missing Users before migration resumes; inactive Users are provisioned as inactive Asana members so historical assignment records are preserved.