" Part of providing value as a consultant is knowing when we should and
when we shouldn't do something for a customer unless they say we don't
care do it our way."
Right. And as a consultant we probably shouldn't be making blanket
recommendations without assessing the actual situation first.
In my experience it is a rare site that actually needs a rebuild. Why
would we bother with an upgrade path at all if that weren't the case?
These instances stand out in our mind because that's A) usually when
they call the consultants in, and B) They're a giant PITA. But as far as
'always being more cost effective to rebuild' I think that is very far
off the mark. And not a good or true impression to leave a client with.
On 02/13/2012 11:21 AM, Christian Pearce wrote:
> Points well taken. What ruler do we use to decide quickly if it is a simple site that is could be upgraded easily? Sort of doing the upgrade to see if it works. For example are you using CCK and views? If so then no it isn't worth it? Or how much content do you have? Part of providing value as a consultant is knowing when we should and when we shouldn't do something for a customer unless they say we don't care do it our way.
> ----- "Sam Tresler"<sam@...> wrote:
>> From: "Sam Tresler"<sam@...>
>> To: "A list for Drupal consultants and Drupal service/hosting providers"<consulting@...>
>> Cc: "Christian Pearce"<pearcec@...>
>> Sent: Monday, February 13, 2012 11:08:26 AM GMT -05:00 US/Canada Eastern
>> Subject: Re: [consulting] Feasibility
>> I'm not sure I agree with this. It depends on what/how the site was
>> built originally. I've upgraded simple sites along that path (5 to 6,
>> then 6 to 7) in less than a day. More complex sites or sites that
>> weren't built properly in the first place, the assertion that rebuilt
>> cheaper may be true. I don't think this is a blanket statement that
>> can say until we know more details about the site.
>> Upgrading themes is fairly simple if you follow the well published
>> by step guides.
>> I guess my main point is "Upgrades are never smooth" is not the case.
>> Frequently they are, and when they aren't it's generally due to
>> that need to be fixed regardless of the upgrade.
>> Sam Tresler
>> On 02/13/2012 10:45 AM, Christian Pearce wrote:
>>> (Please don't turn this thread into garbage. Which tends to happen
>> from time to time.)
>>> Hi Amy, I don't want this to necessarily be about you or turn you
>> off from our list. So please accept my advanced apologizes if it
>>> I wanted to get people's thoughts on upgrade versus rebuild from a
>> cost perspective. Seems to me going from 5 -> 7 would require going
>> to 6 first. Upgrades are never smooth. Having to go from 5 -> 6 and
>> the 6 -> 7 would be effectively paying for 2 upgrades.
>>> What are the pro's of upgrading?
>>> 1. Site content comes along for the ride.
>>> What are the con's?
>>> 1. More expensive then a rebuild
>>> 2. Might be forced to redo functionality
>>> Seems to me in either case you need to upgrade the theme to work in
>> 7. And you are more then likely finding replacement modules for
>> existing functionality. So if you are already forced to redo
>> functionality, might as well put the money towards a refresh. Further
>> I would venture to say on small sites it would be more worth while to
>> redo functionality and redo the content by hand.
>>> Please lets have a healthy, no flame, honest and open opinions
>> discussion. Also please don't talk ill of Amy's request. I am sure
>> several non-profits are in her shoes. And I would suspect budget is
>> limited. Hence my reason for bringing it up. What is going to be the
>> most cost effect.
>>> ----- "Weinstein Amy"<amy@...> wrote:
>>>> From: "Weinstein Amy"<amy@...>
>>>> To: consulting@... >>>> Sent: Monday, February 13, 2012 9:46:58 AM GMT -05:00 US/Canada
>>>> Subject: [consulting] Please post this job listing on the mailing
>>>> Freelance job opportunity with small non-profit (501c3)
>>>> dedicated to funding children's brain tumor research. Experience
>>>> required includes Drupal 5, 6 and 7. HTML, SQL, PHP. Position is
>>>> part time and would require upgrade of existing website from Drupal
>>>> to Drupal 7. Also, transfer of site from existing host to Drupal
>>>> Gardens. After upgrade is complete, ongoing maintenance (10
>>>> hours/week) would be welcomed. Please respond ASAP to
>>>> amy@... >>>>
>>>> consulting mailing list
>>>> consulting@... >>>> http://lists.drupal.org/mailman/listinfo/consulting >>>