Migration CMFCollectorNG to PloneCollectorNG

PloneCollectorNG comes with a migration script that allows the (automatic) migration of several CMFCollectorNG instances to PloneCollectorNG instances. The script can be found in PloneCollectorNG/Extensions/migrate.py

Installation:

• Create an external method inside your Plone site (the destionation) with:

        Id: 'migrate'
  
        Title: ....
  
        Module: PloneCollectorNG.migrate
  
        Function: migrate_trackers
  

• Adjust the url_from and url_to default parameters of the method (in migrate.py) to reflect the source and destination of the migration. url_from is the relative path of the container where your CMFCollectorNG instances live. url_to is a the path to your Plone site or the path to a folder inside your Plone site.
• when you run the external method then every CMFCollectorNG instance inside the source folder (no recursion!!!) will be migrated to the destination. You may modify the script to migrate only one instance (do it on your own risk).
• the script contains also two other methods migrate_memberdata() and migrate_acl_users(). Both are commented by default and they allow you to migrate the users and/or memberdata preferences from your CMF site to your Plone site. (Warning: these methods may override exisiting users and/or member preferences).
• If you are using CMFCollectorNG instances with extended issue_config.py files (you added some more properties for issues) then you need to modifiy the mapping dictionary in the script to reflect the mapping between old properties and Archetypes fields and their schematas.
• It might be useful to migrate the acl_users and memberdata from CMF to Plone first since they are necessary to set the workflow state for the migrated issue instances

Attention:

BACKUP YOUR SITE FIRST BEFORE TRYING THE MIGRATION

I tried my best to perform a 100% migration and to make this script as powerful as possible but of course there might be problems with some installations of CMFCollectorNG. I have tested the script with about 12 CMFCollectorNG? instances with roughly 4000 issues and the migration worked fine.

Please accept that I will give only limited support on migration issues. Don't expect that I will check your sites in case of problems (except as commercial support service). So you should know what you are doing (means you should be able to understand the migration script and modify it if necessary).