Author Topic: Data Loss - Upgrading from Beta 3 to Beta 5 (Read 6046 times)

LanceD · March 05, 2008, 05:53:38 pm

I exported my contacts to a CiviCRM CSV file before upgrading from beta 3 to beta 5. I also exported the contributions via CiviCRM's export function before upgrading. Since I'm running a Joomla install, I then uninstalled beta 3, installed beta 5, and attempted to reimport the contacts I had exported from CiviCRM. Two problems immediately appeared.

1) The CiviCRM contact matching process incorrectly identified a number of fields names from the CSV file that CiviCRM had created. I would think that it should at least be able to get it's own file format right.

2) Every time I try to import it tells me that I have mismatched contact ID's. It's a fresh install with no data in it so I'm not sure why it's telling me that.

There's only a handful of records involved right now, but I'd really rather not deal with data loss. Can you advise me on what to do?

Also it might be wise to try to address the first item as it sounds like a bug. Please help.

Donald Lobo · March 05, 2008, 06:43:07 pm

1. You could have reused the same database by following the instructions here:

http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrading+Joomla%21+Sites+to+1.9

(and skipping step

I dont think doing an export / import will necessarily get all your information back (depending on what you have changed etc). If you do feel that our import should match the export titles, please submit a patch that does the needful

2. Since your db is empty, the import will create new contacts (and not necessarily in the same order as they were originally created). Hence the mismatched contact id's message.

In general i think using your beta3 database is an easier and more preferred solution

lobo

LanceD · March 05, 2008, 07:23:56 pm

Thanks for the feedback, Lobo. I've got a few things I have to do for my client before I can work on a patch, but I'm willing to try it. To speed things up, what file would require the patch?

Also, if importing any data into the Internal Contact ID field is always going to throw an error like that (or will it?), then why have it?

Donald Lobo · March 05, 2008, 08:04:43 pm

1. CRM/Import/Form/MapField.php, function defaultFromHeader( ).Note that the header patterns come from the xml files. but for now, u can hack it in there for the fields u need and give us a good set of patterns

2. The internal contact id is typically used for existing contacts. i.e. a typical pattern might be:

export contact id, first name, last name, email address

munge data fields as you like

import using internal contact id match and update a few existing fields with new data

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: Data Loss - Upgrading from Beta 3 to Beta 5 (Read 6046 times)

LanceD

Data Loss - Upgrading from Beta 3 to Beta 5

Donald Lobo

Re: Data Loss - Upgrading from Beta 3 to Beta 5

LanceD

Re: Data Loss - Upgrading from Beta 3 to Beta 5

Donald Lobo

Re: Data Loss - Upgrading from Beta 3 to Beta 5