Prepare for SharePoint 2010 with a pre-upgrade test

Use SPD2007 to backup a site as a .cmp or set of .cmp packages.

Then use this WPF application or perform the following manual tasks:


1. Rename the extension from .cmp to .cab (teamsite.cmp to for example).
2. Extract all files from the .cab package.
3. Create a new CAB Project in Visual Studio.
4. Add extracted files from the .cab package to the new CAB Project.
5. Edit SystemData.xml Version from to Change Build to 14.0.6029.1000.
6. Edit Manifest.xml by deleting SPObjects for features that do not exist in the SP2010 environment.
7. Edit Requirements.xml by deleting SPObjects for features that do not exist in the SP2010 environment.
8. Build the solution.
9. Change the extension for the new .cab package from .CAB to .cmp.

Use Powershell to import the reformatted package into a SP2010 site of the same type.

If the import is successful…

1. You will be able to access the new site by navigating to the home page in the browser (…teamsiteSP2010/default.aspx). Images and styles will be missing from the page, but do not worry about it. Once you change the default master page to v4.master, the home page will be /SitePages/Home.aspx.
2. Open the new site in SharePoint Designer 2010.
3. If default.aspx has been customized, copy the scripts into /SitePages/Home.aspx.
4. Change the default master page from default.master to v4.master (r-click on Master Pages > v4.master and select “Set as Default Master Page”).
5. Confirm that you can access the new site by navigating to the site root in the browser.
6. Don’t expect custom list forms, workflows and dataview web parts to work. Microsoft’s standard upgrade process addresses these.

Customizations that may need your attention

1. JQuery will have to be reworked on all customized pages and forms because content is rendered differently in SP2010.
a. JQuery and SPServices Web Service calls that target the People Picker will have to account for unresolved (Daniel, Neal W) and resolved ( Daniel, Neal W ;) rendering of people and groups.
b. JQuery that targets DOM elements will have to be rewritten due to differences in ids, classes, tables, and divs.
c. References to the JQuery library will be broken because the file structure is different.
d. Any JQuery on default.aspx will have to be transferred to /SitePages/Home.aspx.
2. The upgrade process will fix custom list forms, but, for our test all customized list forms will have to be recreated as modal dialog boxes.
3. The header and footer for DataView Web Parts are different in SP2010. The upgrade process will address this, but, for the pre-upgrade test all DataView Web Parts that have been customized in SP2007 will fail to recognize their data sources. This can be resolved manually by creating a DataView Web Part in SPD 2010 with the desired data sources, and then replacing the XSL portion with the customized XSL.
4. The upgrade process will convert custom workflows from ASPX to InfoPath. For the pre-upgrade test, however, you will have to rebuild the workflow in SPD 2010.
5. The upgrade process will create necessary SPGroups, but, for pre-upgrade testing you must create these.
6. ASPX pages (dashboards) that have JQuery, DVWPs or Web Parts must be fixed.
7. Personal list views will have to be recreated.

Last edited Sep 27, 2012 at 4:45 PM by webpilotforever, version 8


No comments yet.