Troubleshooting web part migration issues (4311881)

When running SharePoint migrations, one or more of the following issues may be encountered when copying web parts:

1. Web parts are missing on the target page, but no error appears in the migration logs.
2. Web parts failed to copy with logged errors.
3. Web parts copied, but are out of alignment on the target page.
4. Web parts are duplicated on the target page.

There can be many possible reasons for the issues described above. Here are some of the more common causes.

1. The web parts may have copied, but are not visible on the target page. To verify, go to the web part maintenance page by adding ?contents=1 to the end of the URL. For example, http://target-web-app/sites/target/SitePages/Home.aspx?contents=1.
    
2. The most common causes of web parts failing to copy are:
   • It is a list view web part and the list does not exist on the target site.
   • It is a third-party web part and the assemblies are missing on the target environment. Note that migration of third-party web parts are not supported by Content Matrix.
3. The most common causes of web part misalignment are:
   • There is a mismatch between the source and target web part pages. The web part zones are not configured identically.
   • The source is a web part page, while the target is a wiki page.
4. This is caused by a setting in the job configuration.

Here are some actions/suggestions for troubleshooting web part issues. Note that it is recommended to be on the latest version of Content Matrix to take advantage of all recent fixes.

1. Web parts are not visible on the target page
   • If the web parts are visible only within the web part maintenance page, there is most likely a zoning issue between the source and target pages. Make sure that the source and target pages are using the same page layout and that the page layout is identical between source and target. You may need to run a migration to copy the master page gallery to bring custom page layouts over from source.
   • If the web parts do not show up in the web part maintenance page of the target, try making a new connection to the source environment using a different adapter type, and then recopy the web parts. For instance, instead of using a DB connection, use a Remote Connection (Metalogix Extensions Web Service).
     
     
2. Web parts fail to copy
   • Copy the site, which the web part is pointing to, and then recopy the web parts.

     Note: Make sure to enable the Advanced Mode on the Settings tab of the Content Matrix Console to see all the other context menu options.

     
     
      
   • Install all necessary web part assemblies on target farm prior to migration.
3. Web parts are misaligned
   • As in section 1, try migrating the page layouts to ensure target page layout is identical to the source page layout.
   • If the target is a wiki page, below are two possible solutions:
     1. When migrating a site, choose the option "Clear Default Features on Target" under Migration Options > Site Options. This option prevents the "Wiki Page Home Page" feature from being activated, which results in the target page using a Wiki Page layout instead of the standard Web Part Page layout. The Wiki Page layout contains a Content Zone, which does not exist in a Web Part Page.
        
        
         
     2. Try copying the web parts (Copy Site / Paste Site Objects > Web Parts) using a different target connection adapter. For instance, if you are connected to your target using Remote Connection (Metalogix Extensions Web Service), try to connect using the Client Side Object Model connection type instead.
        
        
         
4. Make sure that you set the Web Part Options in the job configuration to "Delete Existing Web Parts on Target".
   
   

   Note: Make sure to enable the Advanced Mode on the Settings tab of the Content Matrix Console or on the job configuration window to see all the job configuration options.