Goodbye Drupal 6
Security updates and most support, in general, is now gone for Drupal 6. What do you do now? No, it’s okay, don’t panic. There is something that can be done. Although many sites that were running on Drupal 6 have already started the process of migrating to another version of Drupal, not all sites have had the chance for one reason or another.
Support ended on on 2/24/2016 and that means that the community has largely left D6 behind. There aren’t going to be as many bug or security fixes, if any at all, for contributed modules and this means that sites running Drupal 6 are left in a less desirable state and could become vulnerable to attack in the future. It can be quite scary if you aren’t a developer or someone who has spent a lot of time in Drupal. So what do you do? How do you stay safe?
As you know now, just because Drupal 6 hit end of life, your sites didn’t magically stop working or anything crazy. The question is whether it is time for you to move on from Drupal 6 to a supported release like 7 or 8. Chances are that you will want to avoid this upgrade question for as long as possible, so upgrading to Drupal 8 will provide the longest support cycle for your site and it boasts a ton of new features.
Depending on your site, you may be able to use Drupal’s built in upgrade modules to do this upgrade from 6 to 8, but it is still a work in progress, so your results may vary. There are a few things at the time of this writing that are not supported in this method. One of the larger ones is the Views module and that means that a lot of the more dynamic portions of some sites will not be able to directly upgrade at this time.
Nervous about making this transition by yourself? Don’t have a dedicated dev team to handle taking your site into the modern web? I just happen to know a really great team that can help.