Skip to content Skip to navigation

Drupal 6 to Drupal 7 Migration Worksheet

Author: 
This document is a work in progress. For a formatted version of this worksheet that you can print and fill out, download the PDF.

Rationale for This Document

An upgrade of a Drupal 6 website is a complex proposition. As a general rule of thumb, many professional Drupal development teams approach a major Drupal version upgrade as a new site development project, and estimate anywhere from 60-80% of the original development resources (time, money) for the upgrade.
For a migration to be successful, you will need functional specifications built by someone internal to your organization. By investing the time in answering the questions in this worksheet, you will increase your chances of a successful project.

Goals:

  1. Determine the necessity of upgrading or migrating an existing Drupal 6 website
  2. Determine the scope, resources, and effort required to migrate a site from Drupal 6 to Drupal 7
  3. Provide a high-level overview of various approaches to migrating or upgrading to Drupal 7

Questions to Answer:

  1. What do we have?
    1. Complete Audit document (Appendix A)
    2. Where does Drupal fit in our stack (re: other web technologies)?
  2. How long can we stay in D6?
    1. What’s the risk beyond end of long term support?
  3. Do we wait for D8?
    1. Q1 2014 targeted release date
    2. See http://drupal.org/documentation/version-info for how to choose a Drupal version
  4. Do we need to go to 7 now?
    1. If not now, when?
  5. What other advantages does D7 offer?
  6. What do we need to upgrade?
  7. Do we “upgrade,” “migrate,” or “rebuild”?
  8. What does “upgrade” mean?
    1. Core
    2. Theme
    3. Modules
  9. What does “migrate” mean?
  10. Why should we migrate?
  11. Cannot build new features in D6
  12. Better performance ( e.g., sites.stanford.edu vs AFS )

Outline of D6-D7 Migration Process

  1. Document functionality, features and relationships on the current site + wireframes
  2. Upgrade core or install new D7
  3. Develop content types and views for D7
  4. Re-build theme for Drupal 7 (possible candidate for outsourcing)
  5. Develop migration tool to migrate content from D6 database to new  Drupal 7 database (best candidate for outsourcing)
  6. Migrate media object
  7. Useful links (?)
    1. http://drupal.org/node/1144136 - Migrating D6 Content Construction Kit (CCK) to D7 Fields

 

Global Issues with Moving to Drupal 7:

Data Migration
(outsource?)

  1. Feeds
  2. Migrate Modules

Theme
Core

  1. Fields in core
  2. Entities

Modules

  1. some modules have upgrade tools
  2. can cck be moved from d6 to d7
  3. can views be upgraded or export/import via features?

Training
Redirects
When / what / how to move to Stanford Sites

Do we need to go to D7?

If yes:

  1. Option A: Upgrade
    1. Definition: Replace D6 code with D7 code; run upgrade scripts on D7 database
    2. Good only for really basic sites
    3. Most like your old site
  2. Option B: Migrate
    1. Definition: Install new D7 site from scratch with new database; import content, Views, users, etc.
    2. Clean Codebase
    3. Old content can be left out
    4. Retweak IA
    5. Tweak Data Model
    6. Con: Content Cleanup takes time
    7. Are there migration tools that can be used?
    8. Outsource data migration?
  3. Option C: Develop new site
    1. Definition: Install new D7 site from scratch; no mass import of content, Views, users, etc.
    2. New Information Architecture
    3. New Data Model
    4. New Content
    5. Brand new hotness

If not:

  1. retire
  2. wait for Drupal 8 (life cycle)
  3. move to something else

Appendix A: Drupal 6 to Drupal 7 Audit Worksheet

Technical Audit

URL of Drupal 6 site:

 

Who developed original site (in-house/external):

 

Number of nodes:

 

Number of users:

 

Number of roles:

 

Number of Views:

 

Number of Content Types:

 

Number of Contributed Modules:

 

Number of vocabularies/terms:

 

Number of nodes tagged with taxonomy terms:

 

Custom Theme (yes/no):

 

Number of custom theme templates (.tpl.php files):

 

Custom modules (yes/no - number):

 

Hacks (yes/no):

 

Custom PHP (yes/no):

 

Custom Blocks:

 

JS Libraries:

 

Feeds:

 

Hosting environment (AFS, sites.stanford.edu, department server, external host):

 

Number of vanity URLs / redirects:

 

Performance modifications (Boost, Varnish, Pressflow, etc.):

 

Search (Solr / Google, internal):

 

Files on disk / DB:

 

Functional Audit

Audit of existing content (using analytics, etc.) - what is our critical content?

 

Critical functionality (e.g., data integration, etc.):

 

Content authoring experience (e.g., custom workflows, dashboards, etc.):

 

User Experience (admin and end users):

 

Use of taxonomy:

 

Data integration (importing and/or exporting data [Feeds, Services, etc.]):

 

Permissions matrix (permissions, access control, Views access):

 

Rules and triggers:

 

Hosting environment (resources committed):

 

Layout Architecture (Panels, DS/Context, block.tpl.php, etc.):

 

Navigation Architecture (Book, Taxonomy):

 

Data components (fields, attachments, files, images, etc.):

 

Media Files: