Onplana vs OnePlan
Two different bets on PMO tooling for Microsoft 365 teams.
OnePlan and Onplana are two genuinely different bets on portfolio and project management. OnePlan is built on the Microsoft cloud and runs inside Teams, Azure DevOps and SharePoint, strong if your organisation is committed to Microsoft as a platform. Onplana is a standalone platform, AI-native, with a published price on every self-serve plan and a free plan with the full Gantt. Neither is wrong; the right answer depends on whether your strategic direction is "stay deep in Microsoft" or "decouple from Microsoft platform decisions."
The architectural difference, in one paragraph
Both extend project-management capabilities. They sit in fundamentally different places in your stack.
OnePlan
Built on the Microsoft cloud. OnePlan describes itself as built on the Microsoft cloud. It installs into Microsoft Teams, Azure DevOps and SharePoint, and connects to Planner, Project desktop, Power BI and Power Apps.
Strong for orgs already deep in Microsoft 365 that want portfolio management inside the tools their teams use. Less suited if you're not committed to Microsoft as a platform direction.
Onplana
Multi-tenant SaaS. Onplana runs as a hosted service. On Enterprise+, Onplana sets up and runs a private copy in your own Azure subscription. M365 integrates via standard SAML/OIDC SSO and Microsoft Graph, no Power Platform required.
Strong for orgs that want to decouple from Microsoft platform decisions, or for greenfield PMOs without existing Microsoft 365 PPM investment.
What a Microsoft Project file brings across
Most comparisons stop at features. The question that decides your timeline is what comes across, what gets rebuilt, and who has to be available for it.
| What you are moving | Into OnePlan | Into Onplana |
|---|---|---|
| Schedules (.mpp / MSPDI) | Connected from Project Desktop through OnePlan's Office add-in; Microsoft Project Integration is on its Enterprise plan. | Parsed natively. All four dependency types with lag, costs and percent-complete carry over. |
| Resource pool | Not stated on its pages. | Matched by email address. Unmatched people surface as warnings rather than being silently created as users. |
| Enterprise custom fields | Not stated on its pages. | Become custom field definitions, with their per-task values attached. |
| Actuals and timesheets | Timesheets are in Basic; importing actuals is not stated. | Deliberately not imported. Microsoft Project ActualCost is frequently stale, so Onplana rebuilds actuals from timesheets against rate cards instead of inheriting a number nobody trusts. |
| Project sites and documents | SharePoint stays where it is; OnePlan can run within SharePoint. | SharePoint stays where it is. Link or attach it into the project workspace. |
| Workflows and stage gates | Rebuilt as workflows and automations, on its Enterprise plan. | Rebuilt in the built-in 12-stage pipeline. |
Some of it will be rebuilt wherever you land
Custom workflows, project site permissions, resource plans and reports built in your old tool have no portable form. They are re-authored on the destination platform, whichever one you pick. That work is where migration estimates usually go wrong, so it is worth scoping before you choose a tool rather than after. The FAQ below lists the specific cases.
What the import actually looks like
Your Microsoft Project plan, imported and mapped
Both products connect to Microsoft Project files, so the honest question is what the import does. This is the wizard: .mpp or MSPDI XML, with dependencies, custom fields and costs mapped before you commit to anything.
Feature-by-feature comparison
Where one platform leads, we mark it. Where they're at parity, we mark a tie.
| Capability | OnePlan Built on the Microsoft cloud | Onplana Standalone SaaS |
|---|---|---|
| Hosting model | "Built on the Microsoft cloud"; installs into Teams, Azure DevOps and SharePoint | Hosted multi-tenant SaaS; a dedicated deployment in your own Azure subscription (Enterprise+) |
| Microsoft 365 integration | Runs inside Teams; Planner, Project desktop, Power BI and Power Apps connectors | SAML/OIDC SSO + Microsoft consumer SSO + Graph integrations |
| AI architecture | Sofia AI, its embedded assistant | Claude (Anthropic) + Azure OpenAI, both disclosed with operator-managed failover |
| Time to first project | Not stated; a free trial sign-up is offered | Minutes (sign up, import .mpp, project ready) |
| .mpp / MSPDI fidelity | An Office add-in connects Project Desktop .mpp files (Enterprise) | Native MPXJ-based parser; preserves all 4 dep types, ECFs, costs |
| Desktop app that opens .mpp files | Not offered | Onplana Schedule: free Windows and Mac app, opens, edits and reschedules, saves back to Project XML |
| Free starter tier | OnePlan Free: My Work and Teams collaboration; the Work Plan and portfolio on paid plans | ✓ Free plan with full Gantt + critical path |
| Trial of a paid plan | A free trial, no credit card required | Some Free workspaces are offered a 14-day trial of a paid plan in the app, with no card |
| Pricing transparency | Basic $10 a user a month billed yearly (5+ users); Enterprise on a quote (pricing page, 3 November 2026) | Public per-seat pricing across 4 self-serve plans: Free, $12, $20 and $29 per seat a month |
| Stage-gate governance | ✓ Workflow and automations (Enterprise) | ✓ Built-in 12-stage proposal pipeline, multi-reviewer gates and an audit trail, on the Enterprise plan and up |
| Tasks shorter than a day | Task durations, unit not stated on its Work Plan page (31 October 2026) | Onplana Schedule plans to the minute (type 2h or 90m); the web app schedules in whole working days |
| Phone and tablet apps | An Android app on Google Play | Onplana Tasks on iPhone, iPad and Android phones and tablets; Onplana Schedule from the Microsoft Store, the Mac App Store, the App Store and Google Play. All free. |
| Capacity / portfolio | ✓ Portfolio Plan, and a Resource Plan on Enterprise | ✓ Native (capacity across projects, RAG portfolio rollups) |
| Sourced from public product documentation. "Tie" indicates rough parity; deeper buyer fit depends on existing platform investment. | ||
Which one fits your team?
When OnePlan fits
- •Your organisation has standardised on Microsoft 365 and wants portfolio management inside Teams, Azure DevOps and SharePoint.
- •You want portfolio, resource and financial plans alongside Planner, Project desktop and Power BI.
- •You value Microsoft platform continuity over decoupling.
- •You're comfortable with a quote for the Enterprise plan, where resource and financial planning sit.
When Onplana fits
- •You want PM tooling that doesn't tie you to one vendor's platform decisions.
- •You want a free starting tier and transparent per-seat pricing before committing budget.
- •You want a dual-provider AI engine (Claude, Azure OpenAI), both disclosed, one on standby, not one Microsoft-locked default.
- •You want a first project the day you sign up, with no add-in or tenant setup.
- •You have
.mppfiles to import and want native MPXJ-based fidelity preserving all four dependency types, ECFs and costs.
Test the comparison with your own data
Two free tools, no signup, and a third that estimates 3-year migration cost.
Migration Preview
Upload a .mpp; see exactly what would land in Onplana.
Open toolMigration Cost Calculator
Estimate full 3-year migration cost (licenses, parallel running, training).
Open toolPMO Maturity Assessment
15-question diagnostic on whether your org needs governance-heavy or governance-light tooling.
Open toolFrequently asked questions
How do you bring Microsoft Project plans into OnePlan?▾
What in a set of Microsoft Project plans does not move cleanly to anything?▾
How quickly can we evaluate both?▾
If we're committed to Microsoft 365, does OnePlan win automatically?▾
Both have stage-gate governance, what's the actual difference?▾
What about pricing?▾
Can we run a 4-week pilot of each?▾
Try Onplana before you decide
Free plan, no credit card, no sales call. Sign up, import a real .mpp, see whether a standalone platform fits.