Migrate from Viewpath to monday Work Management

Viewpath Projects map to monday.com Boards. The Project name, description, start date, end date, status, and owner assignment transfer to the Board name, description, and admin. We create one Board per Viewpath Project. If a Viewpath Project was saved as a reusable template rather than an active project, we document the template structure for manual board creation in monday.com rather than importing a template that carries no active schedule data.

Viewpath Tasks map to monday.com Items. Task name, planned start and end dates, duration, percent complete, and priority transfer to Item name, Timeline column, and numeric or status columns. We flag Tasks that were flagged as locked in Viewpath's UI and report them separately; locked items cannot be imported as editable records because the lock state has no monday.com equivalent. The customer manually recreates those schedule segments in the destination.

Viewpath's finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependency types map to monday.com's dependency column which natively supports finish-to-start only. For finish-to-start dependencies, we set the monday.com dependency column directly. For non-FS dependency types, we preserve the original dependency type and source-target pair in a custom text column so the customer can reconstruct the logic manually in monday.com. Monday.com's dependency column requires a Pro plan ($19/seat/mo); Standard-plan customers receive the dependency data as a reference export.

Viewpath Resources represent people allocated to tasks with name, role, and allocation percentage. We map these to monday.com People columns on each Item, resolving each resource to the monday.com User by email match. Allocation percentage maps to a numeric column since monday.com People columns do not natively store allocation percentage. We flag any Resource without a matching monday.com User for admin provisioning before the migration finalizes.

Viewpath Users with name, email, and role assignment map to monday.com Workspace Members. We extract the full user list and resolve by email. Any Viewpath User referenced on a Task or Resource without a monday.com Workspace Member account goes to a reconciliation queue for the admin to provision before migration resumes.

Viewpath's Gantt view configuration (column layout, grouping, collapsed rows) is stored as a view preference in Viewpath's proprietary UI and has no monday.com equivalent as a data object. We extract the underlying schedule data (Tasks, Dependencies, Resources) and configure monday.com Boards with Timeline columns as the equivalent scheduling view. The customer recreates the visual grouping and collapsed-row state manually in monday.com's Board view settings.

Viewpath baseline schedules (saved project baselines with per-task baseline start and end dates) map to a structured data export we deliver as a CSV alongside the monday.com migration. Monday.com does not have a native baseline feature, so we cannot import baselines as a live comparison tool. We preserve the original baseline dates and the comparison logic so the customer can manually create baseline-equivalent duplicate timeline records in monday.com if needed for schedule comparison.

Viewpath custom filtered reports store filter logic tied to the platform's UI. We extract the report definitions including all filter conditions, column selections, and grouping logic as a structured document. We rebuild equivalent board views in monday.com using the native Group, Filter, and Sort tools. Dashboard-level report summaries rebuild as monday.com Dashboard widgets. The customer validates the rebuilt views against the extracted report data during the validation window.

Viewpath's primary document attachment mechanism was linking to files stored in Google Drive through Viewpath's embedded viewer. Since Viewpath is closed, the application's OAuth integration with Google Drive is no longer valid. We attempt to resolve each linked document URL and flag any that return a 403 or 404 error. Resolved URLs are preserved as a URL column in monday.com; broken links are reported in a separate inventory so the customer can re-upload or reconnect files in their destination system.

Viewpath had no structured Portfolio or Program object. Organizations that used Viewpath to manage multiple projects across a portfolio used workarounds such as shared Resources or naming conventions rather than a native portfolio view. We document any multi-project patterns found in Viewpath data and recommend a monday.com Workspace structure as the equivalent portfolio container if the customer has multiple related Boards to organize.

Multiple Capterra reviewers documented task-locking glitches in Viewpath's UI where specific tasks became uneditable. We detect these locked records during extraction and flag them explicitly rather than importing the locked state. The locked-task list is delivered as a separate inventory so the customer can manually recreate those schedule segments in monday.com. We do not attempt to preserve the locked state because monday.com has no task-lock equivalent.

Viewpath automations consisted of basic task-level notifications and reminder emails. These do not migrate as executable code because the automation logic is not exported as a structured object from Viewpath. We deliver a written inventory of automations documented from customer-provided screenshots or descriptions, with recommended monday.com automation recipes for each trigger and action. The customer's monday.com admin rebuilds these in the Automation Builder post-migration.