Session from SPBiz.com online event on June 18th, 2015. It’s always best to begin with a plan, and this session will provide a framework for developing your own migration plan. While tools will help automate some aspects of the content move, much of the complexity of a SharePoint migration happens before a tool is installed. This session will help analysts, project managers and admin of SharePoint to reduce migration time and increase success.

1. @buckleyplanet

2. Christian Buckley
Managing Director, Americas
www.buckleyplanet.com
@buckleyplanet
cbuck@gtconsult.com

3. About GTconsult

6. Collaboration has evolved

7. ~ John Mancini, CEO of AIIM.org

8. SharePoint Growth & Evolution
SharePoint Releases
Metadata
Content

9. http://www.eweek.com/small-business/public-it-cloud-services-
spending-to-reach-108-billion-by-2017-idc.html

10. Organizing for the Cloud

11. •
•
•
•

13. •
•
•
•
•

15. Is there risk in moving
my data to the cloud?

16. of workers used an unsanctioned cloud service
for document storage in the last 6 months
41%
87%
$1.8
of these workers knew their company had
policies forbidding such practices
(billion) estimated annual cost to remedy
the data loss
New Mobile Survey Reveals 41% of Employees Are Deliberately Leaking Confidential Data http://onforb.es/18h92Nv

17. According to IDC:
• 74% expect their cloud service to
be able to move a cloud offering
back on-premise if needed.
• 63% expect to have a single major
cloud service provider.
• 67% expect to purchase a wide
variety of services from a single
vendor.
• 84% want an established
relationship with a vendor to trust
them as a cloud service provider.

20. http://social.technet.microsoft.com/wiki/contents/articles/4633.what-is-infrastructure-as-a-service.aspx
Partner Hosted Private
Cloud
• Dedicated environment
• Externally hosted
• Externally or internally
managed
• Internally designed
Self Hosted
Private Cloud
• Dedicated environment
• Internally hosted
• Internally managed
• Internally designed
Shared or Dedicated
Public Cloud
• Shard or dedicated
environment
• Externally hosted
• Externally managed
• Externally designed
Dedicated
Public Cloud
• Partially or fully dedicated
• Externally hosted
• Externally or internally
managed
• Minimal customization
Traditional
on premises

22. What about my existing investments in
SharePoint on prem?
• Most SharePoint deployments have included customizations
to meet critical business needs
• User Management & Administration
• Security and Compliance
• Auditing, Reporting, Alerting
• User Adoption, Records
• Branding, etc…
• Consider the business problems you’ve
already invested in solving

23. •
•
•
•
•
•
•
•

25. On Premises Cloud
1. Migration

26. On Premises Cloud
2. User-driven (osmosis)

27. 3. Phased
On Premises Cloud

28. 4. Hybrid transition
On Premises Cloud
AD
Azure
ADADFS

29. Methodology used internally at Microsoft
Plan a Large Scale Migration to SharePoint Online (SlideShare) by Erica Toelle

30. Five things you should
consider before making
the move:

33. URLs
Site Collection Name
Site Collection Size
Sub site count
Large Lists
Document Versions
Customizations
Site Location/position
Content DB – Size, Number
Site Collections per DB
Duplicate or Orphaned Site Collections
My Sites – Content DB, Size
SharePoint 2013 Thresholds and Limits
http://technet.microsoft.com/en-us/library/cc262787.aspx

34. Community sites
Managed Navigation
Social Features
Mobile Devices
Deprecated Site
Definitions
New functionality can significantly increase
potential adoption if used well:
• Managed Metadata & Navigation – find
relevant information faster!
• “New” file storage and sharing capabilities http://technet.microsoft.com/en-
us/library/cc261834(v=office.15).aspx

35. Evaluate current business
process
Consider existing site structures
Departmental/team
reorganization
Publishing requirements
Search/findability
Navigation
Content Growth
“Over half feel they would be 50% more
productive with enhanced workflow,
search, information reporting, and
automated document creation tools” 1
1 – The SharePoint Puzzle – adding the missing pieces, AIIM, 2012

37. Strategy & Inventory
Updated Information
Architecture & New Features
Prepare - Reorganization?
Prepare - Migrate, archive,
or leave behind?

39. Skip SharePoint versions e.g. 2007
straight to 2013
Site collection-specific vs. content DB
Reorganization, splitting sites & lists
taxonomy, permissions, content types
Re-template sites
Implement a customized migration or
upgrade strategy
Support for Workflow

42. Limitation Impact
Limited APIs. Migrations to on-premises and
private cloud (e.g. Azure/Amazon/O365-D)
implementations of SharePoint support the
use of the full SharePoint Server Object
Model, the richest API available for
SharePoint, or a thin web services layer that
exposes the SharePoint Server Object Model
(Metalogix Extensions Web Services/MEWS),
for both reading, and writing SharePoint
Content.
Due to the multi-tenant nature of SPO,
Microsoft cannot expose the full SharePoint
Object Model in SPO.
Limited automation and controls around
migration and provisioning.
Microsoft currently expose three, relatively
limited API’s that are useful for migrations:
• The Client Side Object Model (CSOM)
• The Native Web Services (NWS) API
• The REST based interfaces to the CSOM

43. Limitation Impact
Inability to connect at the Farm/Tenant
level (CSOM) - With the full SharePoint
Object Model or MEWS, users can
connect at the Web Application or Farm
level. With the CSOM adapter users
cannot connect at the closest
equivalent, which is the Tenant level
• Users have to create Site
Collections in the SPO admin page
prior to connecting to them.
• Using 3rd party migration tools,
users may have to create a separate
connection for each Site collection
in SPO. Users are unable to
browse/search for all root level Site
Collections, and may require more
steps to promote Sites to Site
Collections.

44. Limitation Impact
Inability to preserve Item IDs in lists • Lists with dependencies on other
lists such as Lookup columns rely
on Item IDs in the Lookup lists.
• Because the CSOM does not
support retaining the Item ID of list
items, some 3rd party tools have
created workarounds that may
impact performance.

45. Limitation Impact
Copying MySites can only be done one
MySite at a time, and does not include
User Profile information.
• Unlike on-prem to on-prem
migrations where MySites can be
moved in a single operation, in SPO
admins must first create each
MySite.
• Admins then need to connect to
each MySite Site Collection
separatey, and then copy the
content from the source, pasting it
into the target MySite.
• Admins cannot copy MySite profile
information.

46. Limitation Impact
Versioning limitations in the CSOM API. • No support for migration of minor
versions of documents
• Authorship information for rejected
versions in a document library with
approval is lost.

47. Limitation Impact
Nintex workflows cannot yet be
migrated to Office 365 due to these
same CSOM limitations.
Nintex workflows must be recreated
using the Nintex SPO offering to the
best extent as possible.

48. Limitation Impact
Most on premises 3rd party solutions
are either not available in SPO, or their
functionality is greatly reduced
Work with vendor to understand
product roadmap and capabilities.
Other options are to build using out of
the box capability.

49. Limitation Impact
Inability to troubleshoot issues Required to work through Microsoft
support and SLAs. Retrieving a
correlation ID for a error could take
days/weeks

52. Mechanism Impact
User and Tenant-based throttling,
which ensures that no single user or
tenant can perform so many
simultaneous operations that it would
cause performance issues for other
tenants*
Large or complex migration jobs can be
cut off mid-migration.
*For more information, see HTTP Request Throttling in
SharePoint 2010 which still applies to 2013.

53. Mechanism Impact
Farm-based throttling. If a SPO farm
becomes unhealthy due to extreme
levels of activity, Microsoft may throttle
migrations to SPO and not permit them
to continue until farm health returns to
normal.
Any migration job can be throttle at
any time of day (usually during peak
time. This makes migration
performance extremely unpredictable,
and variable based on time of day, day
of week, and other variables out of your
control.

54. Mechanism Impact
Virus scanning SPO requires stringent virus scanning to
ensure all tenants on the shared farm
are protected, but it slows down
migrations as each document migrated
must be scanned.

55. Mechanism Impact
Hardware-based load balancing
determines which Web Front End (WFE)
server in the farm to route incoming
traffic, based on how busy any given
WFE is at that time
This can slow down migrations that are
large (content) or complex (many items
with multiple metadata fields, and/or
many versions)

56. Mechanism Impact
Third-party commercial denial of
service monitoring platform for
monitoring and throttling capabilities*
This can slow down migrations that are
large (content) or complex (many items
with multiple metadata fields, and/or
many versions)
*See The Office 365 Trust Center for more information.

57. Mechanism Impact
Third-party commercial denial of
service monitoring platform for
monitoring and throttling capabilities*
This can slow down migrations that are
large (content) or complex (many items
with multiple metadata fields, and/or
many versions)

58. Microsoft now offers a new Office 365 migration API that moves
files through Azure using a dedicated path.
Most of the migration tool vendors now take advantage of this
“conduit” to migrate files/content by packaging up exports of
your content and sending them to Azure, and from there Office
365 can import the data more quickly.
Works for SharePoint files, file shares, and person file shares, but
still requires you to build out your site collections, information
architecture, etc.

59. Due to the migration performance, it is recommended that
you take a gradual migration approach
May involve migrating one division at a time, and going live
with that division.
Allows you to assess the impact on your business users and
your helpdesk after moving one group of people to a new
user interface.
Also allows you to use focus groups to determine which
features you would like to implement as you gradually
migrate the business to SPO.

62. • http://ow.ly/KsuA7
• http://bit.ly/1ATXECn
• http://ow.ly/Omvhv
• http://ow.ly/OlQIH
• http://bit.ly/1DmwwQw
• http://bit.ly/1pl2UOY
• http://slidesha.re/1r6oIeP
• http://bit.ly/1or8ngE
• http://bit.ly/QC7mK1
• http://bit.ly/VTcuuY
• http://bit.ly/1rCyYPR
• http://bit.ly/1LfLdqQ
• http://bit.ly/1lyyg3L

63. •
•
•
•
•

64. Thank you!
www.buckleyplanet.com
@buckleyplanet
cbuck@gtconsult.com