Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there any checklist to configure before upgrade for better deciding?

Is there any checklist for it after upgrade?

share|improve this question
up vote 2 down vote accepted

I have used the Upgrade status module on the past to better understand how much work will be involved in upgrading a site from a mayor version to the next.

Also, depending on how many modifications, or modules you have, it will also make the process easier.

One more tip: Check the Drupal documentation, and remember Youtube is your friend.

share|improve this answer
Don't forget to try the Drush Site Upgrade command. drupal.org/project/drush_sup – greg_1_anderson Dec 25 '12 at 15:44

Just follow the 20 steps for successful upgradation from Drupal 6 to Drupal 7. These steps are listed in the Community docuentation page Upgrade process.

share|improve this answer

Identify the hacked modules and/or themes

Often times when you're considering upgrading you also want to have an answer to the question like "Are there any tweaks (hacks) in any of our contributed modules that we need to be aware of?".

Especially if somebody else first created the D6 site, and you're in charge of the D7 upgrade.

Guess what, there's a module for it, it's called Hacked!. Here is a quote from its project page:

... scans the currently installed Drupal, contributed modules and themes, re-downloads them and determines if they have been changed. Changes are marked clearly and if the diff module is installed then Hacked! will allow you to see the exact lines that have changed.

Evaluate module alternatives

When upgrading you might have to replace some module with another module, for various reasons, such as:

  • The module is not yet available (or released) in the new Drupal version.
  • The module will never be upgraded to the new Drupal version, because of some Drupal core changes, or changes in other modules it depended on.

Or you may want to take advantage of adding new features, etc in your upgraded site.

So there are quite some situations where you will have to decide between multiple contributed modules, such as:

  • A stable module.
  • A module that's on the horizon.

Whenever I have to decide between multiple modules, I often use the (23) criteria that I ever documented in "maintenance scorecards" (within the Community documentation about "Comparison of Charting modules"). Those scorecards are actually "applied" to charting modules, but the same criteria can be used, I think, to mostly any type of module comparisons.

D8 module status

The D8 Module Status site provides an interesting summary of various contributed modules, about their D8 readiness. Here is a quote about it:

... a daily script that runs the tests of all the mentioned projects below and displays a summary.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.