> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.netnet.app/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # Moving a Task Without Losing Its Time or History **In brief:** Move task carries a Job Task's time and history to another Deliverable or Job. Nothing converts between Quick Tasks and Job Tasks. **Applies to:** Anyone with a role that can edit Jobs. Move task appears on Job Task rows only. **See also:** Job Tasks: Assignees, Allocations, and Statuses covers the rest of the task row, and Quick Tasks vs Job Tasks vs My Lists: Which to Use covers where each kind of work belongs. **Moving a task never costs you its history. Use Move task in the ⋮ menu on any Job Task row to send it to a different Deliverable in the same Job, or to a different Job entirely. The task keeps its identity and every hour ever logged against it comes along. Nothing is duplicated, nothing is recreated, nothing is lost. The source Deliverable's actuals go down by exactly what the destination's go up by, and the Job's total never changes.** You'll find it under **Jobs → your Job → Tasks**, in the **⋮** menu on any task row. # Why this exists Work does not always land in the right place the first time. A Deliverable gets restructured halfway through. A client adds something that really belongs on a different Job. Somebody files a task under Discovery that was always part of Build. This is normal, and without a way to move things the options are all bad: delete the task and recreate it, which throws away the logged time; leave it where it is, which corrupts every number downstream; or do nothing and let the reporting drift away from reality. Moving is the honest path. The work moves. The truth stays intact. Treat it as a normal part of running a Job, not an emergency repair. # How to move a task 1. Find the task row on the Tasks tab, inside its Deliverable or in **General Job Tasks**, as laid out in [Job Tasks: Assignees, Allocations, and Statuses](https://help.netnet.app/en-us/article/job-tasks-assignees-allocations-and-statuses-1fy1ov5/) 2. Open the **⋮** menu and choose **Move task** 3. A panel opens on the right, showing where the task lives now 4. Pick **Move to another deliverable** or **Move to another job** 5. Choose the destination, then click **Move Task** The move happens immediately. There is no staging step and nothing to confirm afterwards. You move one task at a time. ## Move to another deliverable Stays inside the current Job. Pick any other [Deliverable](https://help.netnet.app/en-us/article/deliverables-status-due-dates-and-confidence-explained-x7yi7t/) on it. The one the task is currently in is left off the list, so you cannot accidentally move a task to where it already is. ## Move to another job Two choices instead of one: first the destination Job, then a Deliverable inside it. The Job you are already in is left off the list. # What moves and what stays **Fields that change:** the Job and the Deliverable. That is the entire list. **Everything else stays exactly as it was:** - The task's identity, so links, chat, and audit history still point at the same task - Every time entry ever logged against it - Its status, whether that is Backlog, In Progress, Completed, or Archived - Its start and completion timestamps - Its title, description, due date, and assignee allocations Who is assigned does not change when a task moves. Changing which people are available to assign in the first place is a workspace-level job, covered in [Managing Team Members, Invites, and Join Requests](https://help.netnet.app/en-us/article/managing-team-members-invites-and-join-requests-dstmjr/). # What happens to the hours All of them move. Not a split, not a copy, not a partial. If six hours were logged against the task, the source Deliverable's actual hours drop by six and the destination's rise by six. The total hours in the workspace are identical before and after. Both Deliverables' rows on the [Job Performance tab](https://help.netnet.app/en-us/article/reading-the-job-performance-tab-plan-actual-drift-1hi6cta/) update to match, immediately. || This is the reason moving is safe to do casually. The numbers are not adjusted or reconciled after the fact, they simply follow the task. A Deliverable's actuals are always the sum of the time on the tasks currently inside it, so moving a task is self-correcting by construction. # The service type rule There is one thing that will stop a move, and it is worth understanding before you hit it. **A task's service types have to exist on the destination Deliverable.** Every assignee allocation on the task carries a [service type](https://help.netnet.app/en-us/article/service-types-and-service-groups-what-each-one-does-y89pui/), and the destination needs an effort pool for each of them. If a task has 4 hours of Copywriting on it and the destination Deliverable has no Copywriting pool, the move is refused and the panel tells you why. Net Net is not being fussy here. If it let that move through, those 4 hours would land in a Deliverable that never budgeted for that kind of work, and the Deliverable's numbers would stop meaning anything. Quietly parking unbudgeted work somewhere is exactly the drift Net Net exists to prevent. ||| If you hit this, you have two honest routes. Change the allocation's service type on the task first, if the work genuinely was a different kind of work than it was filed as. Or add that service type to the destination Deliverable with a [Change Order](https://help.netnet.app/en-us/article/change-orders-how-to-add-scope-to-a-locked-job-plan-1gplwsw/), if the destination really should be carrying this work. Either way you end up with a plan that matches reality, which is the point. # What Move task does not do Worth being direct about the edges, so you are not hunting for something that is not there. - **It does not move a task out of a Deliverable into General Job Tasks.** You can move a General Job Task into a Deliverable, but not the other way around - **It does not convert between Quick Tasks and Job Tasks.** Quick Tasks are standalone personal work with no Job attached, and Net Net has no conversion between the two anywhere: not in the row menu, not in the task itself, not anywhere else in the product. [Quick Tasks vs Job Tasks vs My Lists: Which to Use](https://help.netnet.app/en-us/article/quick-tasks-vs-job-tasks-vs-my-lists-which-to-use-1hlzaoy/) explains where each one belongs - **It does not move a task into a Pending Job.** A Job that has not been activated has no live plan to receive work, as described in [Job Lifecycle: Pending, Active, Completed, Archived](https://help.netnet.app/en-us/article/job-lifecycle-pending-active-completed-archived-1jvg51y/) # Frequently Asked Questions ###### Will I lose the time logged against a task if I move it? **No. Every time entry moves with the task, every time.** The source Deliverable's actual hours drop by exactly what the destination's rise by, and the Job's total is unchanged. No entry is split, orphaned, or deleted. ###### Where is the Move task option? **In the ⋮ menu on any Job Task row, on the Tasks tab of the Job.** It sits alongside Edit details and Delete. It works on tasks inside a Deliverable and on tasks in General Job Tasks. ###### Can I move a task to a different Job? **Yes. Choose Move to another job in the panel, then pick the destination Job and a Deliverable inside it.** The task keeps its identity, its status, its assignees, and all of its logged time. ###### Why is my move being refused? **Almost always because the destination Deliverable does not have an effort pool for one of the task's service types.** Either change the allocation's service type on the task, or add that service type to the destination Deliverable with a Change Order. ###### Does moving a task change its status or its dates? **No. Status, due date, start and completion timestamps, title, description, and assignee allocations all stay exactly as they were.** The only things that change are the Job and the Deliverable the task belongs to. ###### Can I turn a Quick Task into a Job Task? **No. There is no conversion between the two, by any route.** Move task works between Deliverables and between Jobs. Quick Tasks stay standalone, and Job Tasks stay attached to their Job. ###### Is moving tasks around a bad sign? **No, it is a normal part of running a Job.** Scope gets restructured, work turns out to belong somewhere else, and things get filed in a hurry. Moving is how the records stay honest when that happens. The alternative, leaving work in the wrong place, is what actually damages your numbers. # Related articles Moving is one of several things you can do from a task row, and [Job Tasks: Assignees, Allocations, and Statuses](https://help.netnet.app/en-us/article/job-tasks-assignees-allocations-and-statuses-1fy1ov5/) covers the rest of them. When a move is refused, [Deliverables: Status, Due Dates, and Confidence Explained](https://help.netnet.app/en-us/article/deliverables-status-due-dates-and-confidence-explained-x7yi7t/) explains how a Deliverable's effort pools are put together and [Which Tasks Can Accept Time (and Which Cannot)](https://help.netnet.app/en-us/article/which-tasks-can-accept-time-and-which-cannot-ykihm4/) explains which rows will take time once the task lands. If you were hoping to delete rather than move, [Why Some Things Can't Be Deleted: Archive, Retire, Move](https://help.netnet.app/en-us/article/why-some-things-cant-be-deleted-archive-retire-move-si6k0l/) explains why removing work outright is usually the worse option.