10 Reasons your SharePoint Migration Failed

63,682 views
68,056 views

Published on

With the arrival of SharePoint 2013 on the market and the push for Office 365, many are planning to make the move on to this new version of SharePoint. I consider myself lucky to have already participated to a few of these so far. Often, I come across some challenges in the organization surrounding this upgrade. I thought I would put up this post and hopefully some of you will continue the reasons a migration can fail through the comments.

Published in: Technology, Business
21 Comments
48 Likes
Statistics
Notes
  • Very impresive insight of SP migration. We have been through all the issues pointed out in the slides. Thank you for sharing. I am going to share this!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • The Users Experience is undoubtable one of the most important things that can be thought of when designing a Content Management System. Microsoft has made this easy with their cool to use Office products that integrate with each other. As the years go on MS products get better and leave other technology based system in the pass. Products like SkyDrive, SkyDrive Pro, SharePoint, Office 365 and other key products that integrate with the software giant are becoming more and more popular to consumers. One thing Microsoft has thought us all is that it is a leader in enterprise technology software. We’ve learned that at times products like these are restricted to limited areas. This makes it hard to customize towards a company’s overall need. With products that are designed to integrate with one another at an individual rate with no room to modify the software beings problems to a company. This means the company has to wait for updates, hotfixes, third-party software and even new versions of the product for change. The company is force to grow when the product grows. The User Experience decreases in time from a familiar interface to a less productive Content Management System. An alternative to SharePoint and other solutions sometimes just makes sense. This is why we’ve chosen Centralpoint by Oxcyon. As a professional with over 15 years with content management experience I feel comfortable saying, “Centralpoint beings change to the table.” A Content Management System that comes with 230 out the box modules, Open Source license, easy to use interface (Like MS Office), No cost per seat, and a Company like Oxcyon that customizes Centralpoint to work for your company.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Quite powerful presentation! Liked the way images are used.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @Vivekdevaraj Thanks!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • The way each slide has been laid is cool!

    Good work
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
63,682
On SlideShare
0
From Embeds
0
Number of Embeds
46
Actions
Shares
0
Downloads
450
Comments
21
Likes
48
Embeds 0
No embeds

No notes for slide

10 Reasons your SharePoint Migration Failed

  1. 1. 10  bniaulinREASONS yoursharepointmigrationFAILED 
  2. 2. SharePoint 2013 has arrived So You took off with SharePoint 2013
  3. 3. But ignored KEYCONCEPTS
  4. 4. Now you feelOVERLOADED
  5. 5. Now you feelOVERLOADEDLike it might all comeCRASHINGDOWN
  6. 6. SO WHY DID YOURSHAREPOINT MIGRATION FAIL?
  7. 7.  bniaulin 1YOU DON’T KNOWSharePoint
  8. 8. Yes, you.
  9. 9. Yes, you.But it’s ok, that’smostly everyone
  10. 10. SharePointis easy to use.A few clicks,and you get:Sites, Lists, Libraries, Pages...
  11. 11. And now youFeel like thecoolestperson in town
  12. 12. But SharePointrequirestimeknowledgepatienceand experience
  13. 13. It’s built onWindows ServerIIS .NET SQLDNS Javascript ADand so muchmore...
  14. 14. 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
  15. 15. and if you’re not an expert in all of these fields....then ASSEMBLE an EPIC team of them
  16. 16.  bniaulin 2YOU THOUGHT TRAININGWAS OPTIONAL
  17. 17. SH OC KIN G!
  18. 18. G! KIN OCSH Training is often left at the end of the project or even ignored
  19. 19. BUTWHY?
  20. 20. Some see it as too big anexpen$e
  21. 21. Some see it as too big an expen$e cost of training +cost of lost productivity
  22. 22. TRAINING HELPS!
  23. 23. TRAINING HELPS! employee satisfaction 
  24. 24. TRAINING HELPS! employee satisfaction tackle more tasks 
  25. 25. TRAINING HELPS! employee satisfaction tackle more tasks motivation to use SharePoint 
  26. 26. TRAINING HELPS! employee satisfaction  tackle more tasks  motivation to use SharePoint increased adoption 
  27. 27. TRAINING HELPS! employee satisfaction  tackle more tasks  motivation to use SharePoint increased adoption  and much more... 
  28. 28. SO DON’T IGNORETRAINING IN YOURPLANNING
  29. 29. Let the users play with SharePoint
  30. 30. and ensure yourSharePoint migration’s success
  31. 31.  bniaulin 3 LACK OFCOMMUNICATION
  32. 32. By bringing change
  33. 33. By bringing change you are already the bad guy
  34. 34. trying to change their routine.
  35. 35. Without or properannouncements communication it’s going to HIT HARD 
  36. 36. increasing your chances for a badSharePoint Migration experience 
  37. 37. Take the time to show off! New Features Dates & Milestones Organize launch events How it’ll facilitate tasks Reasons for the change
  38. 38. COMMUNICATE and see yourself become the hero coming to the rescue
  39. 39.  bniaulin 4 YOU THOUGHTDATABASE-ATTACH WOULD DO EVERYTHING
  40. 40. There can be only 1 ...upgrade scenarioaccording to Microsoft,onlyDatabase-Attachis supportedthis is only from SP2010
  41. 41. and you thought thiswould work like magic
  42. 42. bringing along all the old junk.that’s everything that was in the Databases
  43. 43. did you forgetyou had customcoded solutions?
  44. 44. Though it mightwork for some... Take the time to pick and choose what to migrate to SharePoint 2013
  45. 45. Enough has changed in SharePoint 2013 That you’ll want to build a new architecture
  46. 46.  bniaulin 5 IGNOREDBUILDING A NEW ARCHITECTURE
  47. 47. 2013 SP2013arrived with cool new features Search WCM Social SkyDrive Pro WebParts Design Manager
  48. 48. Doing a Database-Attach upgradeand bringing the same old architecture over is like...
  49. 49. getting a COOLnew office
  50. 50. And furnishing itwith old computers
  51. 51. things like theContent Search WebPart will completely redefine how you seea SharePoint Architecture
  52. 52. What used to be a brick wall you couldn’t workaround(boundaries between sites, site collections, etc.)
  53. 53. Can now easily be done using SEARCH
  54. 54.  bniaulin 6 YOU DIDN’T INVENTORY YOUR SITES AND TESTTHEM FOR UPGRADE
  55. 55. Many factors will influence whether your sitewill still work after migration
  56. 56. If you don’t know what you have in your environment
  57. 57. Then you won’t knowwhat could potentiallycause a problem after an upgrade
  58. 58. Take the time to inventory your sitesand know what you have
  59. 59. To run the available health checks and testsbefore upgrading
  60. 60.  bniaulin 7 NO PLANNINGNO GOVERNANCENO INFORMATION ARCHITECTURE
  61. 61. GovernanceShould not strike fear when said out loudShould not be a burden to carry during the project
  62. 62. A Governance plan helps establish rules.With so many users and sites, it helps maintain everything together.
  63. 63. but keep it simple.
  64. 64. or it will turn into a document NO ONE will read
  65. 65. Information Architecture is the logical way of organizing your SharePoint architecture
  66. 66. it will help you define things likeMetadata Columns Sites Content on Pages Navigation Hierarchy and everything else that will be used in your SharePoint
  67. 67. Make sure you have a plan SharePoint Migration is no easy task
  68. 68. set goals and milestones tomeasure the success of your migration
  69. 69. This can be simpleLook at what you want to Remove Migrate RebuildAnd this will be even easier to do if youdid an inventory of your sites before
  70. 70.  bniaulin 8NO MEASURABLE GOALS WERE SET
  71. 71. 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
  72. 72. Define clear goals Objectives thatmake it a successful migration for you
  73. 73. Measuring can be assimple as knowing howmany sites have to be: Remove Removed Migrate Rebuild Migrated or Rebuilt 14% 47% 39%
  74. 74. or using SharePoint Analytics to see if users are using the new features
  75. 75.  bniaulin 9 BRANDING SEEMEDIRRELEVANT TO YOU
  76. 76. DID THESE IMAGESEVOKE AN EMOTION?
  77. 77. WHICH INTRANETWOULD YOU HAVE RATHER USED?
  78. 78. But it has all thesame functionality, why not?
  79. 79. Branding helps increase user adoption and if done correctly, might even help with User Experience and “Findability”
  80. 80.  bniaulin 10 IGNORINGTHIRD PARTY TOOLS
  81. 81. Tools cost money
  82. 82. But sodoes your time
  83. 83. THESE TOOLS MIGHTEND UP SAVING YOU TIME AND MONEY
  84. 84. SOME OF THEM AREEVEN PRETTY COST EFFECTIVE and EASY TO USE
  85. 85. 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 
  86. 86. NO MORE FAILEDSHAREPOINTMIGRATIONS
  87. 87. Thank You!  Please Share to help others with their SharePoint Migration Benjamin Niaulin twitter.com/bniaulin bniaulin.wordpress.com en.share-gate.com/blog

×