On this page
Short answer: you can leave MS Project without rebuilding your schedules. Save the plan as XML (File > Save As > XML), import it into a tool that reads the MS Project XML format, and check the result against a short list. Tasks, hierarchy, dependencies, dates and the working calendar usually come across. Resource rates, task-level calendars and custom fields usually do not. Whether the move is worth it depends on what you need from the new tool, so start there.
Why teams look for an alternative
The reasons we hear most often are practical, not ideological:
- Collaboration. A schedule that lives in one person's desktop file is hard for a team to update and hard for stakeholders to read.
- Mixed work. Many teams now run a fixed-date plan next to agile work, and want both in one place.
- Hosting and data control. Some organisations need the data on their own servers or in their own country.
- Licensing. Per-seat licences add up, especially when many people only need to view or update a few tasks.
If none of these apply to you, MS Project may still be the right tool. We cover that at the end.
What to check in any alternative
Do not judge a scheduling tool by how its Gantt chart looks. Check how it behaves. Ask for a demo with your own plan and test these:
| Check | What good looks like |
|---|---|
| Dependencies | All four link types (finish-to-start, start-to-start, finish-to-finish, start-to-finish) with lag |
| Rescheduling | Slip one task and everything that depends on it moves, on its own |
| Calendars | Working days and holidays respected; a task that spans a weekend takes the right number of days |
| Constraints | "Must finish on", "start no earlier than" and similar, honoured by the schedule |
| Baseline | You can save the original plan and compare it with the forecast later |
| Critical path | The longest chain of dependent tasks is shown, with its length |
| Cost | Budget and actual cost per task, and earned value if you report it |
| Import and export | A way in from MS Project and a way back out, so you are not locked in |
| Mixed methods | Tasks, deliverables and milestones next to agile items if you need both |
Run the "slip one task" test first. A chart that does not reschedule is a drawing, not a plan.
How a plan moves across
MS Project can save a plan in an open XML format (MSPDI). That is the usual bridge to other tools. The older binary .mpp file is not the same thing, and most alternatives, including ours, do not read it directly. Save as XML first:
- In MS Project, choose File > Save As and pick XML Format.
- Open your new tool's import for MS Project XML and upload the file.
- Review the result and the warnings the importer shows.
In NUSK, the import reads the following from the XML file:
- Structure. The outline hierarchy becomes parent and child work items, in the same order. The project summary row and blank rows are skipped.
- Dates and progress. Start and finish dates, and percent complete. Progress sets the status: 100% becomes Done, anything above zero becomes In Progress.
- Dependencies. Predecessor links with their type (finish-to-start, start-to-start, finish-to-finish, start-to-finish) and lag.
- Constraints. The constraint type and date (must start on, must finish on, start no earlier than, and so on).
- Baseline. The first baseline's start and finish dates are kept for variance reporting.
- Cost. Task cost and actual cost.
- Milestones. Milestone tasks become milestones, each linked to its own milestone record so the milestones list, the Gantt chart and the dashboard agree.
- Calendar. The project's working days and non-working exception days, so durations still add up.
- Notes and owner. Task notes become the description. The first resource assigned to a task becomes its owner.
A plan of up to 20,000 tasks imports in one go. Links that point at tasks which were not imported are skipped, and the import tells you which ones.
What does not carry over
Be ready for these gaps. They are typical of any move away from MS Project, not just ours:
- Resource rates and work hours. The importer takes names, not pay rates, work contours or effort-driven scheduling. Cost rates are set up again in the new tool.
- More than one assignee per task. Only the first assigned resource becomes the owner.
- Task-level calendars and custom fields. Recreate these by hand if you rely on them.
- Formatting and views. Bar colours, filters and saved views stay behind.
- The
.mppfile itself. You need the XML export.
Do a pilot first. Import one real plan, then compare the old and new Gantt chart side by side, the finish date and the critical path. If the finish date moves by more than a day or two, check the calendar and the constraints before blaming the tool.
Going back out
Lock-in worries are fair. NUSK can export a project as MS Project XML, with the outline, dates, milestones, dependencies, working calendar and assignees, so a plan can be opened in MS Project again. MS Project recalculates the schedule when it opens the file. Test the round trip on a copy before you rely on it.
What you gain: the rest of the project, not just the chart
A scheduling tool is more useful when the plan sits next to the things that decide whether it succeeds:
- Baseline, forecast and critical path on the same Gantt chart.
- Cost and earned value (planned value, earned value, actual cost, CPI, SPI and the forecast at completion) on the project dashboard.
- Risks, assumptions, issues and dependencies in one register that feeds a health score.
- Agile work next to the plan. Sprints and boards for the teams that work that way, and deliverables and milestones for the plan. Each project can be predictive, hybrid or agile.
- Hosting choice. The same product can run on your own server or on a desktop, with Arabic and English, including a full right-to-left layout.
When MS Project is still the right tool
Be honest with yourself. Stay on MS Project if:
- You build very large plans with resource levelling, effort-driven scheduling and per-resource calendars, and the schedule engine is the product you depend on.
- Your clients or contracts require plans in MS Project format and nothing else.
- Your organisation is already standardised on the Microsoft stack and the licences are paid for.
- A single planner owns the schedule and nobody else needs to touch it.
NUSK is a better fit when many people must update the plan, when the data must stay on your own infrastructure, when you mix fixed-date and agile work, or when you want cost, risk and schedule in one view. It is not a replacement for deep resource levelling.
Try it with your own plan
The quickest test costs you ten minutes. Save a real plan as XML, import it into a new project, and run the checks above: slip one task, read the critical path, compare the finish date. If the result matches, you have your answer.
See it with your own project
Import a plan or a Jira project into a free NUSK workspace and judge it on your own data.