[development] 5.x to 6.x migration timeline, best practices, tips

Earnie Boyd earnie at users.sourceforge.net
Mon May 18 12:27:23 UTC 2009

Quoting T L <tloud365 at gmail.com>:

> Hello All,
> I've inherited a 5.x (5.05 I think) site with about 20 contributed modules
> and one monster custom module (~ 7000 lines), and I'm looking at migrating
> to 6.x sometime in the next few months.  I've looked over the handbook pages
> and done a little bit of googling with some good success.  But I haven't
> found much info on planning or common pitfalls.
> So I was wondering if anyone had any suggestions on things to look out for
> or a generalized timeline?  My guess was at least 100 hours to upgrade to
> 5.18, migrate to 6.12, test the system, and then adjust the theme and api
> calls.  Does this seem reasonable at all?
> Any thoughts, suggestions, or redirects to resources would be much
> appreciated.

Here is what I did to move from 4.7.3 to 6.10:  

Be sure to move the contrib modules directory out of the Drupal tree  
while upgrading the core modules.  Others have already mentioned coder  
and deadwood modules.  When using deadwood, take the resulting module  
as a report of what needs to be done manually; there is a lot left to  
the user but most of it is documented in the resulting source.

-- http://r-feed.com/           -- http://for-my-kids.com/
-- http://www.4offer.biz/       -- http://give-me-an-offer.com/

More information about the development mailing list