Drupal Audit for Rebuilds (Work in Progress) - DEPRECATED

This is a draft for instructions on what to look for when preparing to build a replacement for a Drupal site. The goals are to figure out all the functionality that the current site is doing, so that it can be recreated on the new site if needed, along with identifying the data and files that will need to be migrated.

Figure out basic drupal facts

What version of Drupal are they using? Where is hosted, and how can you get access to the site to review it?

Review Contributed modules

Review all of the contributed modules that they have installed. Most of the standard drupal modules can be ignored since their functionality will be replaced with the new site, however, you should pay special attention to any modules that communicate with third-party services, as those integrations will likely need to be maintained with the new site.

Review Custom Modules

Any functionality that hasn't been implemented with standard contrib module may need to be migrated/recreated in the new site. Feature modules may contain the structure for things like their content types.

Review the Theme

Determine what functionality is being provided in the theme. It may be hiding in the template.php file or the javascript files.

Review the Database

Since much of the content on the site needs to be migrated, you should look through all the database tables. Create an inventory of all the content types and fields. Search for any additional data that has been stored that may need to be migrated to the new site.

Review the Files Directory

FIgure out the size and types of files. 

Review the settings.php file

Custom functionality may be hiding out in the settings.php file, including redirects and configuration for integrations, such as mail service.

Review the .htaccess file (if applicable)

If the current server is running Apache, some logic may be in the .htaccess file, including things like redirects.

Log in and review the admin links and roles

You can figure out things that the site is doing by poking through the admin menus. Functionality may be hiding in places like Rules and page/layout modules.

Review History