Upgrading from J 1.5 to J 2.5, using PHPMyAdmin

Hello, I have seen this post: solidsystem.it/how-to-and-tutorials/149-...es-to-joomla-17.html but I'm updating my Joomla site using a different tool (SPUpgrade).

After I upgraded my site, I moved the 3 customproperties tables from my J 1.5 site and imported them into my new J 2.5 site (using PHPMyAdmin), after I did that, I installed CP 2.3.5 (build180). It seems like things are working fine (I still have to test a little more), so, my question is:

what do you think of my migrating process, is it OK to do it like I did?
or did I break something and I'll have trouble with CP?

If my migration process is wrong, could you please tell me what steps should I follow to do it again? remember I don't use JUpgrade,

Thanks

The procedure you followed is fine, as long as the articles kept their original ids after the migration.
In fact the table structure for Custom Properties is the same for the latest J 1.5 packages and the latest J 2.5 versions.

ok, good to know.
thanks

Actually, the J 1.5 and the J 2.5 DB seem to be different, please take a look at the following error message I got when trying to assign access = public to a property (see attached image):

Error while saving: TableCpfield: :store failed
Unknown column 'required' in 'field list' SQL=UPDATE `xxxxxxx_custom_properties_fields` SET `name`='location',`label`='Location',`field_type`='select',`modules`='',`published`='1',`required`='0',`access`='1',`ordering`='1' WHERE `id`='1'

so, the "required" field is missing, what other fields out there could be missing?
did you compare both DB structures?
could you advise how to fix this issue?
Thanks!

attaching image, it seems like it didn't attach

I do confirm that:

- most recent CP version for J1.5: 2.0.5
- most recent CP version for J2.5: 2.3.5

have exactly the same table structure.