Export (0) Print
Expand All
ABS
AND
ASC
COS
DAY
DDB
EXP
FV
IF
INT
LEN
LN
LOG
MAX
Me
MID
MIN
MOD
NOT
IS
NPV
ODD
OR
PI
PMT
PV
SIN
SLN
SUM
SYD
T
TAN
VAR
Expand Minimize

Migrating and Upgrading Web Sites

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

If you have been using from Microsoft, you probably have several Web sites that you need to move to new servers running Microsoft . You may also have new Web sites based on that you want to move to another URL or another Internet Service Provider, for example. To accomplish these tasks, you use the Microsoft SharePoint Migration Tool (smigrate.exe).

For larger scale site migration in , such as moving a site collection to a new server, use the full backup and restore features for . For more information, see Backing Up and Restoring Web Sites .

When you use the SharePoint Migration Tool, you must actually perform two separate operations: First, you back up the site to a file, and then you restore the site to the new location. During the backup process, you specify the URL for the Web site and the backup file to create. You can also specify the scope of the site migration (whether to migrate just the top-level Web site, or whether to migrate the top-level Web site and any subsites). During the restore process, you specify the new URL and the backup file to restore from.

If you are upgrading from to , you can also specify whether to migrate the security settings for the site. Migrating security settings includes all of the following:

  • The list of user roles and associated rights

  • The list of user accounts and role membership

  • The anonymous access settings

  • The setting for inherited or unique permissions for the site

Before you migrate a site, be sure that all of the settings are the way you want them to be in your destination site. Note that if a user account cannot be verified in the domain, and you are not using Active Directory account creation mode, the account will not be restored.

When restoring a site, it's often helpful to create an account specifically for this purpose. This is beneficial because the SharePoint Migration Tool will substitute the name of the account performing the restore in places where the account of the author or the last person who modified the content is unavailable. For example, if you create an account named "SharePoint Migration" and then use that account to restore a site, users will see "SharePoint Migration" as the author of list items whose author was unavailable.

If the site you are backing up or restoring is large, it can take quite a while to process. For example, a site with about 4.5 gigabytes (GB) of data can take up to 3 hours to back up. The same site can take up to 3 hours to restore, because so many files must be uploaded to the new server. The more files included in a site, the longer the restore process will take. As a general performance guideline, you will have the best backup/restore performance when using separate computers for each task. An example of such a configuration is:

  • One computer running smigrate.exe

  • One or more computers running as front-end Web servers

  • One or more computers running as SQL backend servers

Caution: If you are using the SharePoint Migration Tool to migrate and upgrade a site from or FrontPage 2002 Server Extensions from Microsoft to , be aware that several features or types of customizations supported in these environments will not migrate properly or will not work in a migrated site. For a list of items that you must re-create or work around, see "Upgrade Considerations" in the Windows SharePoint Services Administrator's Guide.

You can migrate a site to a new virtual server, to a new top-level Web site on an existing virtual server, or to a subsite under an existing top-level Web site. No matter what level the site is, when you restore the site, you must create a blank site at the destination without applying a site template. For more information about creating a new virtual server, see Extending Virtual Servers . For more information about creating sites, see Creating Sites and Subsites . Follow the steps to create the site, but when prompted to select a site template, close the browser window and do not apply any template (including the Blank Site template) or the restore operation will fail.

Note: Some of the steps in this topic require changing settings in Microsoft Internet Information Services (IIS) or Microsoft SQL Server. To complete the steps that use IIS, you must be logged on as a member of the Administrators group on the local computer, or you must be logged on using an account that is both a member of the SharePoint administrators group and that has been granted permissions to administer IIS. To complete the steps that use SQL Server, you must be logged on using an account that is a member of the db_owner role in SQL Server.

Temporary Files Created During Backup and Migration

While creating the backup file, the SharePoint Migration Tool creates temporary files in a folder at the same location where the backup file (*.FWP) are created. You should ensure that there is enough free space at the location where the backup file will be created to hold all of the data and files from the original Web site, plus approximately 25 percent.

While restoring, files are periodically saved in a folder in Temporary Internet Files folder on the computer on which you are running the SharePoint Migration Tool. Make sure the computer you use to run the SharePoint Migration Tool has sufficient disk space to temporarily store approximately 20 percent of the data and files from the original Web site.

Migrating Sites to Another Server Running

If you use the SharePoint Migration Tool to migrate a site based on to another server running , the following information is not migrated to the new site:

  • Security settings including: rights, site groups and memberships, cross-site groups, anonymous access setting, and whether or not permissions are inherited from the parent site.

  • SharePoint Central Administration settings for the server or virtual server.

  • Personalizations including personal views.

  • Web Part customizations made through Modify My Web Part instead of Modify Shared Web Part .

Migrating Sites to in Active Directory Account Creation Mode

When you are running in Active Directory account creation mode, user accounts are automatically created in Microsoft Active Directory directory service when you add users to a site. Likewise, when you migrate a site from to a server running in Active Directory account creation mode, user accounts are automatically created in Active Directory for the users that existed in the site before migration. If you do not want to migrate user information to the new site, use the x parameter with the SharePoint Migration Tool.

The new user accounts are created based on the users' e-mail addresses, so each user must have a unique e-mail address for the account creation to work correctly. If a user does not have an e-mail address in the old site, no account can be created for that user. Also, because only one account is created for each e-mail address, a shared e-mail address results in a merged user account that is given all of the rights that each original user had, and is also listed as the user name for any items added to the site by any of the original users. Be sure that each existing user account has a unique e-mail address before migrating a site, and that you enter the full e-mail address (for example: someone@example.com).

After you migrate a site to a server running in Active Directory account creation mode, you must reset the passwords for the new user accounts. When user accounts are created during site migration, no automatic e-mail messages are sent with the user name and passwords, so you must send the users their new logon information manually.

Migrating Sites By Using Secure Sockets Layer (SSL) Connections

For the SharePoint Migration Tool to migrate a site by using an SSL connection, the following conditions must be met:

  • The computer on which you are running the SharePoint Migration Tool trusts the certificate authority that issued the SSL certificate.

  • The hostname you provide when running the SharePoint Migration Tool matches the hostname on the SSL certificate.

  • The certificate is valid (for example, it cannot be expired).

If the computer on which you are running the SharePoint Migration Tool does not trust the certificate authority that issued the SSL certificate, you will need to add the certificate authority to your list of trusted certificates by following the steps in the following procedure.

Add certificate authority to list of trusted certificates

  1. Browse to the destination https site.The Security Alert window appears, indicating that the site certificate was issued by a company you do not yet trust.

  2. In the Security Alert window, click View Certificate .

  3. In the Certificate window, click the Certification Path tab.

  4. Click the parent certificate of the selected certificate. The parent certificate will have a red and white "X" through it.

  5. Click View Certificate .

  6. In the second Certificate window, click Install Certificate .

  7. In the Certificate Import Wizard ,click Next .

  8. In the Certificate Store window, choose either:

    • Automatically select the certificate store based upon the type of certificate : Choose this option if you want the new certificate to be kept in the default store for that kind of certificate.

    • Place all certificates in the following store : Choose this option if you want to specify the store in which the new certificate will be kept. After choosing this option, click the Browse button and specify the desired store.

  9. Click Next .

  10. Click Finish .

  11. In the Root Certificate Store window, click Yes .

Migrating Sites By Using Proxy Server Connections

Problems can occur if the SharePoint Migration Tool must migrate a site over a proxy server connection. For example, if the proxy server requires different authentication than the destination Web server, the user name and password specified when you ran the SharePoint Migration Tool will be rejected and the migration will fail.

Migrating Sites across Domains

Problems can occur when migrating a site to a destination Web server in another domain. Failures can occur even if you use the -u and -pw parameters to supply the necessary user name and password. To resolve this problem, on the computer on which you are running the SharePoint Migration tool, complete the following steps.

Turn on prompts for user authentication

  1. Click Start .

  2. Click Control Panel .

  3. Click Internet Options .

  4. Click the Security tab.

  5. Click the Internet zone in which the destination site exists.

  6. Click Custom Level .

  7. In the User Authentication Section, under Logon , click Prompt for user name and password .

  8. Click OK .

Before Migrating Sites to

Before you use the SharePoint Migration Tool to migrate your sites from either or to , it is recommended that you configure the following settings:

  1. If the original site is running , you must download and install service packs 1 and 2 from the Microsoft Product Update site and then install the Office XP Web Services Security Patch: KB812708 for the site to function with the SharePoint Migration Tool.

  2. Set the original site to read-only to ensure consistency. Because backup and restore may take some time, it is best to set the site to read-only so that the original site does not change while you are still restoring.

  3. If the original site is running Windows SharePoint Services, disable blocked file types so that smigrate.exe can include all site files in the backup.

  4. If you are migrating a large Web site and need additional virtual memory, increase the paging file size to at least 1 GB. Increasing the paging file size is recommended especially if you are running the SharePoint Migration Tool directly on a front-end Web server.

  5. Change the following server settings on the destination server (detailed steps appear later in this topic):

    • Increase the Internet Information Services (IIS) timeout settings to 65,000 seconds.

    • If the destination server is using a Microsoft SQL Server 2000 database, disable full-text search before migrating. This step can decrease amount of time required to restore by as much as 40% in some cases.

    • Turn on anonymous user access in IIS (optionaluse this setting only if you want to migrate anonymous access settings).

    • If you are using quotas for the destination virtual server, and the site you are migrating is close to the quota limit for the virtual server, double the quota limit.

    • Turn off blocked file extensions on the destination server.

  6. Change the following virtual server settings on the destination virtual server:

    • Change the maximum file size temporarily from 50 MB to 500 MB (or to the maximum upload limit for your hardware configuration).

    • Set the maximum number of allowed alerts to be unlimited.

  7. Create a destination collection, top-level Web site, or site and do not apply a template.

    Note: To create a destination site with no template, begin creating the site collection, top-level site, or subsite as usual, but when you get to the page where you are asked to select a template, close the browser window without making a selection. Do not apply any template (including the Blank Site template) or the restore operation will fail.

Important: When you have finished migrating your sites to Windows SharePoint Services, change the server settings to the configuration you want to use while users are working with the sites.

Note: If you are migrating sites to a server running in Active Directory account creation mode, you must also be sure that all users of the original Web site have valid, unique e-mail addresses. If you do not want to migrate the users and create new Active Directory accounts for them automatically, be sure to specify the x parameter when you run the SharePoint Migration Tool.

Download and install the update for ( only)

To migrate sites from SharePoint Team Services v1.0 to Windows SharePoint Services, you must verify that the server hosting the original site has been updated to work with the SharePoint Migration Tool. You must download and install service packs 1 and 2 from the Microsoft Product Update site and then install the Office XP Web Services Security Patch: KB812708 . To install this update, you must be a member of the local administrators group on the server.

Set the original site to read-only

You can set the original site to be read-only by turning off all but browsing and viewing rights on the Set List of Available Rights page for the server that contains the site.

Note: This setting applies to all sites and subsites on the server.

If you are migrating a site based on to a new location, you can set the site to read-only by locking the site. For more information about locking a site, see Configuring Site Quotas and Locks .

  1. On the original server, click Start , point to All Programs , point to Administrative Tools , and then click Microsoft SharePoint Administrator .

  2. On the Server Administration page, click Set list of available rights .

  3. Clear all of the check boxes except for the Browse , View Lists , and View Web Document Discussions check boxes.

  4. Click Submit .

Turn off blocked file extensions in the original site (Windows SharePoint Services only)

  1. Click Start , point to All Programs , point to Administrative Tools , and then click SharePoint Central Administration .

  2. Under Security Configuration , click Manage blocked file types .

  3. In the list of blocked file types, delete the file types you want to include in the backup.

  4. Click OK .

Caution: The list of blocked file extensions affects all sites on the server or in the server farm, not just the site you are migrating. After migrating, you must specify the blocked file settings again to restore this protection for any sites on the server or server farm.

Increase the paging file size

If you are migrating a large site or running the SharePoint Migration Tool directly on a front-end Web server, it is recommended that you increase the paging file size for the server to at least 1 GB.

  1. Click Start , point to All Programs , point to Administrative Tools , and then click Computer Management .

  2. In the console tree, right-click Computer Management (Local) , and then select Properties .

  3. On the Advanced tab, under Performance , click Settings .

  4. In the Performance Options dialog box, under Virtual memory , click Change .

  5. In the Drive list, click the drive that contains the paging file you want to change.

  6. Under Paging file size for selected drive , select Custom size , and then type 1024 in the Initial Size (MB) box.

  7. Specify a larger number in the Maximum Size (MB) box, and then click Set .

    This sets the paging file to a minimum of 1 gigabyte (GB).

Changing the Destination Server Settings

Some of the settings must be changed in IIS, and some must be changed in SharePoint Central Administration.

Increase IIS timeout settings

  1. Click Start , point to All Programs , point to Administrative Tools , and then click Internet Information Services (IIS) Manager .

  2. Double-click the server name that is running .

  3. Double-click Web Sites .

  4. Right-click the virtual server that you are restoring to, and then click Properties .

  5. On the Web Site tab, in the Connection time out box, change the setting from 120 to 65,000 seconds.

  6. Click OK .

If you want to migrate the anonymous user access settings to the destination server, you must enable anonymous user access in IIS.

Turn on anonymous user access in IIS

This procedure is optional. Turn on anonymous user access only if you want to migrate anonymous access settings.

  1. Click Start , point to All Programs , point to Administrative Tools , and then click Internet Information Services (IIS) Manager .

  2. Double-click the server name that is running .

  3. Double-click Web Sites .

  4. Right-click the virtual server that you are restoring to, and then click Properties .

  5. On the Directory Security tab, under Authentication and access control , click Edit .

  6. Select the Enable anonymous access check box, and then click OK .

  7. Click OK .

After the IIS settings are configured, you can change quota limits by using SharePoint Central Administration.

Double a quota limit

  1. Click Start , point to All Programs , point to Administrative Tools , and then click SharePoint Central Administration .

  2. Under Component Configuration , click Manage quotas and locks .

  3. On the Manage Quotas and Locks page, click Manage site collection quotas and locks .

  4. Enter the URL of the site collection, and then click View Data .

  5. In the Site Quota Information Section, double the amount of storage allowed for the Limit site storage to a maximum of option.

  6. Click OK .

If you know that the original site contains files that have file extensions on the blocked file extensions list, you must unblock those file extensions before you migrate the site. If you do not remove those file extensions from the blocked list, the files will not be migrated with the rest of the site content.

Disable full-text searching in SQL Server 2000

  1. Click Start , point to All Programs , point to Administrative Tools , and then click SharePoint Central Administration .

  2. On the SharePoint Central Administration page , under Component Configuration , click Configure full-text search .

  3. Clear the Enable full-text search and index component check box.

  4. Click OK .

Turn off blocked file extensions on the destination server

  1. Click Start , point to All Programs , point to Administrative Tools , and then click SharePoint Central Administration .

  2. Under Security Configuration , click Manage blocked file types .

  3. In the list of blocked file types, delete the file types you want to allow.

  4. Click OK .

If you want to continue blocking these file types after the site has been migrated, you must add the file extensions back to this list after the migration is completed. Note that this list of blocked file extensions affects all sites on the server or in the server farm, not just the site you are migrating.

Changing the Destination Virtual Server Settings

You change the settings for the destination virtual server by using the Virtual Server General Settings page in SharePoint Central Administration. Specify a larger maximum upload size to allow any existing large files to be restored during migration and allow an unlimited number of alerts to be sure that all of the alerts for your users can be added.

By default, the maximum upload limit is set to 50 MB, which may not be enough to restore your site's content. However, uploading files larger than 50 MB may cause problems, depending on your available system resources. If you greatly increase the maximum file size and then attempt to upload a very large file, the upload may fail or the server may stop responding. The file size at which may stop responding depends on the hardware you are using and usage patterns. For example, an installation that includes a front-end Web server with 512 MB of RAM and a back-end server with 1 GB of RAM may be able to handle files up to about 128 MB. In general, it is the amount of available memory that determines how large of a file can be uploaded - for a temporary solution, such as when you are running the SharePoint Migration Tool, you can set the maximum upload size to handle files about one quarter of the size of the physical memory for your server.

Note: Service Pack 1 includes a change to provide better support for large file sizes. If you have applied SP1, you can increase the maximum upload size to any value up to 2 GB (2047 MB). For more information, see Configuring large file support in Installing and Using Service Packs for Windows SharePoint Services .

Change the virtual server settings for maximum uploads and alerts

  1. Click Start , point to All Programs , point to Administrative Tools , and then click SharePoint Central Administration .

  2. Under Virtual Server Configuration , click Configure virtual server settings .

  3. On the Virtual Server List page, click the name of the virtual server that contains the destination site.

  4. On the Virtual Server Settings page, under Virtual Server Management , click Virtual server general settings .

  5. In the Maximum Upload Size section, in the Maximum upload size box, type the maximum size you want to allow.

    Note: By default, the maximum upload size is 50 MB. If you change this setting to a larger size, you may also need to change the IIS Connection Timeout setting. For more information, see Configuring large file support in Installing and Using Service Packs for Windows SharePoint Services .

  6. In the Alerts section, under Maximum number of alerts that a user can create , select Unlimited number .

  7. Click OK .

Create a New Top-level Site without Applying a Template

You can migrate a site to a new virtual server, to a new top-level Web site on an existing virtual server, or to a subsite under an existing top-level Web site. No matter what level the site is, when you restore the site, you must create a blank site at the destination without applying a site template.

You can use the stsadm.exe command line tool to create blank sites and site collections. For example:

 stsadm -o createweb 

stsadm -o createsite 

Be sure to not use the -sitetemplate parameter.

You can also use the SharePoint Central Administration, Site Administration, and Create pages to create a destination site without applying a template. To do so, begin creating the site collection, top-level site, or subsite as usual, but when you get to the page where you are asked to select a template, close the browser window without making a selection. Do not apply any template (including the Blank Site template) or the restore operation will fail.

Using the SharePoint Migration Tool to Migrate Sites

The SharePoint Migration Tool (smigrate.exe) is available in the Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin folder on your server computer. To use the SharePoint Migration Tool, you must be a site administrator for both the Web site being backed up and the destination Web site.

Note: You can also download the SharePoint Migration Tool from the Microsoft Web site .

Smigrate.exe takes the following parameters:

Parameter

Description

Example values

-w

Web site URL. Required.

A valid URL, such as http://myserver/site1 or https://myserver/site1.

-f

The name of the backup file. Required.

A filename, or full path to a filename, with the .fwp extension. For example, backup.fwp, c:\backup.fwp, or \\myserver\folder\backup.fwp.

Note: The file name extension is optional. If you do not specify the .fwp extension, it will be added automatically.

-r

Restores a site to a new location.

none

-e

Excludes subsites during backup. Optional.

none

-x

Excludes security during restore. Optional. For use when migrating from to only.

none

-y

Overwrites an existing backup file. Optional.

none

-u

The user name for the Web site administrator. This parameter is required if your site supports only Basic authentication. Note that if the current logged on user has sufficient rights to perform the migration, the current user's credentials are used to perform the migration instead of the one specified with the -u parameter. If you want the migration to be performed by a specific account, log on as that account before migrating. Alternatively, you can change your Internet settings so that your computer does not automatically try to authenticate when you connect to Web sites.

A valid user name, in the form DOMAIN\name.

-pw

The password for the Web site administrator. Optional.

A valid password. Use "*" to be prompted to type a password.

Note: If Internet Explorer Enhanced Security is enabled on your server, you must specify the u and pw parameters.

To back up a site, you use Smigrate.exe with the following parameters:

smigrate.exe -w Web_site_URL -f backup_filename [-e -y -u user_name -pw password]

For example, to create a backup of http://myserver/site1 to a file called backup.fwp at the root of the c:\ drive, without including any subsites of the Web site, you would type the following:

smigrate.exe -w http://myserver/site1 -f c:\backup.fwp -e

Note: If your site has a space in the URL, enclose the URL in quotation marks ("). For example, to back up http://myserver/my site, type "http://myserver/my site".

To restore a site, you use Smigrate.exe with the following parameters:

smigrate.exe -r -w Web_site_URL -f backup_filename [-u user_name -pw password]

For example, to restore the above site to http://yourserver/site2, you would type the following:

smigrate.exe -r -w http://yourserver/site2 -f c:\backup.fwp

If you are logged on with an account that does not have specific permissions to the destination Web site, you can specify a site administrator user name and password that has the appropriate permissions. For example, to restore a site and specify the administrator user name and password, you would use the following syntax:

smigrate.exe -r -w Web_site_URL -f backup_filename -u site_administrator_user_account -pw password

When you migrate a site from to , you can also use the x parameter during restore, which allows you to determine whether or not to preserve the security settings for the Web site (user accounts and site groups). You can run the SharePoint Migration Tool from any computer running Microsoft Windows 2000 Service Pack 3 or later. The tool can be copied to another computer and used even if is not installed.

Note: The upgrade and migration from to is not full fidelity, and some data may be lost because of changes in the functionality between versions. You can view the smigrate.log file to see which items migrated successfully and which did not. The smigrate.log file is stored in the %temp% directory for your user account. If a log file already exists from a previous backup or restore, a log file will be created using the next available name (such as smigrate_1.log, smigrate_2.log, and so on).

To restore a site based on to a server running , and exclude the security information, you use Smigrate.exe with the following parameters:

smigrate.exe -r -w Web_site_URL -f backup_filename -x

Troubleshooting Migration Issues

If your site does not migrate as expected, refer to the following list to understand issues or find solutions:

  • When using the SharePoint Migration Tool to backup my site, I get the message:The server administration programs and the server extensions on the Web server are not compatible. The server is too old to use with this administration program. Please consult the section in the Administration Guide on Migrating and Updating Web Sites for more information.

    To migrate sites from SharePoint Team Services v1.0 to Windows SharePoint Services, you must verify that the server hosting the original site has been updated to work with the SharePoint Migration Tool. To download this update, go to the Office XP Web Services Security Patch: KB812708 page. To install this update, you must be a member of the local Administrators group on the server.

  • When using the SharePoint Migration Tool to restore a site, I get the following error message:Server error: A site template has already been applied to this site. Once a template has been applied, the site must be deleted and recreated in order to apply a different template.

    To restore to a site, you must first create a blank site without applying a template. To create a destination site with no template, begin creating the site collection, top-level site, or subsite as usual, but when you get to the page where you are asked to select a template, close the browser window without making a selection. Do not apply any template (including the Blank Site template) or the restore operation will fail. After you have created a blank site with no template, you can use the SharePoint Migration Tool to restore to that site.

  • How do I determine if there were errors during migration?

    Check the SharePoint Migration Tool log file for errors. The smigrate.log file is stored in the %temp% directory for your user account. If a log file already exists from a previous backup or restore, new log files will be created using the next available name (such as smigrate_1.log, smigrate_2.log, and so on). Search the log entries for the following error messages: cannot, could not, failure, server error, timed out, unable to, and the server sent a response.

  • Alerts from unavailable users were not restored.

    If a user account no longer exist.

    ts at restore time, or if the account was a local account, the alerts for that user account cannot be restored.

  • Survey creation times are incorrect.

    Creation times for surveys are not preserved during migration. This applies to all list types, but is most visible for surveys.

  • The site language is incorrect.

    When you restore a site, the language of the restored site must match that of the backed up site. Be sure that the language you need is available on the server you are restoring to.

  • There are too many views.

    If your site was migrated from to , the restored site contains both the views from the original site and the default views for . The restored views are listed after the default views. You can remove any views that you do not want.

  • I get an error message when I try to back up or restore a site through a proxy server.

    If your firewall or proxy server requires authentication, you may not be able to back up or restore a site.

  • Some of my currency formats changed after migration.

    When migrating a site from to , converts some obsolete currencies to their modern equivalents. For example, German Deutschmarks are converted to Euros. However, only the format of the currency field is changed. The value for each entry is not altered and must be manually converted by using the desired conversion rate.

  • Some of the entries have the fields Created By or Modified By attributed to the wrong person.

    When you migrate a Web site, the SharePoint Migration Tool attributes any content created by users who are not currently members of the source site to the user who performed the site migration. This problem can happen easily if you migrate to a new site, and then migrate from there to yet another site. The second time you run the SharePoint Migration Tool, it is possible that there will be content from a user from the source site who is not a member of first destination site. After that content is migrated to the second destination site, the content will be attributed to the user who performed the second migration. To resolve this problem, make sure that all team members are listed on the User Information page (Userinfo.aspx) of the source site before migrating.This problem occurs only when migrating sites to another server running .

  • The lookup column I created is blank after I migrated the site.

    If you have a lookup column with the Get information from option set to User Information , the field will show up as blank in the restored site. This problem occurs only when migrating sites to another server running . This problem can happen easily if you migrate to a new site, and then migrate from there to yet another site. The second time you run the SharePoint Migration Tool, it is possible that the lookup field looked up a user from the source site who is not a memeber of the first destination site. When that content is migrated to the second destination site, if the SharePoint Migration Tool cannot find the user name in the second destination site, the lookup column is left blank. To resolve this problem, make sure that all team members are listed on the User Information page (Userinfo.aspx) of the source site before migrating.

  • The properties of library folders have the wrong information in fields such as Created By or Created.

    The SharePoint Migration tools does not preserve library folder information such as Created, Created By, Modified, and Modified By. This problem occurs only when migrating sites to another server running .

  • Some of the properties for files in my library are blank after migration.

    If the files were uploaded to the library using a multiple file upload utility such as the one provided in or using a -compatible Web page editor such as , any custom properties that use a default value will be blank after migration.

  • I no longer get alerts for changes in library folders

    The SharePoint Migration tool does not preserve alerts for library folders. This problem occurs only when migrating sites to another server running .

  • The migrated site is larger than the original site

    The size of the restored site will be larger than the original site due to an increase in the size of Web Part Pages. If the original site is near the size quota allowed on the destination server, you may need to increase the quota on the destination server or delete some site content. This problem occurs only when migrating sites to another server running .

  • Properties for my basic page or Web Part Page such as Modified or Modified By have changed after site migration.

    Properties such as Modified or Modified By are not preserved for basic pages or Web Part Pages. This problem occurs only when migrating sites to another server running .

  • The creation date and time for Web discussions have changed after migration.

    The SharePoint Migration Tool does not preserve creation time and date for Web discussions during migration. This problem occurs only when migrating sites to another server running .

  • A user keeps getting alerts for changes to the site, but he or she isn't allowed access to the site.

    The SharePoint Migration Tool migrates alerts to the new site, however, does not migrate site permissions. To resolve this problem, use the SharePoint administration pages to assign the user to a site group on thenew site. If you don't want to give the user access to the site, you must manually delete any alerts that he or she created. This problem occurs only when migrating sites to another server running .

  • The version numbers on my documents have changed after migration.

    If you have a library with Document Versions enabled, the versions are numbered sequentially after migration. Deleting a version of a document from the library causes the original version numbers to be non-sequential. This problem occurs only when migrating sites to another server running .

  • The files that I had checked out are checked in after migration.

    File checkout status is not preserved during migration.

  • My user information from the source site didn't get migrated.

    The user information for the user who performs the migration is not copied to the destination site if he or she is already listed on the the User Information page (Userinfo.aspx) of the destination site.

  • The text direction for a list has changed.

    The SharePoint Migration Tool does not preserve the default text direction (right-to-left or left-to-right) during migration. To resolve this problem, you must manually change the text direction for lists after migration.This problem occurs only when migrating sites to another server running .

  • After migration, one of the lookup columns for a library has one more entry than there are files.

    After migration, an extra entry exists if a lookup field in a libary references files in the same library.

  • Some folders marked as unbrowsable did not migrate. uses the _private folder to store unbrowsable files and folders. FrontPage 2002 Server Extensions and allowed you to mark additional folders as unbrowsable. When you use the SharePoint Migration Tool to migrate a site that has multiple unbrowsable folders, only the _private folder and any files in the _private folder, are restored. If you want to migrate a site that contains additional folders marked as unbrowsable, move the files from those additional folders into the _private folder before migrating.

    Note: You can only see the _private folder and its contents when you open the site in a program compatible with such as or .

In addition, when you migrate a site from to , there are some features or customizations that do not migrate. For a list of these items, see Upgrade Considerations .

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft