Write an upgrade path from 6.x-2.x to 7.x-2.x

Probably this would not be a direct database write, but rather leverage the API itself (ctools exportables). That would require a 6.x compatibility layer possibly.

Since the fields columns is serialized this might require CTools exportables. Some of the other schema changes would have to be made as database writes. Sometime in the next few weeks I'll try to document the changes to make it easier for someone to potentially write this.

Wrote a description of how to port: http://drupal.org/node/1214012.

There could be a temporary table created with the old data, the data dropped on the regular tables, the schema altered, the data loaded from the temp tables, and then written into the tables according to the new schema. I think that would be the easiest way. It would be somewhat like the Views 1 to Views 2 upgrade, except simpler.

The main thing is that the value in the drupal column would sometimes need to be split - i.e., "node_page" would be drupal_entity: node, drupal_bundle: page.

Also salesforce_field_map should be renamed to salesforce_fieldmap, or else the data moved into it.

I'm making this active again, since I just released the first alpha, though I don't intend to work on it currently.