Project management
How to Move Project Work Out of a Spreadsheet
Published 9/26/2026 · Updated 9/26/2026 · Dayzen
Why the sheet stopped being the record is a different article: when spreadsheets and chat stop working. Read that if you are still unsure the move is warranted. This page assumes you have decided, and you want the work to land cleanly.
Key takeaways
- What becomes what
- What to leave behind
- The order of the move
- Owners and names
Moving project work out of a spreadsheet means deciding what each row becomes, then creating those tasks in one project. It does not mean uploading the file. Dayzen has no spreadsheet importer. If you plan the move as a file format, you will stall on columns the product will not map. Create the tasks that are still true, and leave the rest in the sheet.
Why the sheet stopped being the record is a different article: when spreadsheets and chat stop working. Read that if you are still unsure the move is warranted. This page assumes you have decided, and you want the work to land cleanly.
What becomes what
Use one live sheet, not every copy in people's downloads.
| In the sheet | In the project |
|---|---|
| The file, or one tab, that is one outcome | One project |
| A group of rows that are an area of work | A section |
| A row someone still has to do | A task |
| The owner column, if it is a real person | The assignee |
| A date you still believe | The due date |
| A start column you still believe | The start date |
| A status word people actually use | A status, mapped to Not started, In progress, Done, or Closed |
| A note that changes the task | The description, once |
| A number that is a calculation | Stays in the sheet |
Sections and dates and estimates are the field meanings. Do not also copy a "percent complete" column into a custom field on day one. You will not keep it updated, and it is not a status.
What to leave behind
Leave rows that are done and will not be reopened, unless you need them as context for a live task. The old sheet can remain the archive. Leave formulas, price grids, and budgets. A currency custom field is not a replacement for a pricing model, and it will not invoice anyone.
Leave rows that are really chat. "Waiting to hear back" with no owner is not a task until you name a person and a next action. Leave duplicate rows. If two tabs disagree, pick the one the owner says is current and do not average them.
Do not move personal reminder rows that only one person uses and that are not part of the shared outcome.
The order of the move
- Name the project from the outcome, not from the file name "final_v7."
- Create sections from the groups you will still filter by. If the sheet has fifteen color codes, you do not have fifteen sections.
- Write the status list in the project's words, then map the sheet's words onto it. "Waiting" and "stuck" often both mean In progress, with a Blocks link you should add only where it is real.
- Create tasks for open rows. Assignee and due date only if the cell is trustworthy. A blank owner stays unassigned on purpose, not as "Team."
- Stop using the sheet for status. Put a line at the top of the sheet: status lives in the project as of this date. Keep the sheet for numbers if you still need numbers.
- For one week, when a date is said in chat, it is typed on the task the same day. The old habit is the real risk, not the missing import.
If the sheet has hundreds of open rows, move the ones due in the next month. A complete historical copy is how the new project starts dead.
Owners and names
Match assignees to people who are members of the workspace. A name in a cell is not a user account. If the owner has left, the row needs a living assignee or it should stay in the archive. Do not create a member record just to preserve a name on a closed row.
Keep task titles short. Sheet rows often start with a code, a date, and a sentence. The code can sit in a text custom field if you still search by it. The title should be the work.
After the first week
Check three things. Are new status changes happening on the task, or still in the sheet? Are two files still being emailed? Did any moved task turn out to be a calculation? Put calculations back.
Add Blocks only for waits you hit during the week. Do not draw a dependency from every "see also" note in the sheet. Related to exists for context, and you may not need it during the move at all.
Tell the people who used to own the file that they are not gatekeepers of a copy anymore. They may still own the budget sheet. They do not own a second status.
A worked tab
Imagine a tab called "Launch" with columns: Area, Task, Owner, Status, Due, Budget, Notes.
Area "Design" becomes the Design section. Area "Ads" becomes the Ads section. Rows with status Done last quarter stay in the sheet. The row "Homepage" with owner Priya, status Doing, due next Tuesday becomes a task in Design, assignee Priya, status In progress, that due date. The Notes cell that says "legal must see the headline" becomes one comment, and only if it is still true. The Budget column stays in the sheet. You do not make a currency field for it during the move. If a later conversation needs an amount on the task, that is a separate decision, and it still will not invoice.
The row "TBD banner" with no owner and no date does not move until someone names the work. Moving it as an empty card recreates the blank row.
When the open rows exist as tasks, write the date on the sheet and stop editing status there. The next change to Priya's due date happens on the task. If it happens in the sheet instead, the move did not take, and another meeting about columns will not fix the habit.
Conclusion
Move open work by hand into a project, sections, and tasks, with owners and dates you believe. Leave calculations and closed history in the spreadsheet. Do not wait for an importer. After the move, the project is the status. The product is /pms.
One mistake to avoid
Do not keep a "sync" tab that you update from the project each Friday. That tab becomes the third status. If a leader wants a snapshot, a person looks at the board and writes the sentence that day. The sentence is not a second editable list.
Priya should be able to find Homepage in Design without opening the sheet. If she cannot, the title was too cryptic or the section was wrong. Fix that task before you move the next twenty rows. Speed comes from a clean pattern, not from pasting everything on the first afternoon.
Keep a written list of rows you refused to move and why: done, duplicate, calculation, or no owner. That list stops someone from "finishing the import" next week by pasting the rejects back in as empty tasks.
Related articles
Project management
How to Create a Custom Project Role
A custom project role is a named set of permissions on a workspace, assigned to a member. It answers "what may this person do here?" The map of access layers, organization versus workspace versus a share, is how project access works. This page is the narrower job: create one role and apply it. The example is a reviewer who can comment and must not edit tasks.
Dayzen
Project management
Project Channels, Section Channels, and Private Channels
A channel is a room with a scope. The scope decides who is in it. Dayzen has four scopes: the workspace, one project, one section, or a custom list of members. Pick the smallest room that still includes everyone who must hear the conversation. A custom list is how you make a private channel. It is not a direct message feature with an inbox of its own.
Dayzen
Project management
Project Chat vs Task Comments
Project chat and task comments are both places to write. They are not interchangeable. A channel is the conversation for a project, a section, or a chosen group. A comment is a note on one task, including a reply in that task's thread. Put the decision where the next person will look for it. If they will look at the task, comment. If they will look at the room, use the channel.
Dayzen