SharePoint 2013 Migration

Unleashing SharePoint Potential

01 Key Business Reason to Migrate

02 Migration Approaches

03 Migration Cycle

04 Migration Problems

05 Single Shot Migration

07 External Tools

08 References

3: Key Business Drivers to Upgrade
1.Storage Infrastructure improvements

2.Increase End User Productivity

3.Strong and Effective Enterprise Search

4.Improved BI for Decision Makers

5.Web Content Management

6.Governance Automation

7.Easy moving from SharePoint 2013 to Office 365

3: Migration Approaches

SharePoint
2013
SharePoint
2010

MOSS 2007

• No direct migration approaches to migrate MOSS 2007 to SharePoint 2013
• divided it into two phase approach
• first phase the MOSS 2007 code & content will be migrated to SharePoint
2010 second phase the migrated SharePoint 2010 code & content will
again be migrated to SharePoint 2013.

3: Available Upgrade Approaches
In-place Database attach
1. An in-place upgrade takes place on the same A database attach upgrade enables us to move to new
hardware as your previous version installation. When hardware or a new farm. During a database attach upgrade, we
you run an in-place upgrade, the process upgrades detach (backup) all the content databases from an existing farm
the complete installation in a fixed order. This entire and then attach the databases to a new server farm installation.
migration can be executed offline in a single and When you attach the databases to the new server farm, the
combined process. upgrade process runs and upgrades the data in place.

2. Environment will be down for an undefined amount Does not require your source environment be down during
of time. upgrade.

3. As this process creates a lot of SQL transactions and This process doesn’t create any large amount of system or SQL
other system logs on the system disk, it creates a disk logs on disks.
overhead on multiple drives. Also this upgrade
process isn’t recommended for large content
database i.e. more than 50 GB.

4. The upgrade proceeds continuously. You cannot Can be done one content db at a time instead of upgrading all
pause the upgrade process in between. the content db in a single transaction.

5. No rollback As source environment will be untouched no need of rollback.

6. Less control over upgrade process, can’t predicate More flexible than in-place, exact time can be determine for
most activities time involved in overall process. each activities involved in overall process.

3: Migration Cycle

1.Plan

5.Validate 2.Prepare

4.Implement 3.Test

3: Migration Cycle
Plan Prepare Test Implement Validate
Document Build test farms Build/upgrade Troubleshooting
Determine strategy environment farms

Manage Use real data Deploy Upgrade event
Create a plan for customizations customizations failures
current customization

Plan upgrade Evaluate Minimize UI/UX issues
Plan for site collection strategy techniques downtime

Make items Find issues early Monitor progress Data issues
Plan for performance upgradable

Create a
communication plan
Clean up an
environment

3: Plan Checklist

 Content Databases
 Service Applications
 Farm/Web Application
 Farm Settings
 List down all the
customizations
 Plan Upgrade
Performance

3: Plan – Best Practices

Ensure that the environment is fully functioning before you begin to
upgrade.

Perform a trial upgrade on a test farm first.

Plan for capacity.

Back up your databases.

Optimize your environment before upgrade..

3: Prepare – Moss 2007 to SharePoint 2010
Create the SharePoint 2010 farm
• Installs SharePoint 2010 to a new farm

Web Application Creation & Code Deployment

• Creates a new web application
Or database database • Installs all server-side code customizations
In-place
attach attach
Upgrade MOSS 2007 databases
• Sets the MOSS 2007 Site Collection to
read-only so that users can continue to
OOTB Migration Approach Recommended access the old site while upgrade is in
progress on the new farm
/Available in 2013 • Back up the content databases from the
SQL Server instance on the MOSS 2007
Web Application
• Restores a copy of the databases to the
SQL Server instance on the SharePoint
2010 Web Application
• Attaches the content databases to the new
farm and upgrades the content databases
for this web application

3: Testing – Best Practices

Know what is in your environment. Do a full survey first.

Make your test environment as similar as possible to your real environment.

Use real data.

Run multiple tests.

Do not ignore errors or warnings.

Test the upgraded environment, not just the upgrade process.

3: Implement – SharePoint 2013 Upgrade Process

3: Implement – SharePoint 2013 Upgrade Process
Create the SharePoint 2013 farm
• GATHER INFORMATION AND CLEAN UP 2010 • Installs SharePoint 2013 to a new farm
FARM
• PREPARE 2013 FARM
PREPARE Web Application Creation & Code
Deployment
• Creates a new web application
• Installs all server-side code
• COPY DATABASE customizations
• UPGRADE SERVICE APPLICATION DATABASES Copy & Upgrade SharePoint 2010
• CREATE WEB APPLICATIONS AND APPLY
databases
UPGRADE CUSTOMIZATIONS
DATABASES • UPGRADE CONTENT DATABASES • Sets the SharePoint 2010 Site Collection
to read-only so that users can continue
to access the old farm while upgrade is
in progress on the new farm
• RUN SITE COLLECTION HEALTH CHECKS • Back up the content databases from the
• RUN SITE COLLECTION HEALTH CHECKS SQL Server instance on the SharePoint
• CREATE AN UPGRADE EVALUATION SITE 2010 Web Application
UPGRADE COLLECTION
• Restores a copy of the databases to the
• UPGRADE A SITE COLLECTION
SITES SQL Server instance on the SharePoint
2013 Web Application
• Attaches the content databases to the
new farm and upgrades the content
databases for this web application

3: Validate
Review Logs
• Upgrade Logs
• Application Event Logs

Validate Migrated Environment
• Review and Validate Web Applications
• Review and Validate Services
• Validate External Data Sources
• InfoPath
• BCS Connections (External Content Types and External Lists)
• Excel Services connections
• External targets for Enterprise Search
• Authentication Providers
• Customization defects and fixes

3: Site Collection Health Check
• The health checks are run automatically in repair mode when you start to upgrade
a site collection.
• Health checks examine a site collection and list potential upgrade issues, such as
missing or unsupported elements

Rule name Description
This rule checks for any files that were customized
Customized Files
in the site collection or sub sites

Missing Galleries This rule checks for all default galleries

This rule checks to make sure that the template the
Missing Site Templates site is based on is available and reports if any
elements are missing.
This rule checks to make sure that the language
Unsupported Language Pack References packs that are used by the site collection exist and
are referenced correctly by the site collection.
This rule checks to make sure that the multi-user
interface elements that are used by the site
Unsupported MUI References
collection exist and are referenced correctly by the
site collection.

3: References

http://technet.microsoft.com/en-us/library/cc303420.aspx
http://technet.microsoft.com/library/cc263447(office.14).aspx
http://technet.microsoft.com/en-us/library/cc303420(v=office.15).aspx

3: Migration Problems

1. SP technology 2013 workflows are built on Windows Workflow Foundation 4
(WWF4). However, SharePoint 2010 workflows continue to Windows Workflow
Foundation 3 (WWF3). The workflow migration is not suggested:-
There is one more framework available with SP 2013 called as WAW.
But AFAIK you can still create SP2010 type workflows using SPD2013.

2.Error during upgrade is missing server-side files, templates, features, or other
server-side customizations— either files that were installed with SharePoint
2010 Products or customized files:-
When you prepared for upgrade, you should have created an inventory of the
server-side customizations. Check this inventory to make sure that all the files that
are needed for your customizations are installed in your new environment.
3.More than 5,000 site collections in a database, consider breaking them out
into multiple databases.
To avoid errors during upgrade or broken sites after upgrade, we recommend that
you move some site collections into separate databases. If you have multiple
content databases, you can also speed up an upgrade process by upgrading
multiple databases in parallel

4. Some sites and site templates are not available in SharePoint 2013 .Sites
based on these templates will not work in SharePoint 2013. Remove these types
of sites before you upgrade:-
You can use the Get-SP Site Windows PowerShell command together
with the following options to find these sites:
Get-SPSite|Where-Object{$_.RootWeb.Template- eq"PowerPointBroadcast#0“}

5. If you haven’t installed SharePoint 2010 SP1, after you upgrade to SP
Server 2013, your out-of-the-box workflow tasks (such as Approval, Collect
Feedback) will go into locked status:-
Users should install SharePoint 2010 SP1 before upgrade to SharePoint
Server 2013.

6. We could create a list item under folder in custom list using Create List
Item action in SharePoint 2010 but in SharePoint 2013 Create List Item
action doesn’t support creating items in the folder due to platform limitation:-
Try calling SharePoint 2010 workflow using Start a list/site workflow action
in the SharePoint 2013 workflow.

7.A mismatch in authentication methods can cause problems when
you upgrade:-
Claims-based authentication is the default authentication method for web
applications in SharePoint 2013. If the web application was using classic mode, you
can either update it to claims before you upgrade the database, or create the web
application in classic mode and then migrate it to claims.

8.You cannot upgrade a database that is set to read-only.
Make sure that you set the databases to read-write before you attach and upgrade
the databases.

9.You must manually create all trusted data connections for Excel Services after
upgrade.

10.How to upgrade environments that include services farms to SP2013.
Some services in SharePoint 2010 Products can be shared across multiple farms . A
services farm hosts services such as Business Data Connectivity service, Search, and
User Profiles that other farms consume. When you upgrade to SharePoint 2013, you
first upgrade the services farm, and then upgrade the farms that consume those
services.

Metalogix Content Manager 6.0
http://www.metalogix.com/Products/Content-Matrix.aspx

Key Features:
1. Direct Upgrade to SharePoint 2013
2. Migrate File Shares and more
1. Content Matrix 6.0 connects and moves terabytes of content from file shares,
blogs, wikis, Exchange Public Folders, PST files, eRoom and websites.
2. Content Matrix 6.0 moves the content, files, associated metadata and other
relevant attributes such as permissions or information structure into
SharePoint. Empower Content Owners

Key Benefits:
1. Upgrade with Confidence
2. Move to the Cloud: Office 365 and Office 365 Dedicated
3. Keep SharePoint Organized
4. migration speeds of up to and beyond 125GB per hour
5. Move Structure, Workflows and Permissions
6. Analyze your existing content

Supported Source Systems
1. SharePoint Server 2013 & 2010
2. SharePoint Foundation 2013 & 2010
3. Office 365
4. Office SharePoint Server 2007 & WSS 3.0
5. SharePoint Portal Server 2003 & WSS 2.0
6. File Shares
7. Exchange Public Folders & PST files
8. Google Blogger, Word press, Movable Type, Telligent
9. Blogs using Metaweblog standard or RSS
10. Atlassian Confluence, Media Wiki
11. HTTP or HTTPS accessible websites

SharePoint 2013 Migration

More Related Content

What's hot (20)

Similar to SharePoint 2013 Migration (20)

More from Vishal Gupta (7)

Recently uploaded (20)

SharePoint 2013 Migration

Editor's Notes