Project Online Migration
Microsoft has brought forward the retirement of Project Online from 2030 to 30 September 2026. From that date, Project Web App (PWA) access, data, and integrations will stop working, and Project Online (including the SharePoint subsites used for Risks, Issues, Actions, and Project Documentation) will be fully decommissioned.
Altus provides a set of PowerShell scripts and a documented approach that Altus Partners can use to migrate Project Online and the associated SharePoint Online data into Altus PPM before the retirement date.
Important
The Altus migration scripts are provided to Altus Partners to assist their customers. If you need a copy of the scripts referred to in this section please contact your Altus Partner Manager.
What can be migrated?
| Source | Data | Notes |
|---|---|---|
| Project Online | Projects | Including custom field data and lookup tables |
| Project Online | Resources | Including custom field data and lookup tables |
| Project Online | Schedules | Including task custom fields, resource rates, and all 11 baselines |
| SharePoint Online | List items | Risks, Issues, and custom lists |
| SharePoint Online | Documents | Exported for upload to Teams or SharePoint |
What is not migrated?
- Workflow History – low data volumes; align projects to the correct stage in the Altus Business Process Flow as a post-migration activity.
- Timesheet data – avoided to prevent significant Dataverse storage costs. Existing actuals are preserved in the .MPP via the assignment-level
Protected Actuals Beforedate. - Portfolio Analyses – the Altus Strategic Prioritisation module replaces this; effort to re-create is minimal.
Documentation in this section
| Page | Purpose |
|---|---|
| Quick Start | Recommended reading order to get up to speed on the migration. |
| Migration Overview | What is and isn't migrated, the migration approach, outcomes, and constraints. |
| Prerequisites | Software, accounts, licenses, solution layers, custom fields, forms, MS Project setup. |
| Altus POL Migration SharePoint App | Granting consent or creating your own Azure app for the SharePoint API permissions. |
| Migration Process | End-to-end procedure for migrating Project Online and SharePoint Online data. |
| Migration Reference | Field mappings and script extension points for projects, resources, tasks, lookup tables, baselines, lists, and documents. |
| Example Migration | Side-by-side examples of Project Online data and the resulting Altus data. |
| Troubleshooting | Known issues encountered when running the migration scripts and how to resolve them. |
| Frequently Asked Questions | Answers to common questions about the scripts and process. |
Recommended reading order
If you are new to the migration, work through the documents in this order:
- Example Migration — non-technical overview of the end-to-end outcome, useful when discussing scope with customers.
- Migration Overview — what will and won't be migrated, and why.
- Prerequisites — everything that must be in place before running the scripts.
- Migration Process — the detailed "follow the bouncing ball" procedure.
- Migration Reference — used while running the migration to extend scripts for custom fields and lookup tables.
- Altus POL Migration SharePoint App — required if the customer will not consent to the Altus-published Azure application.
- Troubleshooting and FAQ — kept open as reference while running the migration.