This document provides 10 reasons why a SharePoint migration may fail: 1) Lack of knowledge about SharePoint and its underlying technologies. 2) Ignoring training which helps with adoption and success. 3) Poor communication about the changes to users. 4) Relying only on database attach upgrades without considering custom solutions. 5) Not building a new architecture to take advantage of SharePoint 2013 features. 6) Not inventorying and testing all sites for upgrade issues. 7) Lack of governance, information architecture, and migration planning. 8) Not defining clear and measurable goals for a successful migration. 9) Underestimating the importance of branding for user experience

1. 10
 bniaulin
REASONS your
sharepoint
migration
FAILED 

2. SharePoint 2013 has arrived
So You took off with
SharePoint 2013

3. But ignored
KEY
CONCEPTS

5. Now you feel
OVERLOADED

6. Now you feel
OVERLOADED
Like it might all come
CRASHING
DOWN

7. SO WHY DID YOUR
SHAREPOINT
MIGRATION
FAIL?

8.  bniaulin
1
YOU DON’T
KNOW
SharePoint

9. Yes, you.

10. Yes, you.
But it’s ok, that’s
mostly everyone

11. SharePoint
is easy to use.
A few clicks,
and you get:
Sites, Lists, Libraries, Pages...

12. And now you
Feel like the
coolest
person in town

13. But SharePoint
requires
time
knowledge
patience
and experience

14. It’s built on
Windows Server
IIS .NET SQL
DNS Javascript
AD
and so much
more...

15. It’s built on
Windows Server
IIS .NET SQL
DNS Javascript
AD
and so much
more...
That’s a lot of moving parts to consider when migrating

16. and if you’re not an expert in all of these fields....
then ASSEMBLE an EPIC team of them

17.  bniaulin
2
YOU THOUGHT
TRAINING
WAS OPTIONAL

18. SH
OC
KIN
G!

19. G!
KIN
OC
SH
Training is often left
at the end of the project
or even ignored

20. BUT
WHY?

21. Some see
it as too
big an
expen$e

22. Some see
it as too
big an
expen$e
cost of training
+
cost of lost productivity

23. TRAINING
HELPS!

24. TRAINING
HELPS!
employee
satisfaction 

25. TRAINING
HELPS!
employee
satisfaction 
tackle more tasks 

26. TRAINING
HELPS!
employee
satisfaction 
tackle more tasks 
motivation to use
SharePoint 

27. TRAINING
HELPS!
employee
satisfaction 
tackle more tasks 
motivation to use
SharePoint 
increased adoption 

28. TRAINING
HELPS!
employee
satisfaction 
tackle more tasks 
motivation to use
SharePoint 
increased adoption 
and much more... 

29. SO DON’T
IGNORE
TRAINING
IN YOUR
PLANNING

30. Let the users play with
SharePoint

31. and ensure your
SharePoint migration’s
success

32.  bniaulin
3
LACK OF
COMMUNICATION

33. By bringing
change

34. By bringing
change
you are already the
bad guy

35. trying to change their routine.

36. Without or proper
announcements communication
it’s going to
HIT HARD


37. increasing your
chances
for a bad
SharePoint Migration
experience


38. Take the time to
show off!
 New Features
 Dates & Milestones
 Organize launch events
 How it’ll facilitate tasks
 Reasons for the change

39. COMMUNICATE
and see yourself
become the hero
coming to the rescue

40.  bniaulin
4
YOU THOUGHT
DATABASE-ATTACH
WOULD DO
EVERYTHING

41. There can be only 1
...upgrade scenario
according to Microsoft,
only
Database-Attach
is supported
this is only from SP2010

42. and you thought this
would work like magic

43. bringing along all the old junk.
that’s everything that was in the
Databases

44. did you forget
you had custom
coded solutions?

45. Though it might
work for some...
Take the time to pick and
choose what to migrate
to SharePoint 2013

46. Enough has changed in
SharePoint 2013
That you’ll
want to
build a new
architecture

47.  bniaulin
5
IGNORED
BUILDING A NEW
ARCHITECTURE

48. 2013
SP2013
arrived with cool
new
features Search
WCM
Social
SkyDrive Pro
WebParts
Design Manager

49. Doing a
Database-Attach
upgrade
and bringing the same
old architecture over is like...

50. getting a
COOL
new office

51. And furnishing it
with old computers

52. things like the
Content Search WebPart
will completely redefine
how you see
a SharePoint Architecture

53. What used to be a brick wall
you couldn’t workaround
(boundaries between sites, site collections, etc.)

54. Can now easily be done using
SEARCH

55.  bniaulin
6
YOU DIDN’T
INVENTORY YOUR
SITES AND TEST
THEM FOR UPGRADE

56. Many factors will influence
whether your site
will still work after migration

57. If you don’t know what you
have in your environment

58. Then you won’t know
what could potentially
cause a problem after
an upgrade

59. Take the time to inventory
your sites
and know what you have

60. To run the
available
health checks
and tests
before upgrading

61.  bniaulin
7
NO PLANNING
NO GOVERNANCE
NO INFORMATION
ARCHITECTURE

62. Governance
Should not strike fear
when said out loud
Should not be a burden
to carry during the
project

63. A Governance plan helps establish rules.
With so many users and sites, it helps maintain
everything together.

64. but keep it simple.

65. or it will turn into a
document
NO ONE
will read

66. Information
Architecture
is the logical
way of
organizing
your
SharePoint
architecture

67. it will help you define things like
Metadata Columns Sites Content on
Pages
Navigation Hierarchy
and everything else that will be used in
your SharePoint

68. Make sure you have a plan
SharePoint Migration is no easy
task

69. set goals and milestones to
measure the success of your
migration

70. This can be simple
Look at what you want to
Remove
Migrate
Rebuild
And this will be even easier to do if you
did an inventory of your sites before

71.  bniaulin
8
NO MEASURABLE
GOALS
WERE SET

72. Without a clear set of goals
You won’t know if the
migration is a success or if
it’s finished. You’ll keep
going on and on

73. Define clear goals
Objectives that
make it a successful
migration for you

74. Measuring can be as
simple as knowing how
many sites have to be: Remove
Removed Migrate
Rebuild
Migrated or Rebuilt
14%
47%
39%

75. or using SharePoint Analytics to see if
users are using the new features

76.  bniaulin
9
BRANDING
SEEMED
IRRELEVANT TO
YOU

82. DID THESE IMAGES
EVOKE AN EMOTION?

86. WHICH INTRANET
WOULD YOU HAVE
RATHER USED?

87. But it has all the
same functionality,
why not?

88. Branding helps increase user adoption and if
done correctly, might even help with User
Experience and “Findability”

89.  bniaulin
10
IGNORING
THIRD PARTY
TOOLS

90. Tools cost money

91. But so
does your
time

92. THESE TOOLS MIGHT
END UP SAVING YOU
TIME AND MONEY

93. SOME OF THEM ARE
EVEN PRETTY COST
EFFECTIVE
and EASY TO USE

95. USEFUL LINKS  bniaulin
Supported Migration Scenarios
Introduction to SharePoint 2013
What might not work after you upgrade
Tools and Techniques to create a simple
Governance Plan
Planning a SharePoint Migration
What’s new with SharePoint Analytics
Using the Content Search Web Part to
Roll Up Sites


96. NO MORE
FAILED
SHAREPOINT
MIGRATIONS

97. Thank
You!

Please Share to help
others with their
SharePoint Migration
Benjamin Niaulin
twitter.com/bniaulin
bniaulin.wordpress.com
en.share-gate.com/blog