I wrote before about the sad state of our drupal-based intranet at the library…well that was two and a half years ago. Only on new year’s eve day did I finally get around to rectifying that unfortunate decision to use the flexinode module years ago.
I used the flexiconvert module to accomplish the conversion from flexinode to cck. It actually worked surprisingly well. There were some wrinkles but I managed to iron them all out. Between the readme file that comes with the module and this set of instructions, the info needed is (mostly) there. It was certainly helpful that I was able to test the process on a local copy of the installation rather than the live one. While working out the process, I did have to roll back a few times and start over.
One immediate stumbling block was a couple syntax errors in an sql statement in the 4.7 version of the module. Obviously, the developer never actually used or tested this version himself. 
The advice to rename your flexinode fields to simple more database-like field names is excellent. In flexinode, the field names and labels are the same, in cck they can be different. Also, I thought it would be smart to use shared cck fields where applicable but that did not make the converter happy so avoid doing that.
We are now in a position to move to drupal 5 which is still supported. I actually have a converted version running on my local machine and it’s looking good so that upgrade will probably happen soon. Then we can look at a drupal 6 upgrade which would put our intranet and new website on the same platform which should be beneficial.
