CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • upgrade or new install when moving servers?
Pages: [1]

Author Topic: upgrade or new install when moving servers?  (Read 1576 times)

m.e.

  • I post frequently
  • ***
  • Posts: 157
  • Karma: 5
  • CiviCRM version: 4.0.9
  • CMS version: Drupal 7.9
upgrade or new install when moving servers?
December 16, 2009, 11:54:40 am
Hello -

I'm moving a Drupal site under development to a new server account. While doing this I'd like to install the latest 3.x version of Civi. On the old server we had installed Civi 2.2.6.  Will it work if I just install the latest Civi fresh, and then import the database from the old site?

Thanks in advance-
m.e.

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: upgrade or new install when moving servers?
December 18, 2009, 03:00:18 am
If your data in 2.2.6 is important I would recommend you should upgrade it to v3.0 and then migrate to new server.

Kurund
Found this reply helpful? Support CiviCRM

teleman

  • I’m new here
  • *
  • Posts: 1
  • Karma: 0
Re: upgrade or new install when moving servers?
January 21, 2010, 12:31:54 pm
I've got the same issues. I had outdated Drupal and outdated CiviCRM. I'm wanting to move servers and upgrade. We had all our civi contacts imported using a csv file. No contacts have user profiles yet on drupal. I've tried migrating servers, then upgrading but had database problems. Our drupal site css was hacked and looked terrible after that. We had no other modules. We had problems with CiviCRM.

I thought it was best to do a new install of Drupal 6.15 and CiviCRM 3.0.3 on the new server (used as a development site for the time being till I repoint the name servers) so that I wasn't dealing with the hacks from the previous developer. I was planning on recreating the drupal content, and figured I could recreate the civiCRM profiles (we have no events right now), paypal processor, and google map, then importing the contacts again.  Am I doing this backwards? Is there an easier way? And in the end, how can I get all these contacts (~150) to create user accounts without letting the whole world sign up for users.

Many thanks to the programming wizards that put together CiviCRM. It's sweet and we're super excited to get up and running.

Peace,
Teleman   

sonicthoughts

  • Ask me questions
  • ****
  • Posts: 498
  • Karma: 10
Re: upgrade or new install when moving servers?
January 22, 2010, 08:09:55 am
Quote
I thought it was best to do a new install of Drupal 6.15 and CiviCRM 3.0.3 on the new server (used as a development site for the time being till I repoint the name servers) so that I wasn't dealing with the hacks from the previous developer.

I was going to do the same thing, but realized that when you upgrade, its really a fresh code base (unless you have customizations, which should be isolated in a directory) so unless there are database hacks or a corrupted database you should be good.  Kurund - aren't there ways to check the database integrity as part of the upgrade?

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • upgrade or new install when moving servers?

This forum was archived on 2017-11-26.