How do I import records from 4.5.1 to 5.0.0e?

[bstonehill]

It appears I may be having some issues with 5.0.0e because I upgraded from 4.5.1. I don't have the same issues in a new 5.0.0e installation. I'm moving sugar and the database to a new server and doing a 5.0.0e upgrade at the same time. When I try to import my data into a new 5.0.0e installation I get this message any time I try to login to sugar, "Sugar CRM 5.0.0e Files May Only Be Used With A Sugar CRM 5.0.0 Database". It imports fine into a new 4.5.1 installation though.

Is there any way to import data from a 4.5.1 database?

[eggsurplus]

Why not just point your new install to your upgraded database? Or do you think the database is part of the issue?

[bstonehill]

Well, i'm moving the database and everything to a new server. So I exported all the data from the mysql database on the 4.5.1 server, installed a fresh copy of 5.0.0e on the new server, and then imported the data from the 4.5.1 database into the new 5.0.0e database. After importing the data I get that message that 5.0.0e is not compatible with the database. I know some of the tables have changed a bit in 5.0 and my guess is that during the import it's overwriting the new tables with the old ones. I am hoping there is a way to work around this.

[Angel]

From your description of the problem, it sounds like your import included all the tables.

In which case, take a look at the Config table and find the record where the name column equals "sugar_version"

Update that record to reflect as 5.0.0 and then try to login to Sugar. If you are able to login, immediately access the admin control panel and run all rebuild operations.

[bstonehill]

Thanks, that got rid of the incompatibility message and let me login, but as soon as I do I get an sql error.

Query Failed:SELECT tracker.* from tracker WHERE user_id = '1' AND visible = 1 ORDER BY id DESC LIMIT 0,10::MySQL error 1054: Unknown column 'visible' in 'where clause'

I'm guessing this is due to the differences between 5.0 and 4.5.1 tables and it's missing something it needs.

Any other suggestions?

Thanks!

[bstonehill]

Okay, I had to manually add 3 fields to the tracker table and that SEEMS to have cleared it up. I am concerned though because I had to guess what the field types were supposed to be and because I'm not sure if I'm going to run into more issues like this once it's put into production. Does anyone know if there are any other differences in the tables? Should I be concerned about this?

Thanks

[roblaus]

Hi,

I don't quite understand why you didn't upgrade the "normal" way. However, have a look at the handling of email addresses. There is a substantial difference.
And: if you say "importing" - do you mean a dump restore or using the Sugar import function? The former will definitely NOT work.

rgds
rl

[Angel]

Okay, I had to manually add 3 fields to the tracker table and that SEEMS to have cleared it up. I am concerned though because I had to guess what the field types were supposed to be and because I'm not sure if I'm going to run into more issues like this once it's put into production. Does anyone know if there are any other differences in the tables? Should I be concerned about this?

Thanks

Yes, there are other differences, hence the point about the rebuild in my prior post.

And to Roblaus' point, export/import is not the recommended way of performing an upgrade, precisely for these reasons.

What led you to do an import versus resolving the upgrade issues (assuming you were experiencing some)?

[bstonehill]

The problem I was having with the upgrade is that I can't get my custom module subpanels to show up under accounts. They did show up on my development server which was a fresh 5.0 install but not on my production server which was an upgrade from 4.5.1. I've followed every instruction I could find about adding subpanels but none of them worked. I did create the relationship in module builder before exporting the module. Since the only difference between them is that one is a fresh 5.0 and one is an upgrade I figured that had to be the reason why.

I am continuing to get mysql errors on this installation. I've been fixing them as I came across them but when I did a repair I got a whole bunch of errors so I'm guessing I'm fighting a losing battle here.

You said that I went about importing everything the wrong way? I didn't export any of the sugar files or settings. I just exported the mysql database as an sql file and then imported into the new one. Should I be doing it differently? Can I import just the data and any custom fields without overwriting the original tables?

[roblaus]

As I said - between versions there are often schema changes. You can't just use an old DB with a new file system. Please use the recommended upgrade routines. See also the installation & upgrade forum.

rgds
rl