Items in Craft.io live within a Product, inside a Workspace. When your team restructures, hands off ownership, or needs to replicate work across teams, you can move or copy items from one workspace to another - individually or in bulk.
This is useful for teams running a centralized intake or triage workflow - items are validated in one workspace and moved to the relevant delivery workspace when ready.
Move or copy - which one to use
Move an item when you want to permanently relocate it. The item is removed from the source workspace and lives only in the destination. Use this when:
Ownership of a feature or Epic is transferring to another team
You are reorganizing products across workspaces after a restructure
The item was created in the wrong workspace
Copy an item when you want to duplicate it without removing the original. Use this when:
You want to use an item as a template in another workspace
Two teams need to work independently on similar scope
You are setting up a new workspace and want to replicate existing structure
Moving a parent item (e.g an Epic or Feature) automatically moves all of its child items with it. You do not need to select children separately.
Move or copy a single item
Open the item panel or locate the item in any view
Click the three-dot menu on the item
Select Move to or Copy to
Choose the destination Workspace and Product
Confirm your choice via the Move or Copy action
Moving a parent item moves all its child items with it.
Move or copy items in bulk
Bulk moving and copying works through the Multiple fields editor in the bulk action toolbar.
Items must be at the same hierarchy level - select only Epics, only Features, or only Sub-stories. If you mix levels, the workspace option will not appear.
Follow these steps:
Select the items you want to move or copy - check the boxes in any list or board view
Click Multiple fields in the bulk action toolbar at the bottom of the screen
Find the Product field and click it
Choose the destination Workspace via the dropdown and select a Product
Select Move or Copy and confirm your choice
What carries over to the other Workspace
What carries over
Title and description
Any custom Portfolio field values if the original and destination workspaces are part of the same Portfolio
Child items (when moving or copying a parent)
Jira connection - if the destination workspace is connected to the same Jira project, the item will reconnect to its Jira issue on the next sync
Link to the original source item and pieces of feedback connected to the historic item (see below)
What does not carry over
Assignee - this resets in the destination workspace. This is by design, as the user may not be a member of the destination workspace
Workspace-level fields - these are specific to the source workspace's portfolio and do not transfer
Products - these cannot be moved across workspaces. You will need to manually create the Product in the destination workspace in order to move the Epics and items into it
Note, synced items with active Jira or ADO connections may need to be manually re-checked after the move
What comes next?
Learn about using bulk actions in your table view to quickly update field values of multiple items
Learn how to connect and promote feedback items to your backlog
Need more guidance? 🙋 Our LIVE support team (at the bottom right corner of your screen) replies to ANY question!