Here is the showcase of how to proceed list migration across SharePoint Online site collections with the Virto Backup & Recovery solution.

The starting point of the list migration process is like that:

Home Case Studies Nonprofit Benefits From Modern Features After SharePoint Migration Nonprofit Sees Immediate Benefits of SharePoint Migration This nonprofit, consulting industry customer provides services to the civic sector with a focus on solutions that improve the quality of life for those in need. We are frequently asked for guidance on Testing Plans for SharePoint Site Migrations, so have put together this general guidance. While the complexity and nature of migration projects vary massively, and the implications naturally vary with each use-case, we have compiled this list of tests that are generally worthwhile in most migration scenarios.

  1. Save the required SharePoint list as a template (List settings -> Save list as template);
  2. Download the saved template from the List Template Gallery;
  3. In List Template Gallery, upload the list to the site collection, that is supposed to restore the list.

Relative Site Url
/
/subsite
/sites/testsite

Sharepoint Migration Test Cases List

The final content of the xml file TestConfig.xml:

<GlobalOptions xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<Recursive>false</Recursive>
<SiteOwners>false</SiteOwners>
<WebContentTypes>false</WebContentTypes>
<WebLists>true</WebLists>
<WebRoleAssignments>false</WebRoleAssignments>
<Webs>
<ServerRelativeUrl>/sites/b</ServerRelativeUrl>
<ListBackupConfig>
</ListBackupConfig>
<Title>Test_List_2</Title>
</Lists>
</Webs>
</BackupConfig>
</RestoreConfig>

Now run cmd.exe (win -> cmd.exe), and go to the folder with the utility Virto Backup & Recovery.

(Using VS Code, you can press F1, type “Create new integrated terminal” and press enter)

Run virtobr.exe with parameters:

virtobr.exe -o backup -s https://testportal.sharepoint.com/sites/b -d c:TestBackup -u mylogin@testportal.com -p MyP@$sWoRD1 –ConfigPath TestConfig.xml

-o: the type of operation being performed (backup, recovery)

-s: site address (or a folder address for recovery operation)

-d: folder address (the site address for recovery operation), where the backup will be saved (folder will be created automatically with TimeStamp added (e.g. TestBackup_201608251011))

-u: user login to connect to SharePoint

-p: user password to connect to SharePoint

–ConfigPath: The name of configuration file (if you do not specify the name, default Config.xml will be used)

As a result, the folder (such as TestBackup_201608251011) will be created, that will contain the backup files.

You need to run the utility once again with a few changes to restore (move) saved lists to this folder:

virtobr.exe -o recovery -s “c: TestBackup_201608251011” -d “https://testportal.sharepoint.com/sites/c” -u mylogin@testportal.com -p MyP@$sWoRD1

Type recovery as the operation (-o). The backup folder address is the source (-s), and the destination (-d) is the address of site collection where I need to restore backup.

After the recovery is done, check the result:

As you can see, we have items with restored Lookup and Person fields.

You can download and use Virto SharePoint Online Backup & Recovery solution and try its 30-days free trial as well.

Related Products:
SharePoint Online Backup

What will you do first when you understand that your SharePoint environment requires an upgrade? Many SharePoint administrators start the upgrade and migration without much preparation expecting better results from the new version of SharePoint. But, their expectations are not met easily as a SharePoint environment is more complicated than one imagines – it has sites, lists, libraries, site collections, etc. Every new version of SharePoint brings compelling features which any business will like to implement. But improper planning and migration can ruin an upgrade attempt completely.

There are different factors which you need to consider before upgrading your SharePoint environment. Before you upgrade, check your environment by following the best practices –

  1. Conduct a full survey of your current SharePoint environment

    Check the hardware and software configuration and enlist their features and settings. It will help you to manage the environment and use resources effectively. It will also help you to restore the SharePoint if the upgrade fails.

  2. Perform a test upgrade

    Performing a test upgrade will help you identify the possible issues during the actual migration. Try to use the same kind of hardware, URLs, and configuration in the trial environment as in the current environment. It will reduce the differences between the current environment and the destination environment and will facilitate smooth migration during the trial and the actual migration.

  3. Try to use actual data

    When you run a test migration, try to use copies of actual databases. When you use the actual data from the database, you will get to know of the probable troubles, and you can fix them easily. Try to use a small amount of data to run the test migration. To test the complete data, you can run test migrations multiple times.

  4. Run trial migrations multiple times

    Running trial migrations multiple times will help you understand all the possible outcomes and any potential issues. Also, you will get insights into the best migration approaches to apply and mitigation techniques to follow to reduce the chances of errors.

  5. A trial migration will let you have an idea about the following parameters –

    • Time taken to complete the migration.
    • The condition of SharePoint data in the destination environment.
    • Time taken to complete the post-migration troubleshooting.
    • The appearance of sites, subsites, and other data.
  6. Make sure your SharePoint environment is working properly

    An upgrade of SharePoint environment has several advantages; but it will not help you overcome the shortcomings in the current setup. So before starting the migration, you should ensure that your SharePoint environment is working completely fine and there is no such shortcoming which will impact the migration. For example, if you have any web application which you are not using and does not plan to use in the new environment, then you should remove it from the environment.

  7. Backup your SharePoint database

    Before migration, back up your SharePoint database completely. This way, you can retrieve your data in case the migration fails.

  8. Discard unwanted data

    Discarding unwanted data is a useful option as it allows you to migrate only the desired data.

  9. Look for professional SharePoint migration tools

    For actual SharePoint migration, you can use professional SharePoint migration tool. Kernel Migrator for SharePoint is a proficient tool which lets you conduct to-and-fro migrations between different SharePoint versions (2016,2013,2010). It migrates entire SharePoint data (including sites, subsites, lists, libraries, etc.) with metadata and permissions.

×
Sharepoint migration tools

Sharepoint Migration Test Cases John Hopkins

Conclusion

Sharepoint Migration Test Cases Study

Upgrading SharePoint to the latest version will bring best results if done correctly. But you need to understand your current environment, future requirements, and possible issues before initiating the upgrade process. However, analyzing your environment requires a lot of time, energy, and resources.