Transferring a published form template in SharePoint to a different library is a common task for administrators and Power Users aiming to reorganize or update their forms. This guide covers practical, step-by-step methods to move form templates without losing data or breaking form functionality. Whether you’re managing large enterprise forms or small departmental templates, these approaches will help you ensure a smooth transition and maintain form integrity across SharePoint libraries.
1. Use Power Automate to Copy and Re-publish the Form
Power Automate offers a flexible way to duplicate a form template from one SharePoint library to another. You can create a flow that triggers when a new item is added or manually run to copy the form file (.xsn or .xml) and associated data. After copying, you’ll need to re-publish the form in the new library, ensuring it is accessible and functional for end users. This method is especially useful for automating repetitive moves across multiple environments or libraries.
2. Download and Upload the Form Template Manually
The simplest approach involves downloading the form template file directly from the original library and uploading it to the new location. To do this, locate the form’s .xsn or .xml file in SharePoint, download it, then navigate to the target library and upload the file. Once uploaded, you may need to reconfigure the form’s settings or re-publish it, depending on your SharePoint environment. This method is straightforward but best suited for occasional moves or small-scale migrations.
3. Use SharePoint Designer to Reassign the Content Type
SharePoint Designer can be employed to change the content type associated with the form, effectively moving the template between libraries. Open SharePoint Designer, connect to your site, and navigate to the list or library containing the form. You can then modify the content type settings to point to the new form location. This approach is useful when managing multiple forms linked to content types, ensuring consistency and reusability across libraries.
4. Employ PowerShell Scripts for Bulk Migration
For administrators handling large numbers of forms, PowerShell scripts provide a scalable solution. Using SharePoint PnP PowerShell modules, you can script the export and import of form templates, preserving metadata and version history. Scripts can be customized to target specific libraries or content types, automating the move process and reducing manual effort. This method is best suited for complex migrations or regular form management tasks.
5. Re-create the Form in the New Library
If moving the form proves too complex or risks breaking dependencies, re-creating the form using Power Apps or InfoPath in the new library might be preferable. This involves designing a new template that mimics the original, then redeploying it to the target location. While more time-consuming, this ensures the form is optimized for the new environment and can leverage new features or updates.
6. Use the Save as Template Feature in SharePoint
SharePoint allows saving a list or library as a template, which can include form templates if configured correctly. Save the original library as a template, then create a new library based on that template in the desired location. This method copies all associated forms and settings, simplifying the migration process. However, it may not be suitable for highly customized or complex forms that rely on specific workflows or data connections.
7. Leverage Content and Structure Tool for Site Collection Migration
The Content and Structure tool in SharePoint Server or SharePoint Online Management Shell enables moving entire libraries or content across site collections. This is effective when the form library is part of a larger migration project. It preserves permissions, metadata, and version history, making it ideal for maintaining consistency. Note that this tool requires appropriate permissions and careful planning to avoid data loss.
8. Use Third-Party Migration Tools
Several third-party tools like ShareGate, AvePoint, or Metalogix offer user-friendly interfaces for migrating SharePoint content, including form templates. These tools can handle complex migrations with minimal manual intervention, often providing options to preserve metadata, workflows, and permissions. They are particularly valuable in enterprise environments where multiple forms and large data volumes are involved.
9. Export and Import Form Data Separately
In some cases, moving just the form data (responses) separately from the template can be beneficial. Export responses from the original library using SharePoint list export options or PowerShell, then import them into a new list or library with the re-deployed form. This approach keeps the data intact while allowing you to update or change the form template as needed.
10. Use Managed Metadata to Link Forms Across Libraries
Implementing managed metadata or content type hubs allows you to centrally manage form templates and link them across multiple libraries. Instead of physically moving the form, you update the content type or metadata reference, and the form remains consistent regardless of location. This strategy simplifies ongoing management and ensures uniformity across SharePoint sites.
How to Choose
When selecting the best method to move a published form template, consider the size and complexity of your forms, the frequency of moves, and your technical expertise. Manual uploads are quick for small, infrequent moves, while Power Automate and PowerShell excel for automation and bulk migrations. SharePoint Designer and third-party tools offer more control for complex scenarios. Always evaluate dependencies like workflows, data connections, and permissions before proceeding to avoid breaks or data loss.
Frequently Asked Questions
Can I move a form without losing responses? Yes, but it depends on your approach. Export responses separately before moving the form, then import them into the new library.
Will moving a form break its workflows or data connections? Potentially, yes. Ensure you update any references or connections after moving to maintain functionality.
Is there a risk of losing version history when moving a form? Yes, especially with manual uploads. Using PowerShell or third-party tools can help preserve metadata and version history.
Can I automate the entire move process? Absolutely. Power Automate and PowerShell scripts can streamline moving multiple forms or large libraries with minimal manual steps.
What are the best practices for moving forms in SharePoint Online? Back up your data, test the move in a development environment, and verify permissions and dependencies post-migration.
Final Thoughts
Moving a published form template in SharePoint requires careful planning and the right tools to ensure data integrity, functionality, and minimal downtime. Whether you choose manual methods or automation, understanding your environment’s specific needs and dependencies is key. With the right approach, you can reorganize or upgrade your forms seamlessly, maintaining a smooth user experience and preserving critical data assets.
Related
- Use Data to Forecast Resource Demand in Project Online
- Use Data Bars, Color Scales, and Icon Sets to Highlight Data
- Use Custom Templates in Microsoft Planner for Better Workflow