We’ve touched a bit on the added functionality of SharePoint 2010 in our blog, but we understand the migration process can be a bit intimidating for a number of reasons. First of all, you don’t want down time that affects your workflow, and you definitely don’t want to stall important client projects because of a lengthy migration process and/or loss of important data. We understand your concerns and have prepared a 5 step checklist to ensure your SharePoint migration is smooth, fast and secure. Follow these steps, and you’re in for a successful migration!
- Run the pre-upgrade checker – Run the pre-upgrade checker and address any issues. Use the report that is generated by the tool to fill out the Upgrade planning worksheet.
- Clean up your environment– Before you begin the upgrade; make sure that your environment functions in a healthy state and that you clean up any content that you do not have to keep. Remove or repair any orphaned sites or data, address any large lists or large access control lists (ACLs), remove extraneous document versions, and remove any unused templates, features, or Web Parts.
- Record settings for user profile synchronization– Record the settings used for user profile synchronization in your previous environment in the upgrade worksheet. You will apply them to your new environment when you create and enable the User Profile Synchronization service. Record settings for connections, property mappings, and filters.
- Record blocked file types– Blocked file types are not preserved during upgrade. Copy the list of blocked file types and save the list in the upgrade worksheet so you can reapply the settings after upgrade.
- Back up your environment– Back up your entire environment to ensure that you can recover the existing environment in case something goes wrong during the upgrade process.
These steps are essential to a successful migration, but it’s equally important to have an experienced partner to walk you through the process as well as ask key questions you wouldn’t otherwise think of. The CoreBix team has completed a number of successful migrations from SharePoint 2007 to SharePoint 2010 and is here to help you. Please contact us with any questions pertaining to the 5 step process above or in general about migrating to SharePoint 2010.
By Robert Jumblatt of CoreBix, Washington, DC Microsoft SharePoint Solutions Experts
March 20, 2011 at 7:19 pm
Changing SERv Name OR use DNS with AAM – after migr to 2010 with new S.FARM
I am not sure whether this the right place for getting the answer of my question. I relatively new in SharePoint Admin side.
I have a existing MOSS 2007 PRODUCTION intranet server name “SPServer” and the default web application (port 80) is also “http://SPServer”.
I built new SharePoint 2010 server Farm server name SPServer2010. The Default web application (port 80) is also “http://SPServer2010”.
I want keep the same name of URL after migration (doing migr. attach method).
Do I need to change the server name and url from SPServer2010 and url to http://SPServer2010 or redirect with AAM usding DNS?
How can I change the server name and default application name From “SPServer2010” and web aplication “http://SPServer2010” to “SPServer” and “http://SPServer” on cut off date? These new 2010 will become production server.
Thanks,
Utpal
March 25, 2011 at 5:06 pm
You could map the old server name to the IP of the new server in DNS, and create alternate access mapping in Sharepoint.
You also could rename the server as well, see http://technet.microsoft.com/en-us/library/cc261986.aspx
Hope this helps