Migrate plugin data about indico-migrate HOT 4 CLOSED

Probably best to just add it to indico-migrate and add a --plugin option (multiple=True) where we can select which plugin data should be migrated.

Vidyo and LiveSync are probably the most tricky ones since they really need the plugin to be installed for the migration as they have their own database tables.

from indico-migrate.

Not a strict requirement, but it would be nice if third party plugins could provide their own conversion plugin. For example, we use a custom ePayment plugin with its own transaction type in indico 1.2 and indico 2.0.

from indico-migrate.

Since migration is a one-time thing it's better if you just clone the repo and add your own code. So far nobody needed plugin-related migrations and it'd take quite some development effort to add something nice/extensible here for little gain.

from indico-migrate.

Closing this one since most people migrated by now and nobody asked for any of this plugin data to be migrated.

from indico-migrate.