quintagroup.transmogrifier

quintagroup.transmogrifier package provides easy Plone Migration Tool for migrating content from one Plone site to another. Common task for quintagroup.transmogrifier package is migration of content from old Plone version to a new one.

Links

• Home page - http://quintagroup.com/services/plone-development/products/quintagroup.transmogrifier
• Repository - ​https://github.com/collective/quintagroup.transmogrifier
• Releases - ​http://plone.org/products/quintagroup.transmogrifier/releases
• Build status - ​https://travis-ci.org/collective/quintagroup.transmogrifier
• PYPI - ​http://pypi.python.org/pypi/quintagroup.transmogrifier

Features

quintagroup.transmogrifier functionality binds to Plone via portal_setup (GenericSetup) import/export interfaces. This package overrides GenericSetup Content step, so it can be used out-the-box to migrate site content.

To perform its tasks, quintagroup.transmogrifier uses ​collective.transmogrifier package and ​Products.Marshall product.

quintagroup.transmogrifier package includes Plone blueprints for collective.transmogrifier pipelines that allow to:

• return queried items from the catalog
• create pipeline items from contents of Plone site folders
• walk through different GenericSetup import contexts and yield items for every folder
• generate and parse manifest files - listings of objects contained in some foldere in XML format
• migrate properties for objects that inherit from OFS.PropertyManager.PropertyManager mixin class
• use context sensitive components (adapters) to do needed corrections in data generated in previous sections
• set references for content objects
• migrate comments for site content
• extract data from Archetypes file fields
• apply stylesheet to some XML data stored on item.

You can manage import/export procedure by configuring pipeline and appropriate blueprints in quintagroup.transmogrifier configlet that appears after products installation.

Note: quintagroup.transmogrifier package was primarily developed for allowing content migration from Plone 2.1 to Plone 3.2 website. The principle of content migration between sites of different Plone versions is that you have to create buildouts for old Plone 2 site and new Plone 3 site. These buildouts should include several extra packages, since transmogrifier tool is used for Plone content migration.

How-to Guides on common Use Cases

• Content migration from Plone 2 to Plone 3 (Plone 2.1 -> Plone 3.2)
• Content migration from Plone 2.5.5 to Plone 4 (Plone 2.5.5 -> Plone 4.0)
• Content migration from Plone 3 to Plone 4 (Plone 3.2 -> Plone 4.0)
• quintagroup.transmogrifier How-tos

Articles and Blogs

• ​Importing and exporting Plone folders using quintagroup.transmogrifier
• ​Transmogrifier, I want to ...
• ​Migrating Plone 2.5 content straight onto Plone 4