Migrate your Viewpath data

Viewpath's primary container for work. We export all project-level metadata including name, description, start and end dates, status, and owner assignment. Where a project has a saved template, we extract and flag it separately so it can be reapplied at the destination.

Tasks are the core work unit in Viewpath. We extract task name, planned dates, duration, percent complete, and assignment. We flag tasks that were flagged as locked in the source UI to prevent re-importing a locked state that would block editing in the destination.

Viewpath supports finish-to-start, start-to-start, and other dependency types. We map all dependency links and resolve them to the destination system's dependency model. Circular dependency chains discovered during extraction are flagged and reported before import.

Resources in Viewpath represent people allocated to tasks. We extract resource name, role, and allocation percentages. Where a destination uses a different resource schema (e.g., a User-assignee model), we transform the allocation into individual task assignments during import.

Viewpath's Gantt view is its primary UI. Gantt configuration (column layout, grouping, collapsed rows) is stored as a view preference rather than a data object. We extract the underlying schedule data and reconstruct a functional Gantt layout in the destination from the task and dependency data.

Viewpath allows saving project baselines for schedule comparison. We extract baseline start/end dates per task where they exist. Not all destination PM tools support baselines natively, so we either map them to a dedicated baseline field or flag them for manual restoration.

Custom filtered reports are a documented feature. We extract report definitions and their underlying filter logic. Since report formats vary widely across PM platforms, we rebuild equivalent reports in the destination or export the raw data so the customer can reconstruct the report manually.

Viewpath linked documents via Google Drive integration. We extract the link references and attempt to resolve them to the actual files. Where a link is broken or the Google Drive access has been revoked, we flag the orphaned attachment for customer action.

Users are assigned as task owners and resources. We extract the full user list including name, email, and role. User-to-resource mapping is preserved so assignments can be restored in the destination, subject to that platform's user management model.

Viewpath was designed for individual project scheduling rather than portfolio management. It did not have a structured Portfolio or Program object. We do not migrate non-existent data; any portfolio-level rollup must be rebuilt in the destination PMO tool.