The key to this is your assumption that there is "lots of
customization". My goal is always to do as *little* customization as
possible by finding modules that are a good fit and have lots of
flexibility, or by educating the client on ways to bend their goals a
bit to do things in a way that they can be done without a lot of
customization, or by writing patches to modules that make them flexible
enough to do what I need them to do and contributing the patches back
so that they will be maintained and supported, and by trying to avoid using modules that are not widely-adopted (which therefore may have upgrade and maintenance problems).<br><br>If I do those things I
hope to end up with sites that have very little customization. That doesn't eliminate upgrade problems, but it makes the upgrade much much more manageble.<br><br><div class="gmail_quote">2009/3/29 Sam Cohen <span dir="ltr"><<a href="mailto:sam@samcohen.com">sam@samcohen.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I understand the logic in what you're saying, but it makes me wonder whether or not in the real world, big site developers who are now building complex sites in Drupal 6, with lots of customization, are building into their fees and being upfront with clients about what it's going to cost to upgrade that site to Drupal 7. <br>
<br></blockquote></div><br>