Migrate from Viewpath to Microsoft Project

Viewpath Projects map directly to Microsoft Project project files (.mpp for desktop) or Project Online/PWA Enterprise Projects. We extract project name, description, start date, finish date, status, and owner from Viewpath's project-level metadata. Where a Viewpath project was saved as a template, we flag it as such and deliver the template data as a separate reference artifact so the customer's admin can create a Microsoft Project template from it. Projects with orphaned task artifacts (locked tasks from Viewpath's UI glitches) are flagged before migration so the customer can decide whether to import the affected schedule segments or recreate them in Microsoft Project manually.

Viewpath Tasks map to Microsoft Project Task rows. We extract task name, planned start and finish dates, duration, percent complete, and priority. Tasks flagged as locked in Viewpath's UI are explicitly excluded from the import set and reported separately because Microsoft Project does not have an equivalent lock state that prevents editing. The customer's PMO can recreate those task segments in Project after migration. Manual tasks in Viewpath map to Microsoft Project's manual scheduling mode where supported; Project for the web strips manual task support at migration time per Microsoft documentation.

Viewpath supports finish-to-start, start-to-start, finish-to-finish, and start-to-finish dependency types. We map all dependency links to Microsoft Project's dependency model (LinkPredecessor, LinkSuccessor fields). Circular dependency chains detected in Viewpath's data are flagged before import because Microsoft Project handles circular dependencies by breaking the chain silently, which can alter the schedule unexpectedly. We report any circular chains so the customer's project manager can resolve them in the destination before finalizing the schedule.

Viewpath Resources (people allocated to tasks with allocation percentages) map to Microsoft Project Resources. We extract resource name, role, email address, and allocation percentage per task assignment. Where Viewpath used a generic resource pool without individual assignments, we map to a generic Microsoft Project material resource. For Project Online or PWA destinations, resources map to the Enterprise Resource Pool; for Project Desktop destinations, resources are written to the Resource Sheet. Resource max units (% allocation) migrate from Viewpath's allocation percentages. Resource rates do not transfer from Viewpath as Viewpath did not store billing rates as a standard field.

Viewpath's Gantt view is its primary UI, storing column layout, grouping, and collapsed-row preferences as view metadata rather than as a data object. We extract the underlying schedule data but cannot transfer Gantt column customization or grouping settings to Microsoft Project because these are UI preferences stored differently. We deliver a Gantt view snapshot from Viewpath that the customer can use as a reference to manually configure their Microsoft Project Gantt layout. Critical path highlighting from Viewpath transfers as a calculated field set on the project schedule.

Viewpath baseline schedules (saved start/end dates per task for schedule comparison) map to Microsoft Project's Baseline Start and Baseline Finish fields. We extract baseline data per task where Viewpath records show a saved baseline. Not all Microsoft Project tiers expose baseline fields uniformly; Project Plan 1 (entry cloud tier) has limited baseline support compared to Plan 3 and Plan 5. We note the destination tier during scoping and flag any baseline data that cannot be stored in the chosen tier. Multi-baseline tracking (Baseline0 through Baseline10) is preserved as a data artifact if Viewpath stores more than one baseline version.

Viewpath's custom filtered reports are exported as raw data with filter logic documented. Microsoft Project's reporting layer differs significantly: Project Desktop uses built-in visual reports and export to Excel; Project Online/PWA uses Power BI integration for portfolio reporting. We deliver the report data in a format the customer's admin can import into Excel for rebuild, and we document the filter logic (field names, operators, values) so that the admin can recreate the equivalent view in Microsoft Project's reporting tool or in a connected Power BI workspace. Report rebuilding is in scope for the customer's admin team; we do not rebuild reports as code.

Viewpath linked documents via Google Drive OAuth integration, which is no longer valid since Viewpath is closed. We extract each document link reference and attempt to resolve it against the customer's Google Drive. Links that resolve to accessible files are imported as hyperlinks in Microsoft Project Task Notes or as document attachments on the project. Links that are broken or inaccessible (OAuth token revoked or file deleted) are flagged on a Broken Links Report delivered alongside the migration, with the original URL and last-known file name so the customer's admin can reconnect or re-upload the files in SharePoint or Teams for attachment to the migrated project.

Viewpath Users (assigned as task owners and resources) map to Microsoft Project Resources with the user's name and email preserved. For Project Online and PWA destinations, we match Viewpath users to Azure AD accounts by email lookup so that the resource has an Active Directory identity. For Project Desktop destinations, users are added to the Resource Sheet. Any Viewpath user that cannot be matched to a destination identity is held in a reconciliation queue for the customer's admin to provision before final record import.

Viewpath was designed for individual project scheduling and did not have a structured Portfolio or Program object. We do not migrate non-existent data. If the customer needs portfolio-level views in Microsoft Project, we recommend building them post-migration using Project Online's portfolio dashboards or Power BI reports connected to PWA. Any Viewpath data that approximates portfolio-level visibility (multi-project schedule views) is delivered as a reference export for the customer's admin to use when configuring portfolio reporting in Microsoft Project.