Migrate from Viewpath to Trello

Viewpath Projects map to Trello Boards with the project name as the Board title. Project description becomes the Board description field. We create the Board in the destination Workspace and preserve project-level status (active, completed, archived) by mapping it to a Board Label or list name pattern. Projects with sub-projects in Viewpath map to multiple Boards or, if a hierarchical structure is preferred, to a single Board with Lists representing sub-project scopes. Trello Board limits apply at the Workspace level: Free Workspace allows unlimited Boards, Standard allows unlimited, and Premium allows unlimited with advanced features.

Viewpath Tasks map to Trello Cards. Task name becomes the Card title, description becomes the Card description field, planned start and end dates map to Card due dates, duration in days is stored as a custom field, and percent complete is stored as a custom field or reflected in a Checklist with a completion percentage indicator. Tasks flagged as locked in Viewpath are explicitly identified and excluded from import; we report the locked task list so the customer can recreate those schedule segments manually in Trello. Trello board-level card limits are 5,000 open and 2,000,000 total per Board.

Viewpath supports finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependency types with predecessor-successor chains and circular dependency detection. Trello has no native dependency model. We resolve each Viewpath dependency link and document it as a structured dependency map (predecessor Card ID to successor Card ID with dependency type) that the customer can use to reconstruct the chain using Butler rules or the native Card linking feature. Where a predecessor-successor relationship is critical for scheduling, we create a checklist on the successor Card listing the predecessor Card name as a manual dependency reminder. Circular dependency chains in Viewpath are flagged and excluded.

Viewpath Resources represent people allocated to tasks with name, role, and allocation percentage. We extract Resources and map them to Trello Members by email or name match against the destination Trello workspace. Role information and allocation percentage are stored as custom fields on each Card rather than as a native capacity-planning construct, since Trello does not have a resource management module. The allocation percentage is informational rather than enforced.

Viewpath's Gantt chart is the primary UI, with column layout, grouping, and collapsed-row preferences stored as view metadata. Trello's native view is Kanban. For teams needing a timeline view, we install and configure the Trello Calendar Power-Up and, on Premium plans, the native Timeline view. The underlying schedule data (start dates, end dates, durations) is preserved as Card custom fields so that the Timeline view renders correctly. Gantt-specific features like drag-to-reschedule that preserve downstream dependencies are not available in Trello and are documented as a gap.

Viewpath baselines store the original planned start and end dates per task for schedule comparison. Trello has no baseline field. We extract baseline dates where they exist and store them as two custom date fields on each Card: baseline_start__c and baseline_end__c. The customer can use these for manual schedule variance analysis in Trello or export them for comparison in a spreadsheet. Not all destination Trello workspaces have custom fields enabled; on Free workspaces, baseline dates are exported as a CSV artifact for the customer to reference separately.

Viewpath custom filtered reports are named report definitions with saved filter logic scoped to a project. We extract the report definition including filter conditions, sort order, and column layout as a structured JSON artifact. We rebuild the equivalent report data in CSV format at migration time. Since Trello has no saved report definitions and card filtering is session-only, we provide a written inventory of every Viewpath report with its filter logic documented so the customer can apply the same filters manually in Trello or configure Butler rules to replicate the alert conditions.

Viewpath linked documents via Google Drive integration that is now invalid since the platform is closed. We extract the full list of Google Drive attachment URLs and attempt to resolve each one. Where the link is accessible (the file is still hosted in Google Drive independently of Viewpath), we reconnect it as a Card attachment. Where the link is broken or the file has been deleted or access revoked, we flag it in a broken link report with the Card name, the original URL, and the last-known file name. The customer uses this report to re-upload or re-link the files manually in Trello.

Viewpath Users with names, email addresses, and roles are extracted and mapped to Trello workspace Members. We match by email. Any Viewpath User without a matching Trello account is added to a Member resolution report for the customer's admin to provision before Card assignment migration, or we invite them as a Board Member during migration. Active versus inactive status from Viewpath does not map to Trello Member status directly; all provisioned Members are invited with their current access level.

Viewpath did not have a structured Portfolio or Program object; it was designed for individual project scheduling. No equivalent data exists to migrate. If the customer has portfolio-level reporting requirements in Trello, we recommend using Trello Workspace Tables or a third-party portfolio dashboard Power-Up as a post-migration configuration. This is documented as an optional upgrade path, not a migration gap.

Viewpath Tasks that were sub-tasks of a parent Task map to Trello Checklist items on the parent Card. We resolve the parent-child hierarchy from Viewpath and attach each sub-task as a named Checklist item with its own due date and assignment stored as a checklist item annotation. Sub-task percent-complete is not natively tracked on Trello Checklist items, so we add it as a note annotation if present in Viewpath. If the sub-task has further children (grandchildren), we flatten the hierarchy and attach each as a separate Checklist item with a naming prefix indicating the depth level.

Viewpath Notes attached to Tasks migrate as Trello Card Comments. The original note content and timestamp are preserved. If the Note was a task description rather than an attached comment, it merges into the Card description field. Notes attached to Projects migrate as Board-level descriptions or as the first Card Comment on a designated informational Card.