Microsoft Project Online retires September 30, 2026, migrate to a modern platform before it's too late.Start migration
September 30, 2026, Plan your migration now

Migrate from Project Online
in 5 steps

Onplana includes a built-in migration wizard that imports your projects, tasks, dependencies, resources, and baselines. Most migrations complete in under a day.

New here? Start with why teams switch from Microsoft Project to Onplana. Already evaluating dedicated replacements? See Onplana vs OnePlan.

Looking at the full 2026 picture? Onplana's Microsoft retirements 2026 hub maps every Microsoft sunset that hits PMOs this year, with deadlines, impacts, and the migration path for each.

Buy through Microsoft? The Onplana Migration Tool is on Microsoft Marketplace (starts free), so you can add it on your existing Microsoft billing.

See the import in 2 minutes

A real Microsoft Project file imported into Onplana, tasks, dependencies, resources, and costs preserved.

Then walk through the 5 steps below to do it yourself.
Step 1 ~30 min

Export from Project Online

Three export methods are supported. Choose the one that fits your setup.

OData API (recommended)

Connect Onplana directly to your Project Online tenant using the OData API. The importer authenticates with your M365 credentials and streams all projects, tasks, resources, and assignments.

Native .mpp upload

Upload your .mpp files directly from Microsoft Project. Onplana's parser reads the binary format server-side, no XML conversion step needed. Works with Microsoft Project 2007–2024 (.mpp).

Project XML export

Open each project in Microsoft Project and use File → Save As → XML Format (*.xml). Upload the resulting file to Onplana's migration wizard. Works with Microsoft Project 2007–2024 (MSPDI XML).

Step 2 ~5 min

Upload to the migration wizard

Navigate to the Migration Wizard in Onplana and upload your file or connect the OData endpoint.

File upload

Drag and drop your project file. We support .mpp (Microsoft Project binary), .xml (MSPDI), .mpx, .xer (Primavera P6), and Excel / CSV spreadsheets, up to 50 MB. Onplana parses the file server-side and extracts tasks, dependencies, resources, calendars, and baselines. A spreadsheet WBS keeps its hierarchy: outline levels, dotted WBS codes, parent columns and indentation are all understood.

OData import

Provide your Project Online site URL and credentials. Onplana will enumerate all projects and let you choose which ones to import.

Finance data preserved

Cost columns travel with the schedule. Planned Cost, Fixed Cost, Baseline Cost, and project Currency Code (e.g. EUR, GBP, USD) are all captured automatically. The total planned-cost rollup auto-populates Project.budget on import with source IMPORTED_MPP, so earned-value reports work out of the box. When 80% or more of tasks carry cost, the EVM engine uses your imported values directly, no rate-card setup needed first.

Step 3 ~15 min

Map fields

The field mapper shows you every column from your source and lets you map it to an Onplana field, custom field, or skip it.

Auto-mapping

Standard fields (Task Name, Start, Finish, Duration, Work, Resources) are mapped automatically. The importer recognizes all standard Microsoft Project field names.

Custom fields

Enterprise Custom Fields (ECFs) from Project Online are mapped to Onplana Custom Fields. You can create new custom field definitions on the fly during mapping.

Step 4 ~1–2 hrs

Preview and validate

Review a side-by-side comparison of source data vs imported data before committing. Fix any mapping errors.

Task preview

See every imported task with its status, priority, assignee, and dates. Spot and correct outliers before importing.

Dependency check

Onplana detects circular dependencies and orphaned successor links, common in large Microsoft Project plans, and flags them for review.

Step 5 ~1 day

Go live

Commit the import, invite your team, and run Onplana in parallel with Project Online until you're confident.

Invite team

Send invite links directly from Onplana. New members join with the right org role and project membership pre-assigned.

Parallel running

Keep Project Online active while your team settles in, most teams run parallel for 2–4 weeks before fully cutting over.

Want to follow along inside the product? The docs have a step-by-step import guide covering .mpp upload, XML, and the OData connector.

What gets migrated

Onplana supports all standard Microsoft Project fields out of the box.

✅ Fully supported

  • Projects (name, dates, budget)
  • Tasks + subtasks (all standard fields)
  • Task dependencies (FS, SS, FF, SF + lag)
  • Resources / assignees
  • Milestones
  • Baselines
  • Enterprise Custom Fields (ECFs)
  • Work breakdown structure (WBS)
  • Project calendars

⚠️ Partial / manual

  • SharePoint document libraries
  • Resource rate cards (re-enter in Onplana)
  • Views and filters (recreate in app)
  • Timephased data (aggregated)
  • Risk registers (export separately)
  • Issues lists (export separately)

❌ Not migrated

  • Email alerts/reminders (recreate)
  • Power BI reports (rebuild in Reports tab)
  • Custom ribbons / macros
  • VBA automation scripts

Five controls that keep this reversible

A migration is only as risky as the point of no return. Every step below is designed so you can stop, check, and turn back before that point arrives.

1

Assess before you touch anything

The estate assessment reads your Project Online tenant and writes nothing back to it. You get a per-project compatibility report before any decision.

Assess your estate free
2

Your source files stay untouched

Imports read your .mpp and XML exports. The originals are never modified, so the files you archived remain your fallback copy.

Preview an import
3

Preview every mapping before it commits

Field mapping is shown and editable before anything is written, including how custom fields and lookup tables land on the other side.

Read the mapping guide
4

Run both systems in parallel

Keep Project Online and Onplana side by side until the team trusts the new one. The usual gotcha is status divergence, and it is manageable when you plan for it.

Plan the parallel period
5

Write the rollback plan first

Decide the go or no-go criteria and the way back before cutover week, not during it. A written plan keeps reversing course cheap.

Structure the rollback
6

Validate before you decommission

Check the migrated data field by field while the old tenant is still alive. Decommissioning is the only genuinely irreversible step.

Run the validation pass

Patterns from early migration teams

Common observations from PMOs running the migration playbook in 2026. Specific customer quotes are added as they're cleared, we don't put words in mouths.

"OData connector + field mapper handled 90% of our enterprise custom fields automatically. The 10% that needed manual mapping took an afternoon."

Mid-sized enterprise PMO migrating 12 active programs

"The dependency cycle detector caught three pre-existing circular references in our largest schedule before we imported. Saved us debugging that in production."

Construction PMO with 4,500-task master plan

"Running parallel for four weeks gave the executive team confidence. By week three the AI risk detection was flagging issues we used to find in monthly review."

IT services org with 25-project portfolio

Recommended migration timeline

Allow at least 3 months for a safe migration with validation and team onboarding.

Month 1

Evaluate & plan

  • Sign up for free
  • Import 1–2 pilot projects
  • Review field mappings
  • Get stakeholder sign-off
Month 2

Migrate & validate

  • Import all projects
  • Validate data accuracy
  • Configure teams + roles
  • Set up automations
Month 3

Run parallel

  • Train your team
  • Run both systems side-by-side
  • Resolve edge cases
  • Freeze Project Online changes
Month 4+

Full cutover

  • Switch all workflows to Onplana
  • Archive Project Online data
  • Cancel Project Online license
  • Enjoy a modern platform

Migration FAQ

Deep-dive guides

Long-form playbooks for every step of the migration, from cost modelling and pre-migration inventory to the new Microsoft 365 surfaces (Planner, Project for the Web, To Do).

90-Day Project Online Migration Plan

Six-phase, 12-week plan for PMOs with weekly checklists and gate exit criteria.

Read guide

35-Item Pre-Migration Checklist

The inventory admins routinely miss before shortlisting destinations.

Read guide

Migration Cost Breakdown

Full 3-year cost across six categories, license, labor, parallel op, training, integrations, cleanup.

Read guide

Step-by-Step Migration Guide

Inventory, export, mapping, pilot, validation, cutover. 12-week template.

Read guide

Why Most Migrations Fail

The 5 mistakes PMOs make and how to avoid each one before kickoff.

Read guide

9 .mpp Compatibility Checks

Pre-migration audit nobody runs, surfaces fields that won't map cleanly.

Read guide

CFO-Proof Business Case

How to frame migration spend so finance approves on the first review.

Read guide

Migrate Microsoft Planner

One-click import + optional live sync via Microsoft Graph webhooks.

Read guide

Import Project for the Web Premium

Dataverse-backed importer that brings dependencies + effort + resources across.

Read guide

Microsoft To Do Bi-Directional Sync

Per-user mirror of assigned tasks to phone, watch, and Outlook.

Read guide

Project Online vs the New Planner

What changed across Microsoft's consolidated PM line.

Read guide

Microsoft Project Alternatives 2026

Full market roundup, Onplana, Monday, Asana, Smartsheet, Jira, Wrike.

Read guide

Answering the CFO's Objections

The objections finance raises about migration spend and how to answer each with numbers.

Read guide

The Rollback Plan

Structure the cutover so reversing course stays cheap until you have go-live confidence.

Read guide

CapEx vs OpEx for the Replacement

How to classify the spend and which framing clears budget review faster.

Read guide

Start your migration today

Create a free account, open the migration wizard, and import your first project in minutes. No credit card required.