CiviCRM Community Forums (archive)

I have inherited a CiviCRM version 1.9.  I have looked at the install instructions and the suggestion is to first upgrade to 2.2 but the download has been taken off sourceforge.  Any suggestions? is it possible to do a fresh install and transfer the data?

Thanks for the link I have found the down load.

Next problem doing a pre update clean I hit a brick wall trying to load contact lists

    * user warning: Smarty error: problem creating directory '/var/vhosts/fern.org.au/civicrm_files/templates_c/en_GB/%%87/872' in /var/vhosts/fern.org.au/drupal-4.7.3/sites/all/modules/civicrm/packages/Smarty/Smarty.class.php on line 1095.
    * warning: Smarty::include(/var/vhosts/fern.org.au/civicrm_files/templates_c/en_GB//%%87/872/8728DD81%%MapField.tpl.php) [function.Smarty-include]: failed to open stream: No such file or directory in /var/vhosts/fern.org.au/drupal-4.7.3/sites/all/modules/civicrm/packages/Smarty/Smarty.class.php on line 1871.
    * warning: Smarty::include() [function.include]: Failed opening '/var/vhosts/fern.org.au/civicrm_files/templates_c/en_GB//%%87/872/8728DD81%%MapField.tpl.php' for inclusion (include_path='.:/var/vhosts/fern.org.au/public_html/sites/all/modules/civicrm/:/var/vhosts/fern.org.au/public_html/sites/all/modules/civicrm//packages:.:/usr/share/php:/usr/share/pear') in /var/vhosts/fern.org.au/drupal-4.7.3/sites/all/modules/civicrm/packages/Smarty/Smarty.class.php on line 1871.

Ah, someone else still on version 1.9 ?? I have several newer version installations running, but our big one is still on version 1.9.   How did you do, did you successfully move to the current version?

We've looked at exporting and importing and also upgrading.   Also there is a utility mentioned that might help, but I couldn't seem to get it to run.

Export and Import
- - - - - - - - - - - - --
Maybe worth considering. 

Cons *********
Newer versions seem to let more records being exported at a time.  The distasteful part for us is that we have quite a few custom fields as well as smart groups.  Also we have used the membership and contribution module.    So if we import then new internal_contact_ids will be created so some amount of manipulation on membership and contribution module records will be needed.

Pros****************
It would be easy to install on a different domain and not risk the production database.

Upgrading
= = = = = = = = =
The prospect of upgrading version by version from 1.9 to what? until we can jump to the current version is not inviting.   We now have over 3 million records for only 9,000 contacts.  We are using the site utility to back the MySQL up because too big for PhpMyAdmin.    I'm not sure if we could reload on a server.   Locally, I have been able to strip out the big activity files, but not sure of ramifications.

I would definitely like to talk with anyone upgrading from 1.9 or that has upgraded multiple versions from 1.9.

Anyone have a utility they'd like to sell?

You raise a good point. The prospects of upgrading with 2 steps is quite a bit different than all the versions.  I have not seen other information about what upgrade versions are required:  When considering an upgrade in the past, I've looked no farther than the upgrade issues in this forum (great to have the forum) and I know they may be special cases, but the prospects seemed daunting.  Combine that with our large file sizes and .... we're still on 1.9 for for our main installation.   I've wondered if the database upgrade scripts could be pulled out and run separately from the full installations.

3.3.5   2011-02-08      
3.3.3   2011-01-19      
3.3.2   2011-01-04      
3.3.1   2010-12-09      
3.3.0   2010-12-03      
3.2.5   2010-11-17      
3.2.4   2010-10-27      
3.2.3   2010-09-07      
3.2.2   2010-08-23      
3.2.1   2010-08-11      
3.2.0   2010-07-28      
3.1.6   2010-07-21      
3.1.5   2010-05-20      
3.1.4   2010-04-14      
3.1.3   2010-02-25      
3.1.2   2010-02-11      
3.1.1   2010-01-29      
3.0.4   2010-01-21      
3.0.3   2009-12-10      
3.0.2   2009-10-28      
3.0.1   2009-10-08      
3.0.0   2009-10-01      
2.2.9   2009-09-14      
2.2.8   2009-08-04      
2.2.7   2009-07-06      
2.2.6   2009-06-18      
2.2.5   2009-05-29      
2.2.3   2009-05-14      
2.2.2   2009-04-03      
2.2.1   2009-03-25      
2.2.0   2009-03-12      
2.1.6   2009-02-26      
2.1.4   2008-12-19      
2.1.2   2008-11-20      
2.0.7   2008-11-20      
2.1.1   2008-10-10      
2.1.0   2008-10-01      
2.0.6   2008-08-20      
2.0.5   2008-07-08      
2.0.4   2008-05-28      
2.0.3   2008-04-30      
2.0.2   2008-04-01      
2.0.1   2008-03-13      
2.0.0   2008-03-12      
1.9.13019   2008-01-31      
1.9.12432   2007-11-29      
1.9.11960   2007-10-25      
1.9.11940   2007-10-24      
1.9.11930   2007-10-24

I would also update it. Without question. Go through the steps once, "by the book" on a backup copy of the databases, and if all goes well, then do it for real.

Is there a list of the required version updates anyplace? (which ones can we skip)

So from version 1.9 would this be the best upgrade path?

CiviCRM 1.9 - Drupal 5.3
CiviCRM 2.0 - Drupal 6
CiviCRM 2.1 - Drupal 6
CiviCRM 2.2 - Drupal 6
CiviCRM 3.3.6 (or latest) - Drupal 6
CiviCRM 4.0 beta3 (or latest) - Drupal 7

And take a backup of the web hosting space and database after each successful Civi upgrade.

I did not do that many incremental backups when I did the D5->D6 upgrade, and the upgrade from 2.2.x to 3.x (which ever version I was landing at back then) trashed the DB doing the 2.2.x to 3.x upgrade. I had to completely roll back to D5 and Civi 2.0.7!!!