On this page
Short answer: Excel is fine for a short plan with one owner. Switch when several people edit it, when dates depend on each other, or when someone asks "what changed since last week?" and nobody can answer. You do not need to retype the plan: import it, check the rows, and keep the sheet as a backup until you trust the new tool.
When a spreadsheet is enough
- One person maintains it.
- Fewer than about thirty rows, with no dependencies.
- No one needs to see history or who changed what.
- Nobody outside the team reads it.
If that describes you, stay. A tool you do not need costs more than it saves.
Signs you have outgrown it
- Copies multiply.
plan_v7_final_FINAL.xlsxis in three inboxes, and each differs. - Dates break by hand. One task slips and you move the next ten rows yourself.
- No audit trail. You cannot see who changed a date or when.
- Reporting is a weekend job. Someone rebuilds the status chart each Friday.
- Risks live elsewhere. The risk list is a second file nobody opens.
- Permissions are all or nothing. Everyone with the file can edit everything.
What a project tool adds
| Need | Spreadsheet | Project tool |
|---|---|---|
| One shared version | A file you send around | One workspace |
| Dependencies and slipped dates | Manual | Shown on the Gantt chart and in baseline variance |
| History | None, or file versions | Revision history with revert |
| Status for managers | Rebuilt by hand | Dashboard and health score |
| Risks and issues | A separate sheet | A RAID register with owners and scores |
| Who can edit what | Whoever has the file | Roles and per-project membership |
Move without retyping
NUSK imports Excel, CSV or a Google Sheets link. You map your columns once, and the import tells you what to fix before it saves anything:
- Tidy the sheet. One header row, one item per row, dates in one format.
- Map the columns. Title, owner, start, due, status, parent.
- Read the row report. Each problem is listed by row, before the import runs.
- Import. If the result is wrong, remove everything that import created in one click, fix the sheet and try again.
- Keep the sheet for a few weeks as a reference. Do not edit it.
Mistakes to avoid
- Importing everything, including finished work from two years ago. Bring in what is still open.
- Copying the sheet's quirks, such as merged cells and colour codes that carry meaning. Turn them into a status or a field.
- Running both in parallel for months. Pick a date and make the tool the source of truth.
When NUSK is not the right choice
If your plan is a single list that one person owns, a spreadsheet is simpler and free. Move when the pain is real.
Try the import on your own sheet
Import a copy of your current plan into a new project. If it does not look right, roll it back and nothing is lost.
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.