O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

10 Reasons your SharePoint Migration Failed

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
SharePoint 2013 Migration
SharePoint 2013 Migration
Carregando em…3
×

Confira estes a seguir

1 de 97 Anúncio

10 Reasons your SharePoint Migration Failed

Baixar para ler offline

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.

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.

Anúncio
Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Quem viu também gostou (16)

Anúncio

Semelhante a 10 Reasons your SharePoint Migration Failed (20)

Mais de Benjamin Niaulin (17)

Anúncio

Mais recentes (20)

10 Reasons your SharePoint Migration Failed

  1. 1. 10  bniaulin REASONS your sharepoint migration FAILED 
  2. 2. SharePoint 2013 has arrived So You took off with SharePoint 2013
  3. 3. But ignored KEY CONCEPTS
  4. 4. Now you feel OVERLOADED
  5. 5. Now you feel OVERLOADED Like it might all come CRASHING DOWN
  6. 6. SO WHY DID YOUR SHAREPOINT MIGRATION FAIL?
  7. 7.  bniaulin 1 YOU DON’T KNOW SharePoint
  8. 8. Yes, you.
  9. 9. Yes, you. But it’s ok, that’s mostly everyone
  10. 10. SharePoint is easy to use. A few clicks, and you get: Sites, Lists, Libraries, Pages...
  11. 11. And now you Feel like the coolest person in town
  12. 12. But SharePoint requires time knowledge patience and experience
  13. 13. It’s built on Windows Server IIS .NET SQL DNS Javascript AD and so much more...
  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 2 YOU THOUGHT TRAINING WAS OPTIONAL
  17. 17. SH OC KIN G!
  18. 18. G! KIN OC SH Training is often left at the end of the project or even ignored
  19. 19. BUT WHY?
  20. 20. Some see it as too big an expen$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 IGNORE TRAINING IN YOUR PLANNING
  29. 29. Let the users play with SharePoint
  30. 30. and ensure your SharePoint migration’s success
  31. 31.  bniaulin 3 LACK OF COMMUNICATION
  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 proper announcements communication it’s going to HIT HARD 
  36. 36. increasing your chances for a bad SharePoint 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 THOUGHT DATABASE-ATTACH WOULD DO EVERYTHING
  40. 40. There can be only 1 ...upgrade scenario according to Microsoft, only Database-Attach is supported this is only from SP2010
  41. 41. and you thought this would work like magic
  42. 42. bringing along all the old junk. that’s everything that was in the Databases
  43. 43. did you forget you had custom coded solutions?
  44. 44. Though it might work 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 IGNORED BUILDING A NEW ARCHITECTURE
  47. 47. 2013 SP2013 arrived with cool new features Search WCM Social SkyDrive Pro WebParts Design Manager
  48. 48. Doing a Database-Attach upgrade and bringing the same old architecture over is like...
  49. 49. getting a COOL new office
  50. 50. And furnishing it with old computers
  51. 51. things like the Content Search WebPart will completely redefine how you see a 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 TEST THEM FOR UPGRADE
  55. 55. Many factors will influence whether your site will still work after migration
  56. 56. If you don’t know what you have in your environment
  57. 57. Then you won’t know what could potentially cause a problem after an upgrade
  58. 58. Take the time to inventory your sites and know what you have
  59. 59. To run the available health checks and tests before upgrading
  60. 60.  bniaulin 7 NO PLANNING NO GOVERNANCE NO INFORMATION ARCHITECTURE
  61. 61. Governance Should not strike fear when said out loud Should 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 like Metadata 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 to measure the success of your migration
  69. 69. 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
  70. 70.  bniaulin 8 NO 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 that make it a successful migration for you
  73. 73. Measuring can be as simple as knowing how many 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 SEEMED IRRELEVANT TO YOU
  76. 76. DID THESE IMAGES EVOKE AN EMOTION?
  77. 77. WHICH INTRANET WOULD YOU HAVE RATHER USED?
  78. 78. But it has all the same 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 IGNORING THIRD PARTY TOOLS
  81. 81. Tools cost money
  82. 82. But so does your time
  83. 83. THESE TOOLS MIGHT END UP SAVING YOU TIME AND MONEY
  84. 84. SOME OF THEM ARE EVEN 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 FAILED SHAREPOINT MIGRATIONS
  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

×