Migrate from Project Insight to Asana

Project Insight Projects map directly to Asana Projects. We export via the project-level report, extracting project name, status, start date, due date, description, and portfolio assignment. In Asana, we create the project with the same name, set the start and due dates, and apply the status mapping (Active maps to On Track, On Hold maps to On Hold, Completed maps to Complete). Portfolio groupings from Project Insight become Asana Portfolios if the destination is on Advanced tier ($24.99/user/mo) or project Sections grouped by team if Starter.

Project Insight Tasks export via the task-level report with parent-child relationships preserved through a flattened indent structure or path field. We reconstruct the WBS hierarchy in Asana using subtasks and the parent task ID. Dependencies (predecessor-successor relationships) from Project Insight's dependency report map to Asana's dependency feature, noting that Asana dependencies are Finish-to-Start only — any Lead/Lag Day constraints from Project Insight require manual reapplication as dependency offsets in Asana after migration.

Project Insight Resources (people, roles, availability, and allocation percentage) map to Asana Members. We export the resource management report and map each resource name to an Asana user by email match. Role-based placeholders (e.g., Developer, Project Manager) that have no corresponding Asana user are held in a reconciliation queue for the customer's admin to provision before task assignment migration. Allocation percentages are noted in a custom field for Workload view reconstruction in Asana Advanced.

Project Insight custom fields (Pro plan gated) export in the same row as their parent Project or Task. We pre-create matching custom field definitions in Asana before import, mapping Project Insight field types (text, number, date, dropdown) to their Asana equivalents (Text, Number, Date, Enum). If the source is on the Free tier, we confirm during scoping that no custom field definitions exist and document this gap in the migration scope.

Project Insight time entries export via the time tracking report, linked to parent Project and Task with hours, date, and resource attribution. Time entries migrate to Asana's native time tracking if the destination is on Asana Advanced ($24.99/user/mo). If the destination is Starter, we create a custom time tracking setup using a Time Log custom field on tasks and note that native timer functionality requires an upgrade. We flag any time entries that reference a resource not yet provisioned in Asana for admin resolution.

Project Insight constraint types (ASAP, Finish No Earlier Than, Finish No Later Than, Start No Earlier Than, Start No Later Than) export as a text field on the task record. We carry the constraint type as a custom text field in Asana (constraint_type__c) for each task. We note in the migration deliverable which tasks have hard deadline constraints (Finish No Later Than) that require the customer's project scheduler to review and reapply scheduling logic in Asana's dependency chain post-import.

Project Insight portfolios and program groupings export as a portfolio-to-project association table. If the destination Asana workspace is on Advanced tier, we map these groupings to Asana Portfolios with project-level status roll-up. If Starter, we map portfolio groupings to project Sections and use a naming convention that preserves the original portfolio name. The customer chooses the approach during scoping based on their Asana tier.

Project Insight predecessor-successor relationships export via the dependency report. We map these to Asana dependencies using the Asana Dependencies API. We flag any Finish-to-Start with Lag, Start-to-Start, or Start-to-Finish constraint types that cannot be expressed in Asana's Finish-to-Start-only dependency model, and document each for manual adjustment post-migration.

Project Insight file attachments stored within the application are not included in the report export. We do not migrate binary attachments directly. We recommend a parallel document migration: download files from Project Insight via direct access and upload to Asana using the Attach from Google Drive, Dropbox, or direct file upload. We can coordinate sequencing so that record migration and file migration complete at the same time and file links can be restored alongside the record migration.

Project Insight's configurable reports are not a data object but a configuration. We document every active custom report definition (name, filters, columns, grouping) in a written report inventory. The customer's admin uses this inventory to rebuild equivalent views in Asana's Dashboard, Timeline, and Portfolio reporting features. This deliverable is included in the standard migration scope as a written document, not an automated migration.

Project Insight automation rules and workflow triggers do not migrate as code. We deliver a written inventory of every active automation rule in the source workspace, documenting its trigger condition, actions, and any dependencies on custom fields or constraint types. The customer's admin uses this inventory to rebuild equivalent automations in Asana's Rules and Workflow Builder. We do not provide post-migration automation rebuild as standard scope.

Project Insight's project health indicators and status flags (RAG status, health score, budget variance) export as project-level fields in the report export. We map these to Asana's project status update feature and custom fields. Projects that were On Hold in Project Insight are set to At Risk or On Hold in Asana. Budget and financial fields that cannot map directly become custom number fields and are flagged for manual review.