Skip to main content
7 events
when toggle format what by license comment
Dec 21, 2016 at 6:03 comment added Christia The site I am working on was 4.3.8 and had some custom coding in a non-standard install with over 100,000 people in the database. Just backing up the codebase and database took an hour. The installer ran for 8 hours on the test and 8 on the live, and there was significant prep work involved. Depending on your situation, with a CiviCRM version that old, it could easily take 40 hours. But if it's pretty standard and clean, I could see 4 working. Though they shouldn't really bill for the hours the script is updating unless errors come up. Then there's testing. We'd have to see a breakdown.
May 22, 2015 at 1:36 comment added Coleman @Sonicthoughts I think this would be good as an answer rather than a comment.
May 13, 2015 at 3:36 comment added Sonicthoughts I've spent 20 hours on an upgrade and 1 hour. If you have custom template/php files they all need to be retrofitted and that can take a lot of time. If this is an estimate and not a quote then you probably have some padding. You should definitely ask your consultant to justify 40 hours though.
May 12, 2015 at 14:37 comment added ErikH - CiviCooP The time required is not necessarily determined by the amount of custom fields, but more by the complexity of the customizations. Are your customizations in on or more civicrm extension(s)?
May 12, 2015 at 14:15 comment added Donald Lobo Note that many a times providers discover customizations / modifications to the code / db which in general results in a longer time to sort thru, understand and fix. This might be one reason for the higher quote.
May 12, 2015 at 12:21 comment added Gillian R This does help, thanks! We are on Drupal Core 7.19 with CiviCRM version 4.2.7. We want to be on CiviCRM 4.6x. We have some customization, including some links to our website, but not an enormous amount of custom fields.
May 12, 2015 at 11:59 history answered ErikH - CiviCooP CC BY-SA 3.0