Skip to main content

Essential Considerations: Preparing for a Smooth SharePoint Data Migration

I have recently completed a content migration within the same tenant, transferring data from one site to another. During this process, I encountered several challenges. 

Based on my experience I created a checklist specifically for SharePoint content migration. Utilizing this checklist can assist in mitigating challenges and ensure a smoother migration process for you.

Embarking on a SharePoint content migration journey? Make sure to explore the following points to ensure a seamless transition:

  • Storage: When dealing with migration on SharePoint, it is crucial to verify the available storage space on the site. Insufficient storage can pose a problem during data movement, potentially causing SharePoint to transition into a read-only mode. It is essential to preemptively address and ensure adequate storage to avoid such issues during the data migration process.
  • Policies: Examine the policies in place on the tenant. Organizations occasionally establish policies to protect data from actions such as moving, copying, and deleting. These policies impose restrictions on users and trigger notifications to designated individuals if notifications have been configured, particularly in instances where such operations are performed
  • Workflows: Transferring libraries/folders from one site to another can potentially disrupt the workflows in which they are employed. It is essential to identify these workflows and devise a strategy for addressing any issues that may arise.
  • Copying or Moving: Choosing between moving and copying data involves a decision. Opting for data copying helps prevent data loss, albeit at the expense of requiring additional storage space.
  • Choosing between copying both the structure and content or just copying the content. This decision is influenced by scenarios where legacy data is absent in the structure, especially in libraries with a substantial amount of data. In such cases, it is advisable to create the structure first and then move or copy the data into smaller portions. This chunk-wise copying approach facilitates the creation of accurate reports and allows for the timely identification and resolution of any issues. However, for libraries or folders with limited data, it is preferable to opt for copying both the structure and content.


Labels:

Comments

Post a Comment

Popular posts from this blog

SPFx Interview Questions With Answers

In this article, we are going to discuss interview questions related to the SPFx (SharePoint Framework Development ). It will help you to prepare for the interview and in getting clarity on the core concepts of SPFx development. What is SPFx? SPFx, short for SharePoint Framework,  SPFx  allows us for client-side SharePoint development, we can easily connect with SharePoint data and it also supports for open source tools. What is the major difference between SPFx web part and the SharePoint app? Both the development model supports client-side development but the major difference between these two is that the SharePoint app(add-in) runs on the iframe. What you can build with SPFx? Using SPFx framework we can customize the SharePoint pages. We can build things mentioned below using the SharePoint Framework(SPFx). Web parts, Extensions, Adaptive Card, Library Component How many types of extensions we can create using SPFx? SPFx has three extension types: Application Customizers: U...
2 comments
Read more

How to Upgrade SharePoint Web Parts to the Newest Version

Updating the SharePoint/SPFx web parts or other solution is very common requirement, Webparts we can add from the SharePoint store or can be uploaded by our organization. To update a SharePoint web part to the latest version, start by uploading the updated SPFx package to the App Catalog. Then, make sure to upgrade the web part on the site where it’s being used. In this blog will be discussing ways to upgrade both package from the SharePoint app store or the the custom uploaded from the organization Update the web part added from the SharePoint app store: Go to the tenant level app catalog site. Select the app which you want to upgrade. Once you select the app, go the top ribbon and select file and click on the "Upgrade Store App", updated version will be added on the appcatalog if the new version is available on the store. Note: If you built the custom webpart then upload it to the app catalog. Install the upgraded solution: Navigate to the site collection where you have ins...
Post a Comment
Read more

SharePoint Framework SPFx Node Version Compatibility

How to check the compatibility between the SPFx version and the Node.js version The SharePoint Framework (SPFx) is a client-side development platform used to develop web parts and extensions for SharePoint. The SharePoint Framework (SPFx) is compatible with the Node.js versions. Existing SPFx solutions may have different SPFx versions as compared to the current solutions. To make the SPFx solution run, Node.js is required, and in this blog, I am sharing steps to check the compatible node module for SPFx.  Find the SPFx version from the solution:  Open the project solution and navigate to the "package.json" file. In package.json file you will find  "@microsoft/sp-core-library" key and value of this particular key is the version of the SPFx.       Ex:    "@microsoft/sp-core-library": "1.14.0" Another way to find the SPFx version is by command, open the command prompt and run the command mentioned below: npm ls -g --depth=0 @microsoft/generator-s...
Post a Comment
Read more