See your MS Project plan in Onplana

An honest compatibility report for moving your Microsoft Project file into Onplana. You get a 0-100 score, per-bucket counts (tasks, dependencies, resources, constraints) of what transfers cleanly vs. what needs review, a Gantt preview of your project in Onplana styling, a list of migration gaps with specific guidance, and 4-6 Onplana features relevant to your file's shape. No marketing pitch - if a feature doesn't migrate cleanly, we tell you.

Yes. Upload your file, view the full report, download the PDF - no payment, no trial, no credit card. We ask for an email to deliver the PDF and occasionally share migration tips tied to Project Online's September 2026 retirement. Unsubscribe any time. When you're ready to migrate for real, Onplana has a free tier that supports the same .mpp import.

Native Microsoft Project files (.mpp) and MSPDI XML (.xml). Both are parsed by the same MPXJ-backed pipeline that powers our Schedule Health Check tool. Files up to 50 MB work out of the box. If you have a password-protected .mpp or one saved from Project 2003 or earlier, export to MSPDI XML first via File → Save As → XML.

We parse it in memory, run the compatibility analysis, and discard the source bytes. The file is never written to disk or persisted in any blob storage. What we keep: the structured compatibility report (task counts, dependency counts, gap list, features-gained list) associated with a random analysis ID. If you unlock the PDF, we also store your email (encrypted at rest with AES-256-GCM) for report delivery and occasional product updates.

The score is computed from concrete signals in your file: task count, dependency types (FS/SS/FF/SF), lag values, resource email matches, hard constraints, deadlines, custom field usage, and baseline counts. The 0-100 number is a weighted mean across four buckets - tasks 55%, dependencies 25%, resources 10%, constraints 10%. It's a directional estimate based on what Onplana's import can preserve mechanically, not a guarantee. Do a pilot import on 1-2 projects before migrating your full portfolio.

"Lossy" means a task has a predecessor with lag or a non-FS dependency type (SS/FF/SF). These transfer but Onplana stores lag as integer days, so fractional-day or elapsed-time lag rounds. "Manual" means a task has a hard date constraint (Must Start On, Finish No Later Than, etc.) or a deadline field - Onplana preserves the date but doesn't enforce the same "must"-semantics, so a human should verify post-migration.

Text/Number/Date/Flag custom fields map cleanly to Onplana custom attributes. Formula fields and lookup tables need to be recreated manually. Sub-projects and inserted-project references migrate independently - import each source project, then link them via Onplana portfolios. VBA macros, task-level calendars, and cost rate tables with multiple rates are not supported today; the preview will flag these with specific guidance.

Yes. If you're confident your file is well-structured, create an Onplana account (free tier works) and use Settings → Migrations → Import to upload the same .mpp/.xml. The preview is a pre-flight check that surfaces issues before you commit, but it's not required. Most teams find the preview useful for justifying migration effort to stakeholders and planning the post-migration cleanup.

Yes - to keep these tools free and fast for everyone, we apply reasonable limits: up to 5 uploads per day, and up to 10 email unlocks per email per day. Limits reset on a rolling 24-hour window. If you hit a limit, we'll tell you when you can retry. For higher-volume needs, email support@onplana.com.