Migrate from Viewpath to Asana

Viewpath Projects map directly to Asana Projects. We extract project name, description, start date, end date, status, and owner assignment. Viewpath project templates (saved baseline project structures) are documented as Asana project templates the customer can recreate in the destination. Status mapping: Viewpath Active/On Hold/Completed maps to Asana's project status states.

Viewpath Tasks map to Asana Tasks. Task name, planned dates, duration, percent complete, and assignee migrate directly. Start Date on Asana Tasks requires Asana Starter or above; Starter-tier destinations receive the planned start date in a custom field project_start_date__c rather than the native Start Date field. Tasks flagged as locked in Viewpath are excluded from import and listed in a reconciliation report for manual recreation.

Viewpath finish-to-start, start-to-start, and other dependency types map to Asana Dependencies in the Timeline view. We validate the full dependency chain post-import because Asana community reports show that dependency date propagation can produce incorrect dates in complex chains, particularly with tasks sharing the same initial date or multiple predecessors. Circular dependency chains are detected and flagged before import to prevent Asana from accepting them.

Viewpath Resources (people allocated to tasks with allocation percentages) map to Asana User assignments. The resource name and email resolve to an Asana User by email match. Allocation percentage (e.g., 50% on a task) migrates as a custom numeric field resource_allocation__c on the Task because Asana's native model is binary assignment (User is or is not assigned) rather than percentage-based allocation. Customers on Asana Business can use Workload view for capacity visualization using the allocation field.

Viewpath baselines (saved start/end dates per task for schedule comparison) cannot map to a native Asana object because Asana has no baseline feature. We store baseline start and end dates as custom fields baseline_start__c and baseline_end__c on the Task. The customer can compare current planned dates against these fields manually or via a report. Baseline schedule variance is not automatically calculated; we document the comparison logic for the customer.

Viewpath's Gantt view is its primary UI, storing column layout, grouping, and collapsed-row state as view preferences. Asana's Timeline view replicates the schedule visualization but is a view, not a data object. We extract the underlying schedule data (tasks, dates, dependencies) and build the Asana Timeline accordingly. Column layout preferences do not transfer; the customer reorders columns in the Asana Timeline customize panel.

Viewpath custom filtered reports with their filter logic are extracted as data definitions. We export the report name, filter conditions, and the underlying data. Asana's reporting is project-level and portfolio-level rather than a report-builder feature. We document each Viewpath report definition so the customer's admin can rebuild equivalent filters in Asana using project views, custom fields, and Portfolio dashboards.

Viewpath attachments linked via Google Drive are extracted as URL references. Viewpath's OAuth integration with Google is no longer valid since the platform is closed. We attempt to resolve each linked document; where the link is inaccessible, we flag it in a broken-links report with the original URL and file name. The customer manually re-uploads inaccessible files to Asana. Asana enforces a 100MB per-file attachment limit via API; files exceeding this are flagged and skipped.

Viewpath Users (name, email, role) are extracted and matched to Asana Users by email address. Any Viewpath user without a matching Asana User is held in a provisioning queue. The customer's admin creates the missing Asana User accounts before the migration proceeds because OwnerId references are required on imported tasks.

Viewpath did not have a structured Portfolio or Program object; it was designed for individual project scheduling. No portfolio data exists to migrate. Asana Portfolio objects are created post-migration by the customer's admin adding projects to Portfolios based on organizational structure.

Tasks flagged as locked in Viewpath's UI are not imported into Asana. These locked tasks represent Viewpath's documented UI glitch where certain tasks become uneditable. We extract the task name, planned dates, and assignments and list them in a locked_tasks_report.csv so the customer can manually recreate those schedule segments in Asana. This prevents the locked state from transferring to a system where it has no equivalent flag.

Viewpath's custom filtered reports stored filter logic (e.g., tasks where status equals Open and assignee equals X) that is proprietary to the platform. We export the filter conditions as a written report definition. The customer's admin rebuilds these filters in Asana using a combination of custom fields, Sections, and project-level filtering. This is documented work, not automated migration.