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.


Comments

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: Using the

How to register an app in SharePoint

In this article, we are going to learn how to register an app/add-in in SharePoint online. If you have created a Sharepoint provider-hosted add-in or other SharePoint solution and to access the SharePoint site or list using the app/add-in you need to register the add-in on SharePoint and to grant permission. Register app in SharePoint 1. Login into SharePoint and Navigate to register an app page. Use the URL mentioned below:          [Sitecollection URL]/_layouts/15/appregnew.aspx 2.  Once you navigate to the Register app page, a form will open. You need to fill all the fields on the form. Client Id and Client Secret  generated when we click on the generate button available next to the fields.  Title : Name of the add-in which you want to give. App Domain : Where your domain is hosted, for the local environment you can place             "www.localhost.com". Do not include HTTP or HTTPS in App Domain. Redirect URL :  Insert the redirect URL, for t

Permission XML for SharePoint Add-in

In this article, we will be discussing the permission XMLs, which are used to provide permission to SharePoint add-in. Permission XML for the SharePoint app. You can set the App only permission, by setting "true" or "false" in  AllowAppOnlyPolicy=“true” in these permission XMLs.   If add-in granted permission to tenant scope, It includes all children in scope. Before granting access to the app, need to register an app. Follow this link for step by step guide to  How to register an app/add-in in SharePoint   Providing access to add-in at tenant level: To provide access at tenant level user must have the tenant admin level permission. To grant this permission tenant admin can use this URL   https://tenantName-admin.sharepoint.com/_layouts/appinv.aspx Search the App Id (Client ID) and it will fetch all the information which you provide at time of registration of app.   Assign full control at tenant level : <AppPermissionRequests AllowAppOnlyPolicy="true&quo