Sitecore Upgrade
Best Practices
Let's talk!
• Quick Intro
• Why should you upgrade?
• Upgrade basics
• Research and planning
• Recommended approach
• Tips for a smooth upgrade
Sitecore expert with 12 years
of CMS experience and over
10 years of experience on the
Sitecore platform. He loves
building personalized web
experiences using Sitecore's
experience platformand
helping clients understand
Sitecore's capabilities. Scott
has architectedmany large
Sitecore applications including
sites serving 200+ million page
views annually.
Hi. I’m Scott.
Scott Stocker
scott.stocker@edynamic.net
@sestocker
An award winning
global digital
marketing and
technology agency
focused on customer
experience
Exceptional Sitecore Expertise
Sitecore Practice
Sitecore partnership since
2003
Over 200 solutions
delivered
Large global resource pool
> 80 certified Sitecore
resources
Center of Excellence
Best practice development
3 MVPs on staff
Ongoing internal training
program run by MVPs
Creation of industry
acceleratorsand reusable
frameworks such as content
accelerators,customdata
connectors
Creation of reusable
Sitecore connectors:
Eloqua, Pardot, Marketo,
CRMs
edynamic Sitecore integrations
• Identify reasons to keep Sitecore on
a current version
• Identify parts of the upgrade process
• Identify areas for research and
planning
• Review the recommended approach
• Get everyone more comfortable with
the upgrade process
Goals Today
Why upgrade?
• Support from Sitecore
• Browser Compatibility
• Server/Database Support
• New Features
Why Upgrade
Sitecore Support
Sitecore Support
Browser Support
Server/Workstation OS
Database Server
• Sitecore tagging /facetsfor improved search
experiences
• Item Bucketsfor improved content architecture
• Introductionof xDB
• Introductionof xProfile
• IntegratedTag Management
• Sitecore ContentSearch
• SPEAK UI improvements
• Sitecore Items WebAPI
• Support for MVCASP.NET5.1
New Features
The Basics
• Database
• Configuration
• New Sitecore Files
• DLL’s
• /sitecoredirectory
• Code Updates
• New Server Roles
Components of a Sitecore Upgrade
• Have to run steps separately as documented by
Sitecore
• Downloadthe.updatefiles
• UsuallyUpdateInstallation Wizard
• Sometimesdatabasescripts
• Upgrades the content database and files on disk
• Get needed files from Sitecore
• SDNforversionsofSitecorebefore8
• Devfor8.0andabove
Running the Sitecore Upgrade
Running the Sitecore Upgrade
Configuration Changes
• Usually only required for major versions
• Forexample,ContentSearchAPIfrom6.6to7.0
• Analytics APIchangeswithxDBintroduction
• IntroductionofSPEAK
• Start with new Sitecore DLL’s
• Addtoyoursolutioninsourcecontrol
• Lookforcompilationerrors
• Testlocally
• If making several leaps, wait until the final version to
make code changes
• Forexample,ifgoingfrom6.6to8.1,don’tstopat7.0tomake
ContentSearchchanges
Code Changes
• If you are upgrading from < 7.5:
• MongoDB
• Processingserver
• Other options
• xManagementmode
• xDBCloudfromSitecore
New Server Roles
Planning
• Developer Workstations
• Development Server
• QA
• UAT/Staging
• Production CMS
• Production CD
Sitecore Installations
• Sitecore Modules
• WFFM
• Marketplace Modules
• Aretheycompatiblewiththeversionyouareupgradingto?
• Other third party components
• ClayTabletUpgrade
• .NETframework(MicrosoftIdentitychanges)
Sitecore “add-ons”
• “Big bang” upgrade?
• Canallsitesbeupgradedatonce?
• Don’t forget about Sitecore licensing
• PerSitecoreinstance
• Temporarylicensingavailable
Sites
• Baseline metrics
• Responsetimefortoppages
• CPU
• Memory
• Hardware requirements are different for Sitecore 8.x
Performance
• Document non-Sitecore web.config changes
• Customsettingsections
• WCFEndpointdefinitions
• Etc.
• Patch in Sitecoreconfiguration changes
• Ensurethatthepatchingplacesyourconfigurationwhereitneedstobein
thenewversion
• /sitecore/admin/showconfig.aspxcanhelpthisprocess
Configuration
• Final Database UpgradeTiming
• Content Freeze
• Code/Config Deployment
• Rollback
Go Live
Approach
• On a developer workstation or sandbox environment
• PracticeUpgradeSteps
• WorkwithSitecoreSupportonanyerrors
• UsevanillaCMinstances
• Remove customizations – especially pipelines
• UpgrademodulesalongwithSitecoreversions
• Documentstepsandproblems
• Upgraded database can now be used for developer
changes
• Re-enablecustomizationsandtest
• Makenecessarycodechanges
Local Upgrade
• Server where final upgrade will be run
• PracticeUpgradeSteps
• UsevanillaCMinstances
• Remove customizations – especially pipelines
• Makeiteasytoreplicaterunningtheupgrade
• Should be able to run the upgrade steps easily
• Practice at least once before the final upgrade of
content
• Have your CM and CD ready ahead of time
• Code/Configwillbedeployedviayourbuildprocess
• Rememberthatcustomconfigchangeswillbepatchedin
Upgrade Environment
• Upgrade the databases using out-of-the-boxSitecore
instances
• Sitecore files and configuration should come from the
Sitecore installer
• Customconfigshouldbepatchedin!
• Don’ttrytofollowthepagesofconfigchanges
• Remember to remove Sitecoresupport files you might
have
• Typically thesearehotfixesforaparticularknownissue
• Test both content management and content delivery
• Don’t forget to review log files,both during the upgrade
and after
Recommendations
33
Features
 Easy to install on your Sitecore instance - just
select the current and target versions and start
an upgrade
 Pre-configured with automated testing
capabilities powered by Selenium
 Full support for multiple languages
 Can handle any number of websites or
microsites
 Tool tracks all upgrade events in Sitecore log
file so you can see success/failure at any time
 Full support for user interface resolutions post
upgrade
 Full support for any on-premise or cloud
deployment
 Comes with 2 weeks of free, warranty support
Benefits
 Upgrade from any old Sitecore version to a
higher versions within days
Sitecore Automatic Version
Upgrader
edynamic‘s Auto vUpgrader for Sitecore
Tool detects the
current version by
itself. User needs to
select the next version
Confirmation message
displayed once the upgrade is
complete
Automated test case can be
run subsequently with the tool
Test results are displayed
Upgrade of 13 sites from Sitecore
6.6 to 8.1 within 1.2 weeks
Georgia-Pacific LLC is one of the world's
leading manufacturers & distributors of pulp,
paper, tissue, toilet and paper towel dispensers
and related chemicals.
They were struggling for over past 4 months to
upgrade multiple sites from Sitecore 6.6 to the
latest version
Background
Solution & Benefits
• edynamic was hired by G-P to rescue its upgrade project
undergoing delays for months by incumbent vendor
• With its upgrade utility tool edynamic upgraded 13 sites
from Sitecore 6.6 to Sitecore 8.1 within a record time of
1.2 weeks
• Test results showed minimal errors and were easily fixed
after the upgrade
• Migration – not an upgrade
• Youtellthetoolwhatcontenttomigrate
• Migrates:
• Contentitemsandmedia
• Allusers,rolesandsecuritypermissions
• Assistswithconfigurationmigrations
Sitecore Express Migration Tool
Sitecore Express Migration Tool
• Upgrade Sitecore regularly
• Irecommendatleastonceevery12-18months
• Planning is key for success
• Engage a partner for help
• Sitecorepartnersdoupgradesallthetime!
• Practice helps – often based on content freeze and
time it takes to upgrade, you will need to do the
process several times
• Engage SitecoreSupport for issues you can’t google
• Note:onlySitecorecertifieddeveloperscanengagesupport
• Don’t use IE to run the upgrade
• Modify the web.config/sitecore.configto increase
timeouts
Tips
Tips
• Email: scott.stocker@edynamic.net
• Twitter: @sestocker
• LinkedIn: https://www.linkedin.com/in/scottstocker
• Sitecore Stack Exchange:
https://sitecore.stackexchange.com/
• Awesome-Sitecore:
https://github.com/sestocker/awesome-sitecore
Contact Me
Questions?

Sitecore upgrade best practices

  • 1.
  • 2.
    Let's talk! • QuickIntro • Why should you upgrade? • Upgrade basics • Research and planning • Recommended approach • Tips for a smooth upgrade
  • 3.
    Sitecore expert with12 years of CMS experience and over 10 years of experience on the Sitecore platform. He loves building personalized web experiences using Sitecore's experience platformand helping clients understand Sitecore's capabilities. Scott has architectedmany large Sitecore applications including sites serving 200+ million page views annually. Hi. I’m Scott. Scott Stocker scott.stocker@edynamic.net @sestocker
  • 4.
    An award winning globaldigital marketing and technology agency focused on customer experience
  • 5.
    Exceptional Sitecore Expertise SitecorePractice Sitecore partnership since 2003 Over 200 solutions delivered Large global resource pool > 80 certified Sitecore resources Center of Excellence Best practice development 3 MVPs on staff Ongoing internal training program run by MVPs Creation of industry acceleratorsand reusable frameworks such as content accelerators,customdata connectors Creation of reusable Sitecore connectors: Eloqua, Pardot, Marketo, CRMs
  • 6.
  • 7.
    • Identify reasonsto keep Sitecore on a current version • Identify parts of the upgrade process • Identify areas for research and planning • Review the recommended approach • Get everyone more comfortable with the upgrade process Goals Today
  • 8.
  • 9.
    • Support fromSitecore • Browser Compatibility • Server/Database Support • New Features Why Upgrade
  • 10.
  • 11.
  • 12.
  • 13.
  • 14.
  • 15.
    • Sitecore tagging/facetsfor improved search experiences • Item Bucketsfor improved content architecture • Introductionof xDB • Introductionof xProfile • IntegratedTag Management • Sitecore ContentSearch • SPEAK UI improvements • Sitecore Items WebAPI • Support for MVCASP.NET5.1 New Features
  • 16.
  • 17.
    • Database • Configuration •New Sitecore Files • DLL’s • /sitecoredirectory • Code Updates • New Server Roles Components of a Sitecore Upgrade
  • 18.
    • Have torun steps separately as documented by Sitecore • Downloadthe.updatefiles • UsuallyUpdateInstallation Wizard • Sometimesdatabasescripts • Upgrades the content database and files on disk • Get needed files from Sitecore • SDNforversionsofSitecorebefore8 • Devfor8.0andabove Running the Sitecore Upgrade
  • 19.
  • 20.
  • 21.
    • Usually onlyrequired for major versions • Forexample,ContentSearchAPIfrom6.6to7.0 • Analytics APIchangeswithxDBintroduction • IntroductionofSPEAK • Start with new Sitecore DLL’s • Addtoyoursolutioninsourcecontrol • Lookforcompilationerrors • Testlocally • If making several leaps, wait until the final version to make code changes • Forexample,ifgoingfrom6.6to8.1,don’tstopat7.0tomake ContentSearchchanges Code Changes
  • 22.
    • If youare upgrading from < 7.5: • MongoDB • Processingserver • Other options • xManagementmode • xDBCloudfromSitecore New Server Roles
  • 23.
  • 24.
    • Developer Workstations •Development Server • QA • UAT/Staging • Production CMS • Production CD Sitecore Installations
  • 25.
    • Sitecore Modules •WFFM • Marketplace Modules • Aretheycompatiblewiththeversionyouareupgradingto? • Other third party components • ClayTabletUpgrade • .NETframework(MicrosoftIdentitychanges) Sitecore “add-ons”
  • 26.
    • “Big bang”upgrade? • Canallsitesbeupgradedatonce? • Don’t forget about Sitecore licensing • PerSitecoreinstance • Temporarylicensingavailable Sites
  • 27.
    • Baseline metrics •Responsetimefortoppages • CPU • Memory • Hardware requirements are different for Sitecore 8.x Performance
  • 28.
    • Document non-Sitecoreweb.config changes • Customsettingsections • WCFEndpointdefinitions • Etc. • Patch in Sitecoreconfiguration changes • Ensurethatthepatchingplacesyourconfigurationwhereitneedstobein thenewversion • /sitecore/admin/showconfig.aspxcanhelpthisprocess Configuration
  • 29.
    • Final DatabaseUpgradeTiming • Content Freeze • Code/Config Deployment • Rollback Go Live
  • 30.
  • 31.
    • On adeveloper workstation or sandbox environment • PracticeUpgradeSteps • WorkwithSitecoreSupportonanyerrors • UsevanillaCMinstances • Remove customizations – especially pipelines • UpgrademodulesalongwithSitecoreversions • Documentstepsandproblems • Upgraded database can now be used for developer changes • Re-enablecustomizationsandtest • Makenecessarycodechanges Local Upgrade
  • 32.
    • Server wherefinal upgrade will be run • PracticeUpgradeSteps • UsevanillaCMinstances • Remove customizations – especially pipelines • Makeiteasytoreplicaterunningtheupgrade • Should be able to run the upgrade steps easily • Practice at least once before the final upgrade of content • Have your CM and CD ready ahead of time • Code/Configwillbedeployedviayourbuildprocess • Rememberthatcustomconfigchangeswillbepatchedin Upgrade Environment
  • 33.
    • Upgrade thedatabases using out-of-the-boxSitecore instances • Sitecore files and configuration should come from the Sitecore installer • Customconfigshouldbepatchedin! • Don’ttrytofollowthepagesofconfigchanges • Remember to remove Sitecoresupport files you might have • Typically thesearehotfixesforaparticularknownissue • Test both content management and content delivery • Don’t forget to review log files,both during the upgrade and after Recommendations
  • 34.
    33 Features  Easy toinstall on your Sitecore instance - just select the current and target versions and start an upgrade  Pre-configured with automated testing capabilities powered by Selenium  Full support for multiple languages  Can handle any number of websites or microsites  Tool tracks all upgrade events in Sitecore log file so you can see success/failure at any time  Full support for user interface resolutions post upgrade  Full support for any on-premise or cloud deployment  Comes with 2 weeks of free, warranty support Benefits  Upgrade from any old Sitecore version to a higher versions within days Sitecore Automatic Version Upgrader
  • 35.
    edynamic‘s Auto vUpgraderfor Sitecore Tool detects the current version by itself. User needs to select the next version Confirmation message displayed once the upgrade is complete Automated test case can be run subsequently with the tool Test results are displayed
  • 36.
    Upgrade of 13sites from Sitecore 6.6 to 8.1 within 1.2 weeks Georgia-Pacific LLC is one of the world's leading manufacturers & distributors of pulp, paper, tissue, toilet and paper towel dispensers and related chemicals. They were struggling for over past 4 months to upgrade multiple sites from Sitecore 6.6 to the latest version Background Solution & Benefits • edynamic was hired by G-P to rescue its upgrade project undergoing delays for months by incumbent vendor • With its upgrade utility tool edynamic upgraded 13 sites from Sitecore 6.6 to Sitecore 8.1 within a record time of 1.2 weeks • Test results showed minimal errors and were easily fixed after the upgrade
  • 37.
    • Migration –not an upgrade • Youtellthetoolwhatcontenttomigrate • Migrates: • Contentitemsandmedia • Allusers,rolesandsecuritypermissions • Assistswithconfigurationmigrations Sitecore Express Migration Tool
  • 38.
  • 39.
    • Upgrade Sitecoreregularly • Irecommendatleastonceevery12-18months • Planning is key for success • Engage a partner for help • Sitecorepartnersdoupgradesallthetime! • Practice helps – often based on content freeze and time it takes to upgrade, you will need to do the process several times • Engage SitecoreSupport for issues you can’t google • Note:onlySitecorecertifieddeveloperscanengagesupport • Don’t use IE to run the upgrade • Modify the web.config/sitecore.configto increase timeouts Tips
  • 40.
  • 41.
    • Email: scott.stocker@edynamic.net •Twitter: @sestocker • LinkedIn: https://www.linkedin.com/in/scottstocker • Sitecore Stack Exchange: https://sitecore.stackexchange.com/ • Awesome-Sitecore: https://github.com/sestocker/awesome-sitecore Contact Me
  • 42.

Editor's Notes

  • #5 To give you in simple words- edynamic is a digital mrkt tech agency. We focus on bringing technology and marketing experience together and help you provide superior customer experience to your clients
  • #6 Deeply committed to Sitecore, our relationship dates back to … delivered hundered… what differentiates us is COE… connectors at marketplace.. Allows to deliver great results .. Awards..
  • #8 The upgrade process is unique for every solution. Each customer may have different levels of customization, different tolerances for content freezes and different preferences regarding testing and release management. Note that simple upgrades – such as moving from 8.1 Update-2 to 8.1 Update-3 – will typically require less analysis and testing than upgrades that traverse major versions.
  • #11 Mainstream support has already ended for versions 6.6 and under 7.0 and 7.1 mainstream is about to end
  • #12 Without mainstream support, assistance for errors and product defects will cost additional money
  • #13 Current browsers work better with the latest versions of Sitecore If you are not on 7.2 or 8.x I suspect you might see some issues today 8.2 drops the dependency on Silverlight
  • #14 6.6 doesn’t have support for > Windows 8 Microsoft Mainstream support has already ended for Server 2008
  • #15 Old software = bad Want to run SQL 2014? Need to be on the latest version. Mongo 2.6 has been end of life. You need to get on 3.x
  • #16 New user friendly UI in Sitecore 8 Vastly improved Experience Editor
  • #24 Planning is probably the key for success
  • #25 The upgrade needs to be rolled out to all of your environments Current version needs maintained while during the upgrade process
  • #26 CMS upgrade process is pretty straight-forward Modules are more complicated Don’t forget the code changes that might be necessary based on new module versions
  • #27 If all sites can be done at once, that is the simplest approach
  • #28 CM + CD Not just prod
  • #29 CM + CD Not just prod
  • #30 CM + CD Not just prod
  • #31 Now you know the components and what to plan for – but how do execute the upgrade? What does the process look like?