A walkthrough of the many different considerations while planning for your SharePoint migration.

2. Christian Buckley,
Director of Product Evangelism at Axceler
• Microsoft MVP for SharePoint Server
• Prior to Axceler, worked for Microsoft, part of the Microsoft
Managed Services team (now Office365-Dedicated) and worked
as a consultant in the areas of software, supply chain, grid
technology, and collaboration
• Co-founded and sold a software company to Rational Software.
At E2open, helped design, build, and deploy a SharePoint-like
collaboration platform (Collaboration Manager), onboarding
numerous high-tech manufacturing companies, including
Hitachi, Matsushita, Cisco, and Seagate
• Co-authored „Microsoft SharePoint 2010: Creating and
Implementing Real-World Projects‟ link (MS Press, March 2012)
and 3 books on software configuration management.
• Twitter: @buckleyplanet Blog: buckleyplanet.com Email: cbuck@axceler.com

3. Published 2012 by Microsoft Press
Order your copy at http://oreil.ly/qC4loT
Tackle 10 common business problems with
proven SharePoint solutions:
• Set up a help desk solution to track service requests
• Build a modest project management system
• Design a scheduling system to manage resources
• Create a site to support geographically dispersed teams
• Implement a course registration system
• Build a learning center with training classes and
resources
• Design a team blog platform to review content
• Create a process to coordinate RFP responses
• Set up a FAQ system to help users find answers quickly
• Implement a cost-effective contact management system

4. Improving Collaboration since 2007
Mission: To enable enterprises to simplify, optimize, and
secure their collaborative platforms
Delivered award-winning administration and migration
software since 1994, for SharePoint since 2007
Over 2,000 global customers
Dramatically improve the management
of SharePoint
Innovative products that improve security, scalability,
reliability, “deployability”
Making IT more effective and efficient and lower the total
cost of ownership
Focus on solving specific SharePoint
problems (Administration & Migration)
Coach enterprises on SharePoint best practices
Give administrators the most innovative tools available
Anticipate customers’ needs
Deliver best of breed offerings
Stay in lock step with SharePoint development and market trends

8. 10/13/2012 8

9. Despair.com
10/13/2012 9

10. This is your technical
migration, i.e. the
physical move of
content and “bits”
Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

11. This is the bulk of your
migration – the
planning, reorganization, a
nd transformation of your
legacy SharePoint
environment
10/13/2012 11

12. Move Migrate Upgrade
• Use the procedures for • Use the procedures for • Use the procedures for
moving a farm or migrating a farm or upgrading a farm or
components when you components when you components when you
are changing to are changing to a are changing to a
different hardware. For different platform or different version of
example, use these operating system. For Office SharePoint
procedures if you example, use these Server 2007.
move to computers procedures if you
that have faster change from Microsoft
processors or larger SQL Server 2005 to
hard disks. SQL Server 2008.

14. Migrations Migrations Migrations are Migrations are
are phased are iterative error prone not the end goal
• How and what you • Your planning should • There is no “easy” • Proper planning and
migrate should not be not be limited by the button for migration. change management
determined by the number of migration You can run a dozen policies will help you to
technology you use – it‟s attempts you make, or pre-migration checks be successful with your
about matching the by the volume of and still run into current and future
needs and timing of content being moved. A problems. Admins and migrations. The goals
your content owners healthy migration end users do things that should be a stable
and teams. A migration recognizes the need to are not “by the book.” environment, relevant
should be test the waters, to move Customizations. Third metadata, discoverable
flexible, moving sites sites, content and party tools. Line of content, and happy end
and content based on customizations in business applications users.
end user needs, not the waves, allowing users to that run under the radar.
limitations of the test and provide
technology. feedback.

15. Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

16. Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

17. Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

18. Christian Buckley
cbuck@axceler.com
+1 425-246-2823
@buckleyPLANET
www.buckleyPLANET.com
and http://info.axceler.com
Order your copy at http://oreil.ly/qC4loT

20. Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

21. 11 strategies you should
consider as part of your
migration planning

22. Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

23. • What works
• What doesn‟t work
• What are the organizational
“must have” requirements
• What are the “nice to
have” features

24. The tendency
is to jump to
solutions
before you
understand the
problem
Email Cell Twitter Blog
cbuck@echotechnology.com 425.246.2823 @buckleyplanet http://buckleyplanet.net

27. Strategy #2:
Conduct proper
capacity planning
10/13/2012 27

31. Strategy #3:
Understand the
customizations on
your source system
10/13/2012 31

32. Joel Oleson, SharePoint 2010: Best Practices to Upgrade and Migrate

34. Strategy #3: Understand the
customizations on your source system

35. Strategy #4:
Understand the
migration schedule
10/13/2012 35

37. Strategy #5:
Plan for the right
10/13/2012
kind of migration 37

39. Strategy #6:
Plan for
file shares
10/13/2012 39

42. • Move content, as-is, into SharePoint and clean up there
• Clean and organize content first, then move to a new structure in
SharePoint
• Migrate content in waves, using the iterations to sort through and
organize your content while in transit, moving some content as-
is, reorganizing and transforming others

43. Strategy #7:
Plan for
tagging, metadata, an
d taxonomy
10/13/2012 43

44. In Biology, taxonomy is the science dealing with the
description, identification, naming, and
classification of organisms. “however, the term is now
applied in a wider, more general sense and now may
refer to a classification of things, as well as to the
principles underlying such a classification.”
“Metadata provides context for data. Metadata is
used to facilitate the
understanding, characteristics, and management
usage of data. The metadata required for effective data
management varies with the type of data and context
of use.” Wikipedia.org

45. Strategy #7: Plan for tagging,
metadata, and taxonomy
Common Migraines
• Ad-hoc content migration leads to junk in portal
• Legacy content gets migrated slowly, if at all
• Inconsistent taxonomy across farms and site collections
• People author locally - multiplies problems globally
• Authors don‟t apply metadata= “shotgun” approach to
search OR Authors apply metadata without common
classification = better search, but worse authoring
experience
• Portal lacks high fidelity search
• User can‟t find the right content
• As a result, poor portal adoption and low user satisfaction

46. Strategy #7: Plan for tagging,
metadata, and taxonomy
Managed
Metadata
Service
Term
Stores
Improved
Governance

47. • Map out your high level taxonomy (web apps, site
collections) and schemas (Content Types)
• Understand the as-is and to-be, and how it relates to
your metadata
• With Managed Metadata Service in 2010, it is critical that
you set up a governance model to guide this process, or it
will quickly get out of hand

48. Strategy #8:
Understand
centrally
managed and
decentralized
environments
10/13/2012 48

49. CENTRALIZED DECENTRALIZED
• PROS • PROS
• Improves consistency • Requires no planning
• Reduces metadata duplication • Requires little upfront effort
• Easy to update • Works across site collections and
• Easy to support and train on portals
• Allows document-level • CONS
DIP, Workflow, Information • Decreases consistency
Policies, and document templates • Increases metadata duplication
• CONS • Hard to update
• Requires planning • Hard to support and train on
• Requires upfront work • Only allows list-level
• Hard to manage across site Workflow, Information Policies and
collections and portals document templates
• Difficult to reverse

50. Do we lock
Do we
down team
deploy
site creation?
MySites?
Do we
implant
microchips in
their palms?
Common Topics around Centralized
/ Decentralized

52. Strategy #9:
Stage your
platform for
10/13/2012
migration 52

53. • Hardware / software
• Network
• Virtual environments
• Hosting / datacenter
• Downtime / end user impacts
• Communication
• Location of your teams
• Backup/recovery

54. Strategy #10: Decide
Strategy
where and when to
where and when to
involve users
involve users
10/13/2012 54

57. Strategy #11: Define
what success looks like
(probably not this)
10/13/2012 57

59. Words of Wisdom:
Then again…

61. http://bit.ly/szCAt9
http://slidesha.re/d3RHNH
http://bit.ly/bjWXMS
http://bit.ly/dm2kDO
http://bit.ly/bTGe2b
http://bit.ly/eXf0Cy
http://oreil.ly/chSHli
http://bit.ly/9Ismfp
http://slidesha.re/16iiUX
http://bit.ly/9cT9aa
http://bit.ly/9GgDuY
http://bit.ly/cIHIlA
http://bit.ly/dphQ2W

63. Christian Buckley
cbuck@axceler.com
+1 425-246-2823
@buckleyPLANET
www.buckleyPLANET.com
and http://info.axceler.com
Order your copy at http://oreil.ly/qC4loT