#40 Reasons to Migrate to TYPO3 CMS 6.2 # ##Co-Authored at TYPO3 Camp Mallorca 2014 # ###WARNING: This is a relatively short transcription a 45 Minutes Discussion that around 20 people had at a Session of a Barcamp. ###It is not a full arguments list on why, how and when you or your customers should upgrade/migrate to TYPO3 CMS 6.2. Remember that we all live on a free planet, where digital predators will eat your non-maintained website very easily. Dont come whining and search for a scapegoat in TYPO3. You have been warned! - Yours Reverend NeverEnd Please add your Questions to this Pad and your Contact details ## ##Questions People have 1. How much does it cost? 1. Will my extension still work? 1. How much effort will it be to train my editors? 1. Do I have other options than this upgrade? 1. Will the new version run on my server / hosting package (PHP version, etc.) 1. Can I upgrade to 6.2 while running 4.5 in parallel (multiple PHP versions available?) 1. What are the options if extensions are not compatible with 6.2? 1. What can happen if I have a security leak staying at an older TYPO3 version? 1. Why should I upgrade? There seem to be only small changes visible to the editor! 1. Why should I upgrade if typo3.org itself is still running on 4.5? (we are working on that!) 1. Will piBase extensions work with 6.2? 1. Do we need to upgrade an internal web page as well? It's not available from the internet. 1. Is TemplaVoila supported with 6.2? Will it be maintained in the future? 1. My provider offers 1-click upgrades - does this really work for migrating from 4.5 to 6.2? 1. I have never updated my computer. Why is my computer running so slow? What is a computer virus? 1. What is the meaning of life? And do I need to make backups? ##Reasons to Migrate 1. No security updates for 4.5 after March 2015 1. No compatibility updates for new browser versions after March 2015 1. Improved Speed (compared to 4.6, 4.7, 6.0, 6.1) 1. Images and media files are not duplicated in /uploads (pic.jpg, pic\_01.jpg, pic\_02.jpg, ...) 1. Underlying technology also evolves and is partly EOL (End of Life) 1. some customers may find a need for a complete relaunch (special new features supporting e.g. Responsive Web Design) 1. New features on the web won't be implemented to old versions (Or will be only implemented in the new version) 1. Several default packages available in the EM (for new projects) 1. Improved UX backend (Check changelogs and do a compilation of most important changes) 1. Get rid of orphaned extensions (missing [security|bug] fixes) 1. New features!! Using FAL to e.g. separate your media files from the web server. 1. More thorough system check available in Install Tool 1. Migration tool is helpful identifying possible problems during upgrade (\url{http://typo3.org/extensions/repository/view/smoothmigration)} 1. Upgrade wizards in Install Tool do most of the work 1. You do not need to have a major upgrade for the next 2,5 years / you have a really easy upgrade path for maintenance / patch releases 1. Composer support 1. Use of Namespace in PHP to be more compatible to other software 1. theming is easier with the soon be available extension themes ##Contact Details Ingo Schmitt, is@marketing-factory.de, @ischmitt Olivier Dobberkau olivier.dobberkau@dkd.de @T3RevNeverEnd