Cost of Migrating from MS Project Online: 6 Categories

The cost of migrating from Microsoft Project Online splits into six categories, and the spread across them is wide: a small PMO doing the work itself budgets four figures, a consulting-led enterprise move runs to seven, and in both cases the spend displaces license spend rather than adding to it. Microsoft Project Online retired on September 30, 2026, a date Microsoft announced in July 2024 and carries on its product lifecycle page, so the budget question now belongs to teams working from exported files rather than a live tenant.

Most migration-cost guides are vendor pitches. They either minimize the cost ("just import and you're done") to make the destination tool look free, or inflate it to justify a consulting engagement. We don't do either. We built Onplana to be the best Microsoft Project alternative for schedule-driven PMOs and we think the numbers speak for themselves, but that only works if the numbers are honest.

The six categories that make up a full 3-year migration budget are license delta, data-migration labor, training and change management, parallel operation, integration rework, and cleanup. For each category the sections below show the underlying math, the ranges our cost calculator uses, and where the cost varies based on the choices you make. At the end there's a free Migration Cost Calculator that produces a specific number for your organization, but the categories matter more than any specific estimate, because what you need from a CFO is a defensible line-item budget, not a total. The later sections cover what staying cost, what missing the retirement date costs, ROI and payback, capex versus opex, and the CFO objections.

TL;DR: A planned Project Online migration runs $6,000–$20,000 one-time for a small PMO doing the work itself and $550,000–$1,500,000 for a consulting-led enterprise move, and it displaces license spend rather than adding to it. Staying was never free: a 50-seat Plan 3 PMO paid Microsoft $18,000 a year and, in our estimate, $126,000–$312,000 a year all-in with PWA administration, SharePoint support, Power BI upkeep and PM workaround hours counted. At 100 seats the worked example returns roughly 128% ROI over 36 months with break-even inside the first year. The subscription is opex under ASC 350-40; the one-time work goes on its own line and finance classifies it.

License-tier reference: the Microsoft Project Plan 1/3/5 vs Planner Premium breakdown covers what each cloud SKU is being retired into and where the feature gap sits.

Context: this post is one piece of the broader 2026 retirement timeline, the consolidated reference covering all three Microsoft Project ecosystem retirements happening in 2026.

The full Microsoft Project Online replacement stack: this post covers cost. For feature fit, read MS Project vs Onplana: Complete Feature Comparison for 2026 or the wider market in Best Microsoft Project Alternatives in 2026. For the retirement timeline: the three 2026 Microsoft Project retirement dates and what stops at each. For execution: how to migrate from Project Online. For a hub with a product tour: /ms-project-alternative.

The 6 cost categories most organizations forget to budget

Migration budgets that come in over tend to break down the same way: labor was underestimated, integration rework wasn't budgeted at all, or someone assumed training was "self-service" and then had to bring in an instructor three weeks into go-live. Below is the full category set we model, in the order they typically hit the budget.

License delta, the tip of the iceberg

The license delta is the 3-year cost of continuing to pay Microsoft if nothing changes, set against what you'll pay the new tool's vendor for the same period. Our calculator uses your current annual spend × 3 × (0.8 to 1.2) as the range, ±20% captures Microsoft price-tier changes and seat-count drift. For a PMO paying $50,000/year across 50 Project Online P3 seats, the license delta range is $120,000-$180,000. (Note: the legacy Project Online Professional and Project Online Premium subscriptions stopped accepting new customers on October 1, 2025, and Project Online itself retired September 30, 2026; existing subscriptions could not be renewed past that date, so the only forward-pricing options for organizations that were on those tiers are the Planner and Project Plan 3 / Plan 5 SKUs or a non-Microsoft tool.)

The important framing: migration cost displaces license cost, not adds to it. If Onplana's 3-year license comes in $40,000 below what you'd pay Microsoft, that's $40,000 of migration cost you're "pre-paying" with savings you'd otherwise bank. Most vendor cost comparisons hide this by presenting migration as pure additional spend. Read Onplana's pricing at /pricing and compare directly against your Microsoft E-plan pricing before accepting any vendor's cost narrative.

License delta is also where tool selection matters most. The cheapest reasonable destination and the most expensive differ by 3-4x on license. A 50-seat PMO moving to a budget tool might spend $30,000/year in license; the same PMO moving to an enterprise suite with heavyweight governance modules might spend $120,000/year. The 3-year gap is six figures. It's worth spending real time on the tool-selection step before committing, our detailed Onplana vs Microsoft Project comparison walks through the per-seat math side by side, and the broader project management software comparison for 2026 puts ten credible destinations on the same scoring grid so the license-delta math is anchored to a like-for-like shortlist.

Data migration labor, the big one

Data migration is almost always the biggest single cost category. Our calculator uses 3-12 hours per active project and 2-6 hours per historical schedule at a blended $100/hour rate. The range is wide because schedule quality varies enormously, a clean dependency-driven schedule with no custom fields imports in 2-3 hours, a resource-loaded cost plan with 40 custom field values and hard constraints needs a day of manual reconciliation.

For a typical mid-size PMO with 60 active projects and 200 historical schedules, that's $58,000-$192,000 in data-migration labor. The spread is dominated by two variables: your destination tool's native .mpp import quality, and how much cleanup you do per schedule.

Tools with native .mpp import (Onplana's import parses tasks, dependencies, resources, custom fields, and costs in one pass, and a .mpp or Project XML file imported into a new project brings its baseline as a baseline in Onplana) land near the low end. Tools that need a custom script to read each schedule you exported land near the high end. The free Project Online Inventory Checklist sharpens this estimate before you commit to a budget: it produces the active-vs-historical project counts and custom-field counts that drive the per-schedule labor math, so the data-migration line stops being a guess.

Companion reading on the labor math:

• The audit-style deep-dive: Before You Migrate Your MS Project File: 9 Compatibility Checks Nobody Runs.
• The two single biggest line-item drivers inside data-migration labor each have their own deep-dive: Project Online Custom Fields Migration (enterprise custom fields, lookup tables, calculated fields, typically 30-40% of the data-migration line) and Project Online Resource Pool Migration (Enterprise Resource Pool, cost-rate tables, calendars, timesheet history, typically 15-25% of the line).

The 3-year framing matters here because data migration isn't always one shot. Historical schedules get migrated in a second wave 6-12 months after go-live as the business decides which ones it actually needs. Budget for this phased reality, not a single push.

Training and change management

Training is 4-12 hours per PM at a blended rate, with a geo multiplier (1.0-1.5) that captures the overhead of coordinating training across multiple regions and time zones. A 50-PM single-location team budgets $20,000-$60,000. A 50-PM fully-distributed team budgets $30,000-$90,000.

Change management, the non-training component, is the part most organizations forget. This includes: executive communications to explain why the change is happening, manager-level reinforcement in team meetings for the first 30 days post-cutover, early-adopter champions who get trained first and help others, and the internal knowledge base or wiki that captures tool-specific patterns your PMs will reference for the next two years. Budget 20-30% on top of formal training hours for change management.

The change-management cost shows up differently in different organizations. Some PMOs over-invest here (expensive external consultants running workshop series) and some under-invest (one lunch-and-learn and a PDF handout). The right level is proportional to PMO maturity: teams that already have strong internal documentation norms need less; teams where institutional knowledge lives in individual heads need more. If you are pricing outside help, the migration vendor cost breakdown covers what consultancies actually charge per phase and where the day-rate premium is worth paying.

Parallel operation period

In a cut-over before the retirement, teams ran both tools concurrently, the old PWA site for in-flight schedules that weren't ready to move, the new tool for schedules that had moved. Our calculator uses 3 months as the default parallel-operation period with a 1.0-1.5× multiplier on quarterly current spend, plus 2-4 hours per PM per month of dual-tooling overhead.

For a 50-PM PMO with $50,000/year current spend, that's roughly $12,500-$18,750 in dual license, plus $30,000-$60,000 in PM overhead time. The PM overhead is almost always the larger piece and the most frequently forgotten. Now that Project Online has retired there is no parallel period against PWA: drop the dual-license line and keep the PM-overhead line, because the same hours go into re-entering and validating schedules from exports.

The parallel period is shorter if your destination tool has good .mpp ingestion, you can move schedules in batches rather than rebuilding them, which means individual PMs don't run dual-toolset for as long. Phased migrations extend the parallel period in exchange for smoother risk; big-bang migrations compress it but spike PM overhead into a short window.

Integration rework, the scope bomb

Integration rework is the category most likely to scope-bomb your migration. The calculator scales per-integration rates by organization band: $2,000-$8,000 per integration at mid-PMO tier (internal engineering + light consulting help), $5,000-$20,000 per integration at enterprise tier (SAP/Workday/regulatory-reporting-grade complexity). Small PMOs get a flat $500-$2,500 envelope regardless of count claimed, small orgs typically conflate "integrations" with dashboards or reports, and the real integration-rework effort at that scale rarely exceeds $2,500 in total.

Based on patterns we've seen in migration consulting, three integration categories drive most of the cost: Power BI reports consuming the OData feed, SharePoint-driven governance workflows, and custom-field-dependent exports to downstream systems (SAP, Workday, or homegrown tools). A single Power BI report rebuild typically runs 2-5 person-days once you account for column mapping, authentication, visual recreation, and stakeholder acceptance.

The uncertainty here is why the calculator's sensitivity analysis often flags integrations as the #1 or #2 driver of total cost variance. If you answered "don't know" to all three integration-discovery questions, your estimate's range is dominated by integration uncertainty. A one-day discovery pass with IT typically tightens the range by 30-50%.

Cleanup work, the hidden cost

Cleanup is the per-schedule work to fix broken dependencies, resolve orphaned resources, retire obsolete custom fields, and clean up the detritus accumulated over years of tool use. Our calculator uses $30-$100 per historical schedule plus 1-3 hours per PM for review time.

For a 200-historical-schedule, 50-PM PMO, that's $11,000-$35,000. Sounds small. The reason it's not larger is that most cleanup is batched, scripts run across the historical estate, a small team of reviewers spot-checks the output, and the per-schedule cost is mostly script-and-review, not hand-editing.

If you skip cleanup entirely, you carry forward problems to the new tool and pay for them later. Most schedules carry hidden quality issues that migration will preserve but won't fix. The cleanup line item is where you decide whether to fix them now or pay for them downstream.

Cost by organization size

Order-of-magnitude 3-year ranges across organization sizes. The calculator distinguishes between DIY migration (internal labor, typical for small + mid PMOs doing the work themselves over 2-8 weeks) and consulting-led migration (billable rates $100-150/hr + PM overhead). The ranges below use DIY assumptions; multiply by 2-4× for consulting quotes.

• Small PMO (under 10 PMs, under $20k/yr spend): $6,000-$20,000 DIY one-time migration effort. With internal labor at $50-65/hr, bulk-processed historical archives (10-20 minutes each), a $500-$2,500 flat integration envelope, and 2-3 weeks of parallel operation. Consulting firms typically quote $30k-$80k for the same scope. Onplana migration at this scale is mostly about modern tooling, not license-cost savings. Microsoft's current per-user pricing ranges from Planner Plan 1 at $10/mo through Plan 3 at $30/mo and Plan 5 at $55/mo (the legacy Project Online Professional/Premium SKUs stopped accepting new customers on October 1, 2025), so the savings versus Onplana PRO ($12/seat/mo) depend heavily on which Microsoft tier you're on today.
• Mid-size PMO (10-50 PMs, $50k-$300k/yr spend): $40,000-$180,000 DIY one-time migration effort. Mix of internal + light consulting labor at $75-95/hr, $2k-$8k per integration, 1-2 months parallel operation. Break-even typically within 3-12 months given the higher MS license base.
• Enterprise PMO (50+ PMs, $500k+/yr spend): $550,000-$1,500,000 one-time migration effort. Consulting-led by default at this scale: $100-150/hr rates, $5k-$20k per integration (heavily-customized SAP/Workday/regulatory reporting connections), full 3-month parallel operation. Integration rework often dominates the total.

These are rough ranges; a specific estimate for your org requires running the actual inputs. An enterprise PMO with a clean integration surface can land in the mid-size range; a mid-size PMO with a spaghetti of Power Automate flows can land in enterprise territory. Sensitivity to integration count is the dominant factor across all three segments. A small PMO that cannot spend on licences while it migrates can run its pilot on a Microsoft Project alternative with a free tier.

Note on DIY vs consulting framing (added with v2.2 calibration, 2026-04-23). The previous version of this article (pre-v2.2 calculator) quoted "$30k-$120k for a small PMO" which was calibrated against consulting firms' migration quotes. Calculator output is now explicitly DIY, what the PMO itself would spend on internal labor + direct dual-tooling costs. Consulting-led migrations remain roughly 2-4× higher. Both approaches are valid; pick the one that matches how your org plans to execute the migration.

How to get your specific number

We built a free migration cost calculator that runs the migration math against your specific inputs. Enter your PM count, active-project count, historical-project count, current annual spend, geographic distribution, and integration posture, and it produces:

• Stay-on-Microsoft cost, 3-year MS license continuing spend, shown separately (not summed with migration, see the v2 framing note below).
• Migrate-to-Onplana cost, five one-time categories (data migration, training, parallel operation, integration rework, cleanup) plus ongoing Onplana license and training refresh over 3 years.
• Net 3-year impact, migrate minus stay. Positive = migration costs more than staying would; negative = migration saves money over the window.
• Break-even month, when Onplana's lower ongoing cost catches up to the one-time migration investment.
• Sensitivity analysis, the three inputs that move your estimate the most, bounded to ±50% of your supplied values so small-PMO scenarios don't show absurd swings.
• Onplana vs generic migration, per-category reduction estimates with an explicit definition of what "generic migration" means.

Framing note: the v1 calculator (pre-2026-04-23) summed license-delta into the migration total, which double-counted; "staying" and "migrating" are mutually exclusive, so their costs cannot be added. The v2 calculator separates them cleanly; see the calculator's "net 3-year impact" number rather than a single migration total.

The calculator output is designed to be pasted directly into a business case. The per-category breakdown maps to budget line items; the sensitivity analysis gives you three specific "if X changes, cost moves by Y" statements that a CFO can sanity-check against real data.

What did staying on Project Online actually cost?

For a 50-seat PMO on Project Plan 3, the invoice was $18,000 a year at Microsoft's list price of $30 per user per month, and the all-in run cost was, in our estimate, $126,000 to $312,000 a year. The difference sat in payroll, in the IT service queue and in project managers' calendars, which is why finance never saw it and why waiting was never the free option it looked like. The subscription line is Microsoft's list price; the four layers under it are our estimates, from the same migration-consulting patterns as the integration figures above, with the arithmetic shown so you can substitute your own staffing and rates.

The PM workaround line is the largest and the easiest to dismiss as how Project Online works: Excel exports to level resources, hand-built status reports, offline reconciliation of actuals because timesheet data lags a day. The 20% realization factor is deliberate: only a fraction of recovered hours becomes delivery capacity. If your PMO is now on interim spreadsheets, only the first line has stopped; administration of the exported estate, reporting rebuilds and workaround hours continue until the replacement is live.

What does it cost to have missed the September 30, 2026 retirement?

Three costs, and they compound: the run rate you paid to the end with none of the benefit, the data that was never exported, and a rushed move at consulting-led rates with no parallel run. The retirement date has passed; whether your tenant has gone dark or is still answering outside any supported service, this is the section to take into the budget meeting.

The run rate you paid while waiting. At 50 seats the all-in cost of staying was $126,000 to $312,000 a year, so every quarter of deferral cost $31,500 to $78,000 of run rate and bought nothing, against a planned DIY migration of $40,000 to $180,000 one-time for a mid-size PMO per the calculator.

The data that was not exported. Microsoft has not committed to a read-only window, a grace period, or any post-retirement retention, so anything the data extraction window did not capture is not reachable through PWA, the OData feed or an .mpp export now. Three record types matter most to a regulated PMO: timesheet history, which finance and HR need for audit trails; baselines, of which Project Online stores up to eleven per project; and enterprise custom field history (risk ratings, funding codes, portfolio classifications). The audit cost arrives when an auditor asks in 2027 or 2028 for a 2025 project's schedule history and it is not there. Price it as the expected cost of an adverse finding times its probability, and put it on the business case as a line item.

The rushed move. A migration that starts after the switch-off has no parallel period. That removes the dual-license line (the calculator's 1.0–1.5× multiplier on quarterly spend for three months) and puts everything else on a compressed, consulting-led footing. The calculator's calibration puts consulting-led migrations at 2–4× DIY cost, so the mid-size DIY range of $40,000 to $180,000 becomes $80,000 to $720,000, and the break-even model puts a 250-seat moderate-complexity migration at $180,000 to $220,000 when it is executed in 8 weeks rather than 20, against $120,000 on the planned timeline. Re-entry from exports also sits at the high end of the labor matrix above, 3–12 hours per active project, because validation happens against a file.

Now that Project Online has retired, the order of operations is:

1. Secure every export that exists: .mpp files on PM laptops, MSPDI XML, OData extracts, and Power BI reports in import mode, which keep the data from their last successful refresh.
2. Count what the exports contain (active projects, historical schedules, custom fields, resource pool), then move active schedules first and hold the historical estate for a second wave.
3. Replace the parallel-operation line with a re-entry line: keep the calculator's 2–4 hours per PM per month of overhead and drop the dual license.
4. Name an owner and a cutover date for the interim spreadsheets; the workaround layer does not fall while the tool is a spreadsheet. The Project Online migration hub maps the motion from inventory to cutover.

How do you calculate the ROI of a Project Online migration?

ROI = (total benefits – total investment) / total investment × 100, where the benefits are the fully loaded cost of the Project Online stack you no longer carry plus quantified productivity gains, and the investment is the one-time migration cost plus the destination license over the same period. The formula did not change on September 30, 2026, only the label on its first input did: before the retirement it was the cost of staying, and now it is the run rate the migration replaces.

The worked example uses 100 seats on Plan 3 over 36 months. Every line is a list price or a labeled assumption you swap for your own, and the assumptions run lighter than the hidden-cost table on purpose (four hours a week of administration rather than a quarter-FTE, nine hours of Power BI upkeep per report per quarter rather than one to three person-days) so the result holds for a lightly customized deployment.

ROI = ($245,760 + $54,720 – $132,000) / $132,000 × 100 = 128%. Every dollar of migration cost returns $1.28 net over three years.

Break-even follows from the annual figures: avoided cost is $81,920 a year of run rate minus $24,000 of destination license, $57,920, plus $18,240 of productivity gain, $76,160 in total. $60,000 / $76,160 is 0.79 years, so the one-time cost is covered just under month 10; on avoided cost alone ($60,000 / $57,920) it is covered around month 12.

ROI and payback answer different questions. ROI measures total return as a percentage of total investment over the full window; payback measures how many months until cumulative savings cover the one-time cost. A payback under twelve months often convinces finance teams that distrust three-year models, and the break-even model works the payback at 50, 250 and 1,000 seats.

What moves the number. PWA administration: if the deployment really carried a quarter-FTE (500 hours a year at $90, $135,000 over 36 months) instead of four hours a week, the run rate replaced rises by $81,000 and ROI climbs to about 190%, so settle first who administered Project Online and what share of their time it took. Productivity realization: at 20% the gain doubles to $109,440 and ROI is about 169%; at 5% it halves to $27,360 and ROI is still about 107%. One-time cost: at $100,000 the ROI falls to about 75% and break-even moves to month 16; at $100,000 with 5% realization, the downside case, ROI is about 59%. The downside is bounded, which is what a steering committee is actually deciding.

CapEx vs OpEx: how finance classifies the replacement

The subscription is opex; the one-time migration work is whatever finance says it is, so keep the two on separate lines. Under ASC 350-40, the FASB standard for cloud computing arrangements, the ongoing fees for a service the vendor hosts are expensed as incurred, while implementation costs follow a three-phase model: preliminary project (expensed), application development (potentially capitalizable), post-implementation (expensed). Which phase your migration labor falls into is a call for your finance team; this is framing, not accounting advice.

The classification decides the approval path before anyone reads a number. Capital requests above an organization's threshold go to a capital committee and a longer timeline. A PMO that asks to buy new project management software has filed a capital request; a PMO that asks to replace a retired Microsoft service with a SaaS subscription on the same budget line as its M365 licenses has filed an operating one, usually inside existing budget authority. After September 30, 2026 the forced-replacement framing is literal: you are replacing a service the vendor withdrew, and a mandatory replacement does not compete with discretionary capital projects.

The decision rule, in four steps:

1. Put the subscription on a recurring opex line at list price. At 50 seats, Onplana Business on annual billing is $16 per seat per month, $9,600 a year, against $18,000 a year for Project Plan 3 at Microsoft's $30 list price; the delta is an opex saving from year one, not a new expense.
2. Put each one-time category from the six above on its own line, flagged "classification per ASC 350-40, finance to confirm". Bundling invites a capex classification for the whole project.
3. If finance classifies the implementation as capex anyway, do not argue standards in the meeting; get the subscription line confirmed as opex so the recurring portion never returns to the capital committee, and note that capitalizing lowers the year-one P&L hit.
4. Show the three-year model under either treatment; the license delta is identical in both.

How to build your internal business case

A credible internal business case has four parts, in order. First, the fixed deadline: Project Online retired September 30, 2026, the date has passed, and doing nothing is not an option. Second, the 3-year cost range, pulled from the calculator for your specific inputs. Third, the sensitivity analysis identifying which inputs drive the range, this gives your executive team the levers they can pull to reduce cost (archiving historical schedules, sharpening integration discovery, choosing a destination with good .mpp import). Fourth, a tool-selection recommendation backed by the first three.

The most common mistake in internal business cases is leading with the tool recommendation rather than the cost math. CFOs read cost math; they discount tool recommendations from anyone who obviously has a preferred tool. Lead with the numbers.

If you want a more opinionated structure for the deck itself, the three-pillar CFO business case framework goes deeper on how to sequence cost-of-inaction, 3-year TCO delta, and risk-adjusted ROI so the finance team has the answer to its own next question already on the page.

Once the cost math is in your exec deck, the tool-selection step is ~20 pages behind it. Two inputs feed that decision: what you already have (the 35-item pre-migration inventory makes this concrete, also available as the interactive /tools/project-online-inventory-checklist) and what replaces it best (the market roundup at /blog/best-microsoft-project-alternatives-2026, or the Onplana-specific head-to-head at /blog/ms-project-vs-onplana-comparison). The /ms-project-alternative hub page walks through what a Project Online replacement looks like inside Onplana, with a product tour.

CFO objections to the migration budget, and how to answer each

A CFO review is a risk review, not a technology evaluation, and every objection below is one of three questions in disguise: what happens if we do not, what happens if this goes wrong, and why now. After September 30, 2026 the third question answers itself and the other two get sharper.

"We already invested heavily in Project Online"

Yes, the original spend was real and rational when it was made; it is also gone regardless of what happens next, and Microsoft's retirement of the service, not the PMO's judgment, is what makes further spend on that stack irrational. The decision on the table is the least costly path from today to a functioning PMO, and once the CFO accepts that framing the conversation moves from justification to planning.

"The switching costs are too high"

Yes, technology estimates are usually the floor rather than the ceiling. The answer is three scenarios, the calculator's low, mid and high, with the assumption that separates them named (the difference between $X and $Y is whether the SAP export needs a rebuild or an adapter) and the budget set to the high case. A high-case approval that comes in under is a success story; a mid-case approval that overruns is a credibility problem.

"Training will disrupt the PMO"

Yes, throughput dips during a tool transition, and one that lands in a delivery peak is visible to executives. The dip is small enough to schedule around: the calculator budgets 4–12 hours of training per PM, under two working days, plus 2–4 hours per PM per month of overhead during the transition and 20–30% on top of training hours for change management. Put those hours on the delivery calendar and start training in the lowest-load window.

"I do not want to take a risk on a new vendor"

Yes, a new vendor can fail, be acquired, or raise prices. Decompose the risk into three checkable parts: financial stability, contractual lock-in (exit clause, notice period, data-export terms) and data portability, which you test by exporting before you sign. Then set it against what the PMO just lived through: a new vendor might fail; Project Online did retire. A managed uncertainty against a realized certainty is not a close call.

"We have integrations everywhere and this will break everything"

Yes, this is the objection most often partly true: Power BI on OData, custom .NET dashboards, SharePoint workflows, ERP bridges. Make "everywhere" a number. The calculator prices confirmed integrations at $2,000–$8,000 each at mid-PMO tier and $5,000–$20,000 at enterprise tier, and a one-day discovery pass with IT typically tightens the range by 30–50%. A list of 14 integrations with a discovery plan for the unconfirmed ones is a bounded scope; "everywhere" is not.

"Come back next budget cycle"

Yes, budget cycles are real, and for a discretionary project a January start is a legitimate answer. This is not a discretionary project: the platform has retired, and every month on interim spreadsheets is a month in which the largest line in the hidden-cost table, PM workaround time, does not fall, because with a spreadsheet as the tool every report is a workaround. If what the CFO doubts is the cost-of-inaction number, source it externally: Microsoft's Project Online service description and a written quote from a migration partner at current rates.

Conclusion

A defensible migration budget is a line-item budget, not a total. The six categories above are what a CFO actually needs to see: license delta, data-migration labor, training and change management, parallel operation, integration rework, and cleanup. Ranges matter more than point estimates, a number with a range lets stakeholders probe assumptions. A total without a range gets pushed back until someone produces one. The free calculator gives you the full six-category breakdown in under two minutes; once you have it, the business case writes itself. The rest of the case is the run rate you no longer carry, an ROI near 128% at 100 seats on conservative assumptions, a subscription that sits in opex, and six objections answered with a number.

Frequently asked questions

Was staying on Project Online until the retirement cheaper than migrating? No. For a 50-seat PMO on Plan 3 the invoice was $18,000 a year at Microsoft's list price, but the all-in run cost was, in our estimate, $126,000 to $312,000 a year, against a planned DIY migration of $40,000 to $180,000 one-time for a mid-size PMO per the calculator; the PMO that waited paid the run rate to the end and now pays consulting-led rates, 2 to 4 times DIY, with no parallel run.

What does it cost to have missed the September 30, 2026 Project Online retirement? Three things: the run rate paid to the end with none of the benefit, any data that was not exported (Microsoft has not committed to a read-only window, a grace period, or any post-retirement retention), and a compressed, consulting-led migration at 2 to 4 times DIY cost with no parallel period.

Is the cost the same regardless of destination tool? No. License delta varies by tool (Onplana's per-seat price is lower than most enterprise PM suites), data-migration labor varies with native .mpp import, and integration rework varies with how close the destination's API surface is to your connectors; the cheapest and most expensive reasonable destinations often differ by 2 to 3 times on total 3-year cost.

Is a SaaS project management subscription capex or opex? Opex, generally: under ASC 350-40 the ongoing subscription fees for a vendor-hosted service are expensed as incurred, while implementation costs follow a three-phase model in which the application-development phase may be capitalizable, so keep the two on separate lines and let finance classify each.

What is a typical ROI for a Project Online migration? Roughly 128% over 36 months in the worked example at 100 seats on Plan 3, with break-even just under month 10 when productivity gains are counted and around month 12 on avoided cost alone.

We have integrations everywhere; will the migration break everything and blow the budget? Yes, integration rework is the category most likely to scope-bomb a migration, which is why it gets a numbered inventory: the calculator prices confirmed integrations at $2,000 to $8,000 each at mid-PMO tier and $5,000 to $20,000 at enterprise tier, and a one-day discovery pass with IT typically tightens the range by 30 to 50%. The migration cost-overrun patterns post catalogues where overruns come from.

How much should I budget for contingency? 15 to 25% on top of the high-end estimate for a mid-size PMO: bias toward 25% if you answered "don't know" on any integration-discovery question, toward 15% only if your integration surfaces are well documented, and never use it to pad known work.

Should I include my own PM time in the cost? Yes. The calculator's PM-time components (2 to 4 hours per PM per month during parallel operation or re-entry, plus training hours) exist because the PM team's own time is the most common underestimate; exclude it and you finish the migration but miss other commitments that quarter.

---

Run the numbers for your PMO

The post covered the math; the free Migration Cost Calculator runs it for your specific PMO shape in about 3 minutes. Ten questions, six cost categories, sensitivity analysis, Onplana comparison, plus a copy-ready business-case framework. No signup, no email required to see the numbers (the full PDF is gated on email).

---

Related reading, the MS Project Online migration stack:

• MS Project vs Onplana: Complete Feature Comparison for 2026, if the cost math above suggested Onplana is in the shortlist, the head-to-head is the next step
• Best Microsoft Project Alternatives in 2026, full market roundup (Monday, Asana, Smartsheet, Jira, Wrike) scored across 14 features
• Project Online Retirement: Dates, What Stops, What to Export, the three 2026 retirement dates, what stopped at each, and what Planner doesn't replace
• Project Online TCO: The 3-Year Total Cost Model at Three PMO Scales, the supporting-stack layers at 50, 250 and 1,000 seats
• Project Online Migration Checklist (2026): 35 Items Admins Miss, the inventory that feeds this cost calculation
• How to Migrate from Microsoft Project Online, step-by-step execution guide once the budget is approved
• Before You Migrate Your MS Project File: 9 Compatibility Checks Nobody Runs, per-file audit that sharpens the data-migration labor estimate

Interactive tools (free, no account required):

• Migration Cost Calculator, this blog's companion tool
• Project Online Inventory Checklist, 35-item interactive inventory with PDF export

Landing pages:

• /ms-project-alternative, product tour + 5-step migration walkthrough
• /migration, the detailed migration plan
• /pricing, every Onplana tier with the annual discount
• /compare, side-by-side feature comparison

Microsoft 365 integration paths (zero-cost imports, included in every plan):

• Migrate Microsoft Planner to Onplana, one-click import + optional live sync via Microsoft Graph webhooks
• Import Microsoft Project for the Web (Premium), Dataverse-backed importer that brings full schedule data across
• Microsoft To Do Sync With Onplana, bi-directional per-user mirror to phone/watch/Outlook

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.