Migrate from SharePoint 32-bit environment to 64-bit environment

While migrating from a 32-bit environment to 64-bit environment, a common issue arises as to custom and third party assemblies start giving BadImageFileFormat error

The best approach to solve this issue is to

  • Get 64-bit version of the third party assemblies
  • Complile custom assemblies to run on any platform “ANY CPU”
An alternate (not recommended) approach would be to
  • Run the IIS of the 64-bit server to run as 32-bit

Refer the below link for more information

Step-by-Step Guide to Migrating from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010

Follow the steps in this article to migrate your SharePoint websites from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 on a server running Windows Small Business Server 2008.



In-place Migration

An in-place upgrade takes place on the same hardware as your previous version installations i.e. MOSS 2007.
The following steps explain what happens in an in-place upgrade process runs:
  1. Perform all pre-upgrade steps
  2. Run Setup for SharePoint Server 2010 on the server that runs the SharePoint Central Administration Web site. (in-place upgrade is automatically selected in setup)
  3. Run the Setup on the remaining front-end Web servers and application servers (in case of a server farm)
  4. Run the SharePoint Products Configuration Wizard on the server that hosts the Central Administration Web site.

When the configuration wizard finishes, the Central Administration Web site opens. A timer job schedules the upgrade process to run for each site collection. The upgrade process timer job upgrades each site collection. After all sites are upgraded, the upgrade process ends.
Note: You cannot perform an in-place migration on a 32-bit MOSS/WSS 3.0 server

Database Attach Migration

A database attach upgrade enables you to move to new hardware or a new farm. During a database attach upgrade, you detach all the content databases from an existing farm and then attach the databases to a new server farm installation. When you attach the databases to the new server farm, the upgrade process runs and upgrades the data in place.
The following steps explain what happens during a database attach upgrade:
  1. For MOSS:
  2. Update your MOSS servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later.
  3. For WSS 3.0:
  4. Update your servers to Service Pack 2 (SP2) of Windows SharePoint Services 3.0 or later
  5. Set up and configure a new SharePoint 2010 server.
  6. Transfer all customizations (Features, wsp’s, custom assemblies, pages etc) to the SharePoint 2010 server.
  7. Detach the content databases from the old Office SharePoint Server 2007 server and take the old farm offline.
  8. Attach the content databases to the new farm and upgrade the content.

1.1 Update your MOSS/WSS servers to SP2 or later

Update your servers to MOSS/WSS SP2 or later as it is required to perform while doing a database migration of your sites to SharePoint 2010.
Note: If the MOSS/WSS installation is lower than SP2 you cannot perform a database migration
1.2 Setup a SharePoint 2010 server
Setup a SharePoint server where the sites will be migrated.

1.3       Perform “PreUpgradeCheck”

This scans through your current server farm and checks all dependencies to ensure you are ready to migrate.
STSADM –help preupgradecheck
   -[rulefiles ]
MOSS – OssPreUpgradeCheck.xml         
WSS – WssPreUpgradeCheck.xml

1.4       Transfer all the customizations

Transfer all the customizations on the MOSSWSS server to the SharePoint 2010 server. Following table lists all the possible customizations
Site Template
Custom Web Part
Event Handler
Content Types
Un-ghosted Page
Master Pages
Themes and Style sheets
User Controls
Custom Site Definition
Jquery assets
Code or pages in /_Layouts
List Definition
Add-ons Workflow, Server Controls
Third -Party Solutions

1.5       Backup the content database from MOSS server
Backup the content database using any of the following method on the MOSS server
  •  Backup using SQL Management Studio
  •  Copy the *.mdf/*.ldf files

1.6       Attach the content database on SharePoint 2010 server

a.      Create a new web application and create a site collection on the SharePoint 2010 server.  (Doesn’t much matter what template you use, as you will be detaching and deleting its database).
b.      Once you have it created, go into central admin and delete the content DB from the Web app.
Restore the copy of the SQL content database taken in step 5.5 on the SharePoint 2010 server. Now that you have a copy of the Content DB on the new SQL server for SharePoint 2010, it is time to connect it to SharePoint 2010.  To do this, you have to use the command line as the GUI interface cannot handle the upgrade. 
Open a CMD interface and navigate to the BIN directory:
C:program filescommon filesMicrosoft sharedweb server extensions14bin
and perform the following:
stsadm –o addcontentdb –url enter your url –databasename enter your db name
1.7       Apply new Look and Feel

In SharePoint 2010 Microsoft has shipped all of the CSS and Master pages from 2007 to help ease the transition of sites in 2007 to 2010. Hence after you migrate the site to SharePoint 2010 you may still see the same look and feel on the site as in MOSS 2007.
To apply the new look and feel:
Navigate to: Site Actionsà Site Settings under “Title, Description, and appearance” there are these radio-button choices at the bottom of the screen:
  • Keep the previous SharePoint user experience.
  • Preview the new SharePoint user experience, but let me return to the previous user experience.
  • Use the new SharePoint user experience, and don’t ask me again.

Best Practices

  1. .       For MOSS:
  2.     Update your MOSS servers to Service Pack 2 (SP2) of Microsoft Office SharePoint Server 2007 or later.
  3.     For WSS 3.0:
  4.     Update your servers to Service Pack 2 (SP2) of Windows SharePoint Services 3.0 or later
  5.         Ensure that the environment is fully functioning before you perform an upgrade.
  6.         Run the pre-upgrade checker to look for potential issues.
  7.         If Possible perform a trial upgrade on a test farm first.
  8.         Back up your environment.
  9.         After upgrade, review the Upgrade Status page and upgrade logs to determine whether there are issues that must be addressed. Then review the upgraded sites.


With the advent of SP 2010 on the scene discussions are rife within the organizations who are already running on MOSS 2007 or WSS 3.0. Here in this article I will try to pen down the steps required to have a smooth migration from their existing setup to SharePoint 2010.
The key steps to perform the migration are:
  •        Pre-Migration steps
  •          Migration Process
    •          In-Place upgrade
    •         Database attach upgrade
  •          Best Practices

Pre-Migration Steps

Perform the following steps before migration of your site to SharePoint 2010.

Run the pre-upgrade checker.
The pre-upgrade checker identifies potential upgrade issues in your environment. Run this as you plan your upgrade and before you start the upgrade process, so that you can address these issues.

Back up the entire environment
 Create a full backup of your environment to ensure that you can recover if upgrade does not go as planned.

Migration Process

You can choose between two basic upgrade approaches in migration a Microsoft Office SharePoint Server 2007 site to Microsoft SharePoint Server 2010:
  1.  In-place upgrade
  2. Databases attach upgrade.

Let’s discuss these two approaches in more detail, so an in-place upgrade is used to upgrade all Microsoft SharePoint sites on the same hardware i.e. if you are already running your MOSS 2007 site on a 64-bit hardware environment.
A database attach upgrade enables you to move your content to a new farm or new hardware i.e. you can move your MOSS 2007 sites from a 32-bit environment to a 64-bit environment.
Note: SharePoint 2010 runs only on a 64-bit platform.