How To Merge Projects

Agencies routinely run the same website more than once in Atarim — a staging project, a development project, and the live site. Feedback accumulates on whichever one the client was looking at, and ends up scattered.

The merge tool solves that by moving or copying tasks from one project into another, rewriting each task so it points at the destination site. Atarim describes it as ideal for moving tasks from staging to development sites, and then on to live.

Who this is for

Merging is a paid feature, and it is also permission-gated. The menu item appears greyed with a plan badge if your plan does not include it, and does not appear at all if your role lacks the merge permission.

Selecting a locked Merge Sites item opens an upgrade panel describing the feature as combining tasks from staging and live URLs into one project, keeping historical feedback while avoiding duplication.

Copy or move — choosing the right mode

The tool offers two modes, and the difference matters. Choose before you select your projects.

Opening the merge tool

Instructions:

1. Go to Projects and open the actions menu in the top bar. The menu lists project-level actions including Merge Sites.
2. Select Merge Sites. The modal opens, with the mode buttons at the top, the From and To selectors below, and a help icon linking back to this article.

Copying tasks to another project

Use this when you want the feedback in both places — for example carrying a round of staging feedback onto the live project while keeping the staging record intact.

Instructions:

1. In the Merge Sites modal, select Copy Tasks. The Copy option is highlighted, and the action button at the bottom right reads Copy Tasks.
2. Open the From selector and choose the project the tasks are currently on. Projects load in batches as you scroll, showing Loading projects while they fetch. The source must contain at least one task.
3. Open the To selector beneath the arrow and choose the project you want the copies to land on. The action button becomes available once both are selected.
4. Check the direction of the arrow between the two cards, then select Copy Tasks. A confirmation reads Sites merged successfully.
5. Open the destination project and spot-check a few tasks. Copied tasks carry their comments and now point at the destination site.

What to expect after copying

• The source project is untouched. Every task stays exactly where it was, with everything attached to it.
• The destination gains duplicates of the tasks, each with its comments.
• Tags, attachments, subtasks, and logged time are not duplicated. Copies arrive with the task text and its conversation only.
• Pages are copied too, whether or not a matching page is already on the destination.
• Task page titles are rewritten to the destination project’s name.
• Running it twice copies everything twice. There is no duplicate check — a second copy recreates every task and page again, alongside the first set.

Moving tasks to another project

Use this when you are consolidating — retiring a staging project, or cleaning up a duplicate you no longer need.

Instructions:

1. Before you start, confirm you no longer need the source project as a separate record. A move cannot be reversed in one action, so this is the point to change your mind.
2. In the Merge Sites modal, select Move Tasks. The Move option is highlighted, and the action button at the bottom right reads Move Tasks.
3. Open the From selector and choose the project you are emptying.
4. Open the To selector and choose the project everything should end up on. The action button becomes available once both are selected.
5. Read the two cards once more, top to bottom, then select Move Tasks. A confirmation reads Sites merged successfully.
6. If you no longer need the empty source project, delete it separately. Merging never deletes anything, so the source remains on your projects list until you remove it.

What to expect after moving

• The source project is left empty. Both its tasks and its pages transfer to the destination.
• Everything attached to each task comes with it — comments, tags, attachments, subtasks, and logged time — because the original task is transferred rather than recreated.
• Task page titles are rewritten to the destination project’s name.
• Task URLs are rewritten so the source domain is replaced with the destination domain.
• The source project still exists on your projects list until you delete it yourself.

What transfers, and what changes

Merging does more than reassign tasks. Each transferred task is rewritten to belong to the destination.

Known limitations

• There is no undo. Neither a move nor a copy can be reversed from the dashboard.
• You cannot choose which tasks transfer. The tool works on the whole project — there is no way to select a subset.
• Copying does not duplicate tags, attachments, subtasks, or logged time. Only the task and its comments are recreated.
• Nothing is deleted. If your goal is to remove the source project, you must delete it separately afterwards.
• Both projects must be in the same workspace. There is no cross-workspace merge.

FAQs

Common issues

• Merge Sites is missing from the menu. Your role does not carry the merge permission. Ask an administrator to grant it.
• Merge Sites shows a plan badge and opens an upgrade panel. Merging is not included on your plan. The panel names the minimum plan required.
• Nothing arrived on the destination. Check that the source project has at least one task, and that you picked two different projects in From and To.
• The action button stays greyed out. Both a source and a destination must be selected before it becomes available.
• A project is missing from the selector. The list loads in batches — keep scrolling. Also confirm the project is in your current workspace.
• Tasks arrived but point at the wrong page. The URL rewrite swaps the source domain for the destination one. If the two sites have different page structures, some tasks may land on pages that do not exist.
• Copied tasks are missing tags or attachments. Expected. Copying recreates the task with its comments only. Use Move if you need tags, files, subtasks, and logged time to come across.
• More tasks arrived than expected. Every copy brings the whole project across. If you have copied this project before, the destination now holds both sets — delete the extras by hand.
• The merge failed outright. Confirm both projects still exist and are in the same workspace, then try again. If it persists, contact Support.

Conclusion

Merging is the difference between carrying a client’s feedback forward and retyping it. Copy when you want the history in both places, move when you are consolidating, and remember that neither can be undone — so check the direction of the arrow before you confirm.

Learn About Managing Multiple Projects