Moving forms between team folders in Dashpivot lets you tidy up your workspace, correct misplaced forms, or restructure projects as they evolve — without needing to contact support.
How It Works
Open the form you want to move
Click the Move button in the form modal
Select the destination team folder from the dropdown list
Confirm the move
The form will be relocated instantly, and the move will be recorded in both the folder activity feed and the form's activity feed.
Note: Only team folders where the template is already deployed will appear in the destination list. If your form hasn't been saved yet, you'll be prompted to save it before completing the move.
Who Can Move Forms?
Your ability to move forms depends on your role and whether you created the form:
Your Role | Moving Your Own Forms | Moving Other People's Forms |
Org Controller | ✅ Can move to any team folder in the workspace | ✅ Can move to any team folder in the workspace |
Project/Team Controller | ✅ Can move between folders you have access to | ✅ Can move between folders you control |
Member | ✅ Can move between folders you have access to | ❌ Cannot move other people's forms |
Requirements & Limitations
✅ What You Can Move
Forms created from org-level templates only
Archived forms (the form will remain archived and will move to the Archived tab of the destination team folder)
❌ What You Cannot Move
Forms created from team-level templates
Forms to team folders where the template hasn't been deployed
Forms where a selected list item is only available in the source project and not in the destination — remove the affected selection first, then try again.
Forms with a Relationship field or an Actions field
Note: Moving a form between team folders within the same project is always permitted, regardless of list field configuration — list availability is identical across all teams in the same project.
💻 📱 Platforms
Available on web
Availability on the mobile app is coming soon
❓ Why Can't I See the Move Button?
The Move button will only appear if you have the appropriate permissions (see table above).
Why Are No Permitted Team Folders Found
If the destination list is empty, it means there are no team folders that meet the conditions for a move:
The form's org-level template must be deployed to the destination folder, and
You must have permission to move forms into that folder (see the table above for more details)
Here are the most common reasons, and what to do about each:
The template hasn't been deployed anywhere else yet
Ask your Org Controller to deploy it to the folder you want to move the form to — once it's deployed, the folder will appear in the list.
You don't have access to the folders where it is deployed
The template may be deployed to other folders that you can't see. If you think you should have access to a folder that isn't listed, contact your Org Controller.
Frequently Asked Questions
Q: Can I move a form to a different workspace?
A: No, forms can only be moved between team folders within the same workspace.
Q: Will my form data be affected by moving it?
A: No, all form data remains intact. Only the folder location changes.
Q: What happens when I move an archived form?
A: The form remains archived and will be placed in the Archived tab of the destination team folder.
Q: What if I haven't saved my form yet?
A: You'll be prompted to save the form first. Simply confirm to save and move in one step.
Q: Why am I getting an error about list field values when trying to move a form?
A: This error occurs when your form contains a list field selection that isn't available in the destination project. To resolve this, remove the affected list selection from your form and try again.
Q: How can I track when forms were moved?
A: Form moves are logged in both the folder activity feed (available at home, project, and team folder levels) and the form's activity feed within the form modal. Both show who moved the form and when.