Migrate the SharePoint On-premises InfoPath Forms which are build on 2007/2010/2013 to SharePoint Online / Office 365 / O365.
By using the below steps we can use the InfoPath Forms as it is with out converting to 3rd party solutions.
We can categorize the Forms into 2 Types.
By using the below steps we can use the InfoPath Forms as it is with out converting to 3rd party solutions.
We can categorize the Forms into 2 Types.
- Forms Without Code Behind
- Forms with Code Behind
Steps to Migrate the InfoPath Forms Without Code Behind to SharePoint Online
- Download the Form Template.
- Open Template using InfoPath Designer.
- Create New Form Library at SharePoint Online.
- Update the Data Connection to Pointing to the New Form Library.
- Publish it to the SharePoint Online.
- Migrate the Forms using Migration Tool.
- Test it.
Steps to Migrate the InfoPath Forms With Code Behind to SharePoint Online
At On-Premises
- Create new Form Library.
- Download the Template from old library.
- Remove the Code Project.
- Update the Data Connections and others if required.
- Change the security settings to “Automatic”.
- Publish it to new library set Publishing scope to “Form Library” and make sure to select the “Enable this form to be filled out by using a browser”.
- Update and run the PowerShell to copy and update the forms. PowerShell will do the below actions.
- Copy the documents from old library to new library.
- Update the People Picker field values.
- Update the Form Template Url.
- Set the Metadata (Created, Modified, Author, Editor).
At O365
- Update the Data Connections (We can use both inline or UDCX).
- Update the Form Name field (if required).
- Note: since we are using the “User Name” value for Form name fields. User Name is different from On-Premises to O365.
- Create New Form Library.
- Publish it to new library.
- Update the below library settings.
- Set Allow Management of Content Types to “Yes”.Set Default Open behavior to “Use the Server Default”.
- Migrate only Items using Content Matrix.
- Republish it (if required).
0 comments: