60 | | |
61 | | === 5. How to migrate content from one content type to another === |
62 | | |
63 | | If this is a one-off migration, then you might want to consider your options - with just a few items to migrate you may want to think about cutting and pasting, or digging out your regular expressions to manually search and replace the xml files in between the export and import. |
64 | | |
65 | | Alternatively, on import, you can use either the transmogrifier datacorrector blueprint to rewrite the xml or the transmogrifier xslt blueprint to transform it (the latter won't work on a mac though). |
66 | | |
67 | | I still haven't cracked this one completely - so the following is work in progress: |
68 | | |
69 | | Quintagroup themselves have written a couple of products undertaking specific migrations, so these give you a good idea of what you need to do. It seems to me the trick is understanding what information is conveyed by the key value pairs comprising the content pipeline item and the xml that's packaged up with the pipeline item. It's certainly possible to replace the value of a key in the pipeline item - but that probably wouldn't be enough to migrate content where fields have different names etc. |
70 | | |
71 | | {{{ |
72 | | [substitution] |
73 | | |
74 | | blueprint = quintagroup.transmogrifier.substitution |
75 | | |
76 | | key = _type |
77 | | |
78 | | Blog = Weblog |
79 | | |
80 | | PloneFormMailer = FormFolder |
81 | | }}} |