1) The document discusses options for migrating to Microsoft SharePoint 2013, including upgrading existing SharePoint farms or sites to SharePoint 2013 on-premises or in Office 365. 2) It outlines the farm upgrade process for an on-premises migration to SharePoint 2013 and considerations for the different upgrade approaches. 3) Third party migration tools like AvePoint are presented as alternatives that can automate migrations, retain metadata and security settings, and reduce downtime compared to manual upgrades. The document demonstrates AvePoint's migration capabilities through an example project.

1. Migrating to SharePoint 2013 with AvePoint
Mary Leigh Mackie Shyam Oza
VP, Product Marketing Product Manager
mlmackie@AvePoint.com | @mlmackie Shyam.Oza@AvePoint.com | @ShyamOza

2. Technologies Solutions Partners
Support Services Community

3. Goals for SP2013 Upgrades
What Are Your Options?
Site Collection Upgrades
Farm Upgrade Overview
Utilizing Third Party Solutions
Demo: AvePoint’s Migration Solutions
Wrap Up
Q&A
Additional Resources

4. Business Intelligence
eDiscovery
Identity Management
Mobile Support
Social Computing
Records Management and Compliance
Web Content Management

5. Upgrade
Migrate

6. Manual
Automated

7. How much content?
How long? How much downtime can you tolerate?
How much customization?
“Big Bang” or scaled/phased approach?
Loss of metadata / security acceptable?
Who can help?
Minimum requirements?
Mappings available?
Can we restructure?
Maintain coexistence?

8. Out of the Box

9. Safer upgrades
Reduced Upgrade Time
Power to the people

10. Eliminate big bang upgrades
Move forward at a manageable pace

11. Rules can detect and in some cases repair
issues
Rules can exist for use in 14 and/or 15
modes
Can be run without doing upgrade

12. Throttle limit the number of parallel upgrades
Upgrade requests are always queued
Status of all queued upgrades are tracked within the queue

13. Farm Upgrade (On-Prem)

14. SharePoint SharePoint
2010 Farm 2013 Farm
(READ- ONLY)
Database servers:
SQL Server 2008 R2 or
SQL Server 2012
Web and Application servers:
Install all prerequisites
Install SharePoint 2013 Products.

15. Original SQL Server New SQL Server Most actions take place in SQL
Server Management Studio
Set to read-write (optional)
Set to read-only (optional)
Database
servers
Back up
Content databases
Service application databases

16. 1 2 3 4
Create SharePoint 2013
Production farm Copy databases to new farm Upgrade Databases Upgrade site collections
Server Farm Administrators

17. 1. Backup everything
2. Upgrade service first
3. Upgrade content databases
4. Upgrade site collections at your leisure
5. Re-index existing content

18. What About to SharePoint Online?

19. Office 365 – Dedicated
Microsoft no longer supports content migration for Office 365-D customers
Remaining options: Manual migrations, custom-coding, Third-party tools
Office 365 – Standard
Options: Manual migrations, custom-coding, Third-party tools

20. Third Party Solutions

21. Business continuity – minimal interruption to
end-user productivity
Content restructuring and tagging
capabilities
Filter outdated, irrelevant content
Lower total cost of ownership, Increase return
on existing assets
Upgrade challenges and limitations…

22. Perform a Content Archive End-of-Life
Information Architecture
Assessment Content
Reduce Risk of Non-
Harden Security Set End-User Expectations
compliance
Create a Migration Test Don’t Forget About
Environment Governance
© 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.

23. Discovery and Test-Run Tools
Migrate to SharePoint 2010, SharePoint 2013, SharePoint
Online, Legacy Platforms
Live or scheduled, online or offline
Comprehensive metadata, property, and security
mappings + Filter + Restructure
Migrate OOTB, SPD, and Nintex workflows
Centrally report and audit on ALL migration activity and
history

24. Overview
Best For: Pros: Cons:
• Any size environment, from single • Direct migration from 2007 to 2013 • Costs associated with purchasing of
server farms to large, distributed • Pre-scan to determine customisations additional software
farms • Reorganise content structures during • Learning/training of new software
• Migration from non-SharePoint migration
Sources • Granular migration
• Restructuring content • Retains metadata, versions,
permissions
• Preservation of any metadata or
• Virtually no downtime
security
• Applicable to non-SharePoint
repositories
• Options for 24 x 7 Support?

25. Demo: Migrating to SharePoint 2013 with AvePoint

26. 300TB Migration from multiple sources (SP, Livelink)
60TB migrated in one year
8 TB meeting strict 3-4 month timeline
6TB SharePoint migration
45TB Livelink migration
1.8 TB eRoom migration
Fully custom end-user driven migration project

28. Questions?

30. US: 1-800-661-6588 AvePoint.com
Sales@avepoint.com