How to Migrate to Microsoft Office Project Portfolio Server — Step-by-Step

How to Migrate to Microsoft Office Project Portfolio Server — Step-by-Step

Overview

This guide gives a practical, step-by-step migration path from an existing project/portfolio system (Project Server, legacy Project Portfolio Server, or other PM tools) to Microsoft Office Project Portfolio Server. It assumes an on-premises target; adjust for cloud or hybrid deployments as needed.

1. Plan the migration

1. Assess current environment: inventory projects, resources, custom fields, workflows, security groups, integrations, and data volume.
2. Define scope and goals: select which projects, history range, and artifacts to migrate (tasks, baselines, timesheets, documents, reports).
3. Choose migration approach: big‑bang (all at once) or phased (by portfolio, department, or project type).
4. Set timeline and rollback plan: schedule windows, establish backups, and define success criteria and rollback steps.

2. Prepare target Project Portfolio Server environment

1. Hardware & software prerequisites: verify OS, SQL Server, IIS, .NET versions, and patching per Microsoft guidance.
2. Install and configure Project Portfolio Server: set up application servers, database instances, and service accounts.
3. Configure security and permissions: recreate AD groups, service accounts, and assign roles.
4. Enable required services and integrations: search, email/SMTP, authentication (AD/claims), and any third‑party connectors.

3. Cleanse and map source data

1. Data cleanup: remove obsolete projects, merge duplicates, and standardize naming and custom fields.
2. Map fields and objects: create a mapping document linking source fields, lookup values, and entities to target equivalents.
3. Decide on history depth: full history, last N months, or only current snapshots.
4. Export supporting artifacts: documents, templates, reports, and attached files.

4. Choose migration tools and prepare scripts

1. Built‑in export/import: evaluate if Project Server export/import suffices for your data size and complexity.
2. Third‑party migration tools: consider specialist tools for complex mappings, attachments, and preserving history.
3. Custom scripts and APIs: plan PowerShell, CSOM, or PSI scripts to automate data transforms and uploads.
4. Test transforms: run small exports, validate mappings, and adjust scripts.

5. Run pilot migration

1. Select pilot set: choose a representative subset (projects, users, and integrations).
2. Execute pilot: migrate data, attachments, and permissions.
3. Validate thoroughly: verify project structure, resource assignments, schedules, baselines, timesheets, and reports.
4. Collect feedback and refine: fix mapping issues, performance settings, and user training materials.

6. Full migration execution

1. Schedule migration window: notify stakeholders and disable conflicting changes in source system.
2. Perform backups: full backups of source and target systems before starting.
3. Execute migration in phases (if chosen): follow phased order from least to most critical.
4. Monitor and log: track errors, performance, and data gaps; resolve issues as they appear.

7. Post‑migration verification

1. Functional testing: confirm projects, tasks, dependencies, baselines, and reporting work as expected.
2. Security validation: ensure AD groups and role permissions match the mapping.
3. Integration checks: validate connectors (timesheets, ERP, BI, document management).
4. User acceptance testing (UAT): have power users validate workflows, reporting, and day‑to‑day tasks.

8. Cutover and go‑live

1. Finalize cutover tasks: enable users, switch integrations to target endpoints, and update DNS or URLs if needed.
2. Communicate: provide go‑live