Example Migration

This page provides a non-technical, side-by-side view of an end-to-end Project Online → Altus migration. Use it when discussing scope and outcomes with customers.

For the procedural steps, see Migration Process. For field-level mappings, see Migration Reference.

Overview

The Altus migration covers:

• Migration of Projects
• Migration of Resources
• Migration of Lookup tables (flat, hierarchical, multi-select)
• Migration of Schedules (with all 11 baselines)
• Migration of Resource Cost Rates
• Migration of SharePoint list items (Risks, Issues, custom lists)
• Migration of Documents

Project Online

Lookup tables

Three permutations of lookup tables can be migrated.

Flat lookup tables

A lookup table with no hierarchy.

• Project Online — values added in PWA Settings > Lookup table; users select a value from a control on the Project or Resource form.

• Altus — equivalent values held in a custom Dataverse table created in your Solution Layer; users select via a lookup control on the corresponding Altus form.

Hierarchical lookup tables

A lookup table with a parent/child tree structure.

• Project Online — tree of values defined in PWA Settings; users navigate the tree to pick a value.

• Altus — represented as a self-referential Dataverse table (Parent lookup with the Hierarchical flag enabled). Levels are shown using a . separator in the lookup picker (Dataverse currently has no native tree view).

Multi-select lookup tables

A lookup table where the user can pick more than one value.

• Project Online — control configured to allow multiple values.

• Altus — Dataverse does not support multi-select lookups, so a many-to-many relationship between the primary table (e.g. Project, Bookable Resource) and the lookup-value table is created. The selections appear as a sub-grid on the form.

Resources

Resources from the Project Online Resource Centre become Bookable Resources in Altus. The Project Online resource form maps to the Altus bookable resource form, with custom fields surfaced where they have been mapped.

Project Online — Resource Centre:

Project Online — Resource form:

Altus — Bookable Resources view:

Altus — Bookable Resource form:

Projects

Projects from the Project Online Projects view appear in the Altus Initiatives section. The Project Online project form maps to the Altus project form, including any custom fields that have been mapped via ImportProjects.ps1.

Project Online — Projects view:

Project Online — Project form:

Altus — Projects view:

Altus — Project form:

Schedules

Schedules are migrated as MS Project tasks under each Altus project's Tasks tab. The migration also brings across all 11 Project Online baselines (0–10) when re-run with the appropriate -BaselineNumber (see Migration Reference § Baselines).

Project Online — Schedule:

Altus — Schedule:

Resource cost rates

Cost rates from each MS Project resource are migrated into the Rates sub-grid of the matching Altus bookable resource, including time-phased values (one row per effective date).

Project Online — Cost Rates:

Altus — Cost Rates:

SharePoint Online

Risks and Issues

The default Project Online Risks and Issues SharePoint lists are migrated to the Altus Risks and Issues registers respectively. The OOTB columns map directly (Title → Name, Description / Discussion → Description, etc. — see the full mapping in Migration Reference). Custom fields can be added to the export configuration to extend the migration.

Project Online — Risks view:

Project Online — Risk form:

Project Online — Issues view:

Project Online — Issue form:

Altus — Risks view:

Altus — Risk form:

Altus — Issues view:

Altus — Issue form:

Custom lists

Custom SharePoint lists attached to a project subsite (e.g. Actions, Decisions) can be migrated to a corresponding Altus register by adding an entry to export.config.json (see Migration Reference § Custom lists). All standard SharePoint column types are supported.

Project Online — Custom list view:

Project Online — Custom list form:

Altus — Custom list view:

Altus — Custom list form:

Documents

Project documents stored in SharePoint document libraries are exported with their folder structure intact. Sub-folders, metadata, and version history are all preserved (version history is opt-in via the -ExcludeVersionHistory $false parameter). After export, documents can be uploaded to one of:

• A Teams / Microsoft 365 Group created for the Altus project.
• A new non-Project-Online SharePoint document library.
• An existing non-Project-Online SharePoint document library.

Project Online — Documents:

Altus — Documents: