Migration Path

Don't know yet. It's not something that I need to have soon, and while migration paths are important they're also just about the most uninteresting thing to code, ever. Even fixing weird bugs is *way* more interesting.

Personally, I'm hoping that someone will find this nice enough to write a migration path from imagefield, which should be easy apart from the fact that custom titles are not supported in filefield_image at the moment, and therefore either those or the custom alt texts would have to be dropped or pushed into some intermediate storage until filefield_image gains that functionality. Given that this module is currently the only working imagefield-like solution, I would place my bet that someone feels motivated to have imagefields migrated sooner or later. Might be wrong, though.

Migration path from image will be harder to write as it involves fussing with whole nodes instead of only the fields.

Leaving this open as a task, as at least the imagefield migration path should be worked on sometime. Whoever wants to chime in, help is very appreciated not only by myself but presumably a whole lot of users.

i'll sign on to provide a basic one. i'm about to put this into use on a production site and and i'll need some kind of way off if/when it goes.

update: that said i'm not sure i'm in favor of migrating from imagefield to filefield_image and then back to what ever the imagefield replacement is. i'm viewing this as a starting point for new sites.

Is this now the designated thread on migration path from Filefield_Image to Imagefield? (for the moment that Imagefield will be available for D6 and replace Filefield_image)
Like Drewish i'm about to put filefield_image into use on a production site, so I will be available for testing migration.

This module is now phased out in favor of FileField/ImageField 6.x-3.0. All issues are "won't fix" because the module is essentially dead. Please have a look at the project page for some explanations.